> For the complete documentation index, see [llms.txt](https://unicef.gitbook.io/unpp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unicef.gitbook.io/unpp/partners/pre-screening.md).
# Pre-Screening
## Pre-screening
Pre-screening is a new feature on UNPP. It will be done by the UN once at the time of a CSO registering an account on the portal. Pre-screening serves as a deterrent for organizations that are not CSOs. The implementation of pre-screening will result in a modification of the registration screen.
### Actions:
* CSO user selects type of organization and fills the basic information section in the registration form
* The “legal status” section currently placed in the profile—and which includes fields like, “year of establishment in country of operation,” “does the organization have a governing document?” “is the organization registered to operate in the country?” will be brought forward to the registration field
* The CSO can upload the following documents:
* Governing document
* Registration document
* Letter of recommendation
* If a user does not have a governing document or registration document, they can provide a reason for lack of documentation
* The CSO fills the partner declaration, enters their email and password, and provided that the organization is not a duplicate or on the sanctions list, the CSO will be granted access to the portal.
* Once the CSO is in the portal, the documents uploaded will pre-populate the legal status section of the portal and cannot be edited. Users will have the option to ‘add new’ section to upload updated versions of the documents, as relevant. If reference letters uploaded, it will pre-populate the reference section of the portal and cannot be edited, however, the CSO can choose to add additional references.
* Once the CSO is in the portal, their documents can be verified by the UN using the steps in the verification workflow. Verification can happen at any time in the portal.
* If during verification, the UN realizes that the organization falsely presented itself as a CSO (for example, by uploading a governing document indicating that the entity is actually a for-profit enterprise, or uploading a registration document issued to another entity, or indicating in the “reason for lack of documentation” field that it has no registration certificate due to the disbanding of the relevant government entity, when the extenuating circumstance cited is not factual), then the organization can be given an escalated risk flag and subsequently removed from the portal.
### Who has permissions for Verification:
* Editor Advanced
### Restrictions:
* An organization must upload at least one document or provide explanations to gain access to the portal. UNPP will conduct a system-enabled check to ensure that either a file (.pdf, .jpg, .doc, .tiff, .png) is uploaded OR text has been entered the “reason for lack of documentation” field. Those organizations found to have not complied with these requirements will not be able to proceed with registration.
* If, after an organization has successfully registered on UNPP but is found during the human-enabled verification process—to not be a CSO, then it and all its users will be deactivated from the portal.
### Navigations for Pre-screening:
#### The steps for pre-screening are as follows
**1.**\
\
\
\
\
**2.**\
\
\
\
**3.**\
\
\
\
\
\
 
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://unicef.gitbook.io/unpp/partners/pre-screening.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.