> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/control-center/admin.md).

# Admin

Manage users, teams, roles, and API access credentials.

Control who can access the platform and what they can do. Manage **users**, organize them into **teams**, and issue **API keys** for programmatic access.

{% columns %}
{% column %}

#### Manage access

Assign roles to people and group them into teams for product-space access.
{% endcolumn %}

{% column %}

#### Secure integrations

Create permission-scoped API keys for the integrations that need them.
{% endcolumn %}
{% endcolumns %}

#### At a glance

| Area         | Use it to                                 | Start here                              |
| ------------ | ----------------------------------------- | --------------------------------------- |
| **Users**    | Invite people and assign roles            | [Users](#users)                         |
| **Teams**    | Group members and grant agent permissions | [Teams](#teams)                         |
| **Roles**    | See what each role permits                | [Roles](/control-center/admin/roles.md) |
| **API Keys** | Create programmatic credentials           | [API Keys](#api-keys)                   |

People receive account-wide roles. Teams group people together and, separately, scope them to spaces. Integrations receive API keys with selected permissions.

## Roles and spaces

Access in Qore is organized around two ideas that recur throughout this module:

* **Spaces** are the product surfaces a team operates in: **Console** (building and running) and **Control Center** (this surface). A team selects one or both when it's created.
* **Roles** are account-wide permission sets: **Developer**, **Governance Manager**, **Auditor**, **Account Admin**, **Organisation Admin**, **Approver**, and **Billing Manager**. A single user can hold several roles at once. See [Roles](/control-center/admin/roles.md) for what each one grants.

## Related

{% content-ref url="/pages/807cab861e090edd0ce825909db3db1b28f73799" %}
[Control Center](/start-here/control-center.md)
{% endcontent-ref %}

{% content-ref url="/pages/9cd0c4d868b97b43a234c8d0ca5c3690fa58decb" %}
[Evals](/control-center/evals.md)
{% endcontent-ref %}

{% content-ref url="/pages/049796530f3942b2e739e565a1e673ad4924290e" %}
[Controls & Audit](/control-center/controls-and-audit.md)
{% endcontent-ref %}

{% content-ref url="/pages/eIjuTBKGdEo5Aq2Akkal" %}
[Cost Control](/control-center/cost-control.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.uptiq.ai/control-center/admin.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.