> 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/ai-workbench-qore/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](/ai-workbench-qore/control-center/admin/users.md) |
| **Sign-in** | Let invited people sign in with Google, Microsoft, or a password | [Single Sign-On](/ai-workbench-qore/control-center/admin/single-sign-on.md), [Password Sign-In](/ai-workbench-qore/control-center/admin/password-sign-in.md) |
| **Teams** | Group members and grant agent and app permissions | [Teams](/ai-workbench-qore/control-center/admin/teams.md) |
| **Roles** | See what each role permits | [Roles](/ai-workbench-qore/control-center/admin/roles.md) |
| **API Keys** | Create programmatic credentials | [API Keys](/ai-workbench-qore/control-center/admin/api-keys.md) |
| **Help** | Answer common questions and fix sign-in, team, and key issues | [Admin: FAQs & Troubleshooting](/ai-workbench-qore/control-center/admin/admin-faqs-and-troubleshooting.md) |
Access is invite-only: people sign in only after they're invited, whichever sign-in method they use. 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: **Viewer**, **Billing Manager**, **Approver**, **Developer**, **Governance Manager**, **Auditor**, **Account Admin**, and **Organisation Admin**. A single user can hold several roles at once. See [Roles](/ai-workbench-qore/control-center/admin/roles.md) for what each one grants.
## Related
{% content-ref url="/pages/807cab861e090edd0ce825909db3db1b28f73799" %}
[Control Center](/ai-workbench-qore/start-here/control-center.md)
{% endcontent-ref %}
{% content-ref url="/pages/9cd0c4d868b97b43a234c8d0ca5c3690fa58decb" %}
[Evals](/ai-workbench-qore/control-center/evals.md)
{% endcontent-ref %}
{% content-ref url="/pages/049796530f3942b2e739e565a1e673ad4924290e" %}
[Controls & Audit](/ai-workbench-qore/control-center/controls-and-audit.md)
{% endcontent-ref %}
{% content-ref url="/pages/eIjuTBKGdEo5Aq2Akkal" %}
[Cost Control](/ai-workbench-qore/control-center/cost-control.md)
{% endcontent-ref %}
***
{% columns %}
{% column width="83.33333333333334%" %}
Maintained by Abhishek Paul
AI-assisted, human-approved
{% endcolumn %}
{% column width="16.666666666666664%" %}
{% endcolumn %}
{% endcolumns %}
---
# 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.uptiq.ai/ai-workbench-qore/control-center/admin.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.
