> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/en/faq/account/access-management.md). # Access Management Can I grant access to the Sirdata console to one of my collaborators? Yes. Go to the CMP portal: \ Click on the top right to access the account information:

Then click on “Access Management” / “Associated Accounts.” You will then be able to send an invitation to your collaborator. Note: If your collaborator already has an account with Sirdata or is already associated with another account, the operation is not possible.\ Feel free to contact support in this case to get assistance.

### Difference between an Administrator and a User When you add a collaborator to your CMP account, you can choose to assign them a role: **Administrator** or **User**. These roles determine the level of access to the different features of the account. \ 👤 **Administrator** * Has full rights on the account. * Can modify billing information (address, payment method, etc.). * Can view and download invoices. * Access management : Can add, modify, or delete users. 👥 **User** * Has limited access to the account. * Cannot access billing information. * Cannot modify the payment method or view invoices. * Can only view data and features related to CMP management (according to the granted permissions). 💡 To change a collaborator’s role, go to the Associated Accounts section and click on the action menu to the right of the relevant account. --- # 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://cmp.docs.sirdata.net/en/faq/account/access-management.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.