> For the complete documentation index, see [llms.txt](https://docs.xygeni.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xygeni.io/xygeni-products/application-security-posture-management-aspm/inventory/collaborators.md).
# Collaborators
The **Collaborators Inventory** displays information about collaborators of your project(s), including:
* **SCM Organizations**
* **Users**
* **User Groups**
{% hint style="info" %}
You can reach the **Collaborators Inventory** page by selecting the Collaborators tab at the top of any Inventory page.
{% endhint %}
The **Collaborators Inventory** page displays the following information:
* Total number of organizations
* Total number of user groups
* Total number of users
* A table with a full listing of all the Collaborators
{% hint style="info" %}
Click on an asset to see its details.
{% endhint %}
In the **Findings** tab, you will find detailed information about the collaborator as well as a summary of all the *issues introduced by the selected collaborator*.
In the **Audit Trail** tab, you will find a timeline of all the security issues *introduced by the selected collaborator*.
---
# 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.xygeni.io/xygeni-products/application-security-posture-management-aspm/inventory/collaborators.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.
