> For the complete documentation index, see [llms.txt](https://docs.vcheckglobal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vcheckglobal.com/products/id-verification/projects.md).
# Projects
#### Project Navigation and Overview
1. Project List View: The platform first displays a list of all your active orders.
2. **Detailed Project View:** Select the project you want to open from the list. This action takes you to the Project Area, which provides a consolidated, holistic record of the entire order.
Within this central location, you gain a single source of truth for all subjects and reports, allowing you to:
* View all subjects within that project.
* See the type of verification run on each subject.
* Access all reports associated with each ID Verification attempt.
### Project Participants
To manage participants, open the Messages panel and look for the participants' preview area. Click the "+" (Add) icon to open the menu.
**Add New Participants:**\
Type the emails of the new participants and press add
**Manage Existing Participants**\
In the lower panel, you will find a list of all participants. Review their status (e.g., *Full Participant* or *Email Only*). You can remove participants directly from this list.
{% hint style="info" %}
**Please note:** If a participant is listed by their email address (e.g., **), they are not a registered Platform User. They will receive project updates via email only.
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.vcheckglobal.com/products/id-verification/projects.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
