> 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/governance/account-settings.md).

# Account Settings

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)       |
| **API Keys** | Create programmatic credentials           | [API Keys](#api-keys) |

People receive roles scoped to product spaces. Teams group people together. 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 role or team applies to: **Studio** (building), **Console**, and **Control Center** (this surface).
* **Roles** grant permissions within a space. The available roles span all three spaces plus account-wide scopes: **Studio Collaborator**, **Studio Builder**, **Studio Admin**, **Console Admin**, **Control Center Admin**, **Control Center Auditor**, **Account Admin**, and **System Admin**. A single user can hold several roles at once.

## Users

The Users screen lists everyone with access to the account. Open **Account Settings → Users**.

<figure><img src="/files/waEGH1LJB70KPLXVgYvJ" alt="The Users list in Account Settings, with columns for Name, Email, Phone, and Status"><figcaption><p>The Users screen, listing everyone with access to the account.</p></figcaption></figure>

Search by name or email, narrow by status, and use **+ Create User** to add someone. Each row shows the user's **Name**, **Email**, **Phone**, and **Status** — **Invited** (added but not yet active) or **Active** — with a per-row **Actions** menu.

### Create or edit a user

Creating or editing a user opens a dialog with the same fields:

* **First Name** and **Last Name** — required.
* **Email** — required. Where the invitation is sent and how the user signs in.
* **Phone Number** — optional, with a country code.
* **Role** — required. One or more roles from the list in [Roles and spaces](#roles-and-spaces). This is what determines what the user can do.

<figure><img src="/files/aZVvSGFPqMizja43qGBv" alt="The Role field in the Create/Edit User dialog, with a multi-select list of available roles"><figcaption><p>Assigning one or more roles when creating or editing a user.</p></figcaption></figure>

{% hint style="info" %}
Creating a user sends a real invitation, and changing a role changes what that person can access. Set roles deliberately.
{% endhint %}

## Teams

Teams group members together, scope them to spaces, and grant role-based permissions on specific agents. Open **Account Settings → Teams**. Each team is listed with its **Team** name, its **Spaces**, its **Members** count, and a per-row **Actions** menu. Teams are also what [Human Review](broken://pages/691d9dcfaa31c470fa503aa01848ea2206a236ce#human-review) assignments flow through.

### Create a team

**+ Create Team** opens a two-step dialog.

{% stepper %}
{% step %}

## Step 1: Set up the team

* **Team name** — a label for the team (for example, *Lending Ops*).
* **Spaces** — which products the team operates in: **Studio**, **Console**, or **Control Center**.
* **Members** — add people from the account and set each member's role; you can change these later. **Invite someone new** adds a person who isn't yet on the account.

Click **Continue** to move to Step 2.
{% endstep %}

{% step %}

## Step 2: Grant agent permissions

Grant the team role-based permissions on specific agents.
{% endstep %}
{% endstepper %}

<figure><img src="/files/03FKsaAPJUcoZhtnbENQ" alt="The Create Team dialog, showing team name, spaces, and member fields"><figcaption><p>Step 1 of creating a team — name, spaces, and members.</p></figcaption></figure>

## API Keys

API Keys are credentials for programmatic access to the platform. Open **Account Settings → API Keys**. Search by name or key ID, and use **+ Create API Key** to issue one.

### Create an API key

**+ Create API Key** opens a dialog:

* **Key name** — a label for the key (for example, *Reporting integration*).
* **Select Permissions** — required. A searchable checklist of the permissions to grant — for example, **Create Account**, **Manage Accounts**, **Create User**, **View Users**, **Define Roles**, **Manage Brands**, and **Create Workspace**. Grant a key only the permissions it needs.

Click **Create Key** to issue it. The button stays disabled until the key has a name and at least one permission.

<figure><img src="/files/CqpGJu7s2gXLw8732ucG" alt="The Create API Key dialog, with a key name field and a searchable permissions checklist"><figcaption><p>Creating an API key with a scoped set of permissions.</p></figcaption></figure>

{% hint style="warning" %}
An API key is a credential that can carry account-management permissions, such as creating users or defining roles. Scope each key to the minimum it needs, and store the key value securely — it grants whatever access you selected.
{% endhint %}

## Notes

* **Roles are cross-cutting**: a user can hold several at once, and roles are scoped to the Studio, Console, and Control Center spaces plus account-wide.
* **Team creation** is a two-step flow; the second step grants per-agent permissions, so a team isn't fully configured until both steps are complete.
* **API-key permissions** are granular and can be account-wide — review the selected permissions before issuing a key.

## Related

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

{% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/9cd0c4d868b97b43a234c8d0ca5c3690fa58decb" %}
[Evaluation & Quality](/governance/evaluation-and-quality.md)
{% endcontent-ref %}

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

{% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/d94f394409e2ca941f1b4be707fbb3cb9db99a62" %}
[Credits & Tokens](/governance/billing.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/governance/account-settings.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.