> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-user-manual/settings/users-and-groups.md).

# Users and Groups

Admins can manage users, groups and invitations in the "**Users & Groups**" section of the settings.

<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2F2lYuLB2tOtV7Tbx5mkUG%2FScreenshot%202023-04-05%20at%2014.20.56.png?alt=media&#x26;token=8795db5d-e493-47c3-b353-4abce44fc9a7" alt=""><figcaption></figcaption></figure>

You will find up to five tabs in this section:

* **Users:** is where you will be able to [manage the roles](/carto-user-manual/settings/users-and-groups/managing-user-roles.md) of existing users and [delete users](/carto-user-manual/settings/users-and-groups/deleting-users.md) if needed.
* **Invitations:** to view and manage [invitations to new users](/carto-user-manual/settings/users-and-groups/inviting-users-to-your-organization.md).
* **Requests:** to view, accept or decline requests to join your organization.
* **Groups:** here you'll be able to view the existing [user groups](/carto-user-manual/settings/users-and-groups/managing-user-groups.md) that have been synchronized from your SSO or through [SCIM provisioning](/carto-user-manual/settings/users-and-groups/scim-provisioning.md), as well as the number of members for each one.


---

# 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.carto.com/carto-user-manual/settings/users-and-groups.md?ask=<question>&goal=<user_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.
