> 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/background-checks/project-participants.md).
# Project Participants
**Project Participants** are individuals you want to include on all communications for a specific project. Participants will receive status updates, report delivery emails, and any project-related messages.
To manage participants, open the Messages panel and look for the participants' preview area. Click the "+" (Add) icon to open the menu.
{% hint style="info" %}
Vcheck Customer Success is always included as a default Project Participant.
{% endhint %}
**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/background-checks/project-participants.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.
