> 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/accounts.md).

# Accounts

Understand the account boundary, switch accounts, and create, rename, or delete accounts.

A tenant is your Qore deployment for an organization. It holds one or more accounts.

An account is the operating boundary for a business unit within that tenant. It separates projects, membership, governance, and usage from other accounts.

Use this page to understand the account boundary, switch between accounts, and manage accounts in **Org Settings**. Use the linked Control Center areas to administer an account.

### Account at a glance

| Account area      | What it controls                                                         |
| ----------------- | ------------------------------------------------------------------------ |
| Projects          | The apps, agents, knowledge bases, and design systems your teams create. |
| People and access | Members, teams, roles, and API keys.                                     |
| Governance        | Account-wide monitoring, audit, policy, and quality controls.            |
| Usage             | Credit consumption and the spending controls that apply to the account.  |

### Working with accounts

Accounts help you separate work that needs independent ownership, access, or cost control. Each account contains its own projects and members.

An **Organisation Admin** creates, renames, and deletes accounts from **Org Settings**. Account names are unique within the tenant.

{% hint style="info" %}
**Good to remember**

An account is not the same as a project. Use accounts for business boundaries. Use projects for related apps, agents, knowledge bases, and design systems.
{% endhint %}

### Switch accounts

The account and project switcher sits at the top of the Console sidebar. It shows the current account above the current project.

1. Open the switcher.
2. Under **Accounts**, select an account. A check mark shows the current account.

The **Projects** list below it changes to the selected account's projects. See [Projects](/ai-workbench-qore/console/projects.md) to choose, pin, or create a project.

### Manage accounts in Org Settings

Only **Organisation Admin** carries **Create an account**, the capability that opens the **Accounts** page and its **Create Account**, **Update**, and **Delete** actions. See [Roles](/ai-workbench-qore/control-center/admin/roles.md).

1. Select your avatar at the top right, then select **Org Settings**.
2. In the left sidebar, select **Accounts**.

The sidebar also shows **Brands** and **Roles and Capabilities**.

The **Accounts** page lists every account in the tenant with its **Name**, **Created At** date, and **Status**. Filter by **All Statuses**, **Active**, or **Deactivated**, or search by name. Each row's **Actions** menu (⋮) holds **Usage Limits**, **Update**, and **Delete**.

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-77121ce83ddc6918e5056fd0020dabcfb9fb1d74%2Fqore_control-center_org-settings-accounts-actions_rounded_shadow.png?alt=media" alt="The Org Settings Accounts page: Accounts, Brands, and Roles and Capabilities in the sidebar, the Create Account button, an All Statuses filter and search box, and an accounts table with Name, Created At, Status, and Actions columns, with a row&#x27;s actions menu open on Usage Limits, Update, and Delete"><figcaption><p>The Accounts page in Org Settings, with a row's actions menu open.</p></figcaption></figure>

#### Create an account

1. Select **Create Account**.
2. Enter a **Name**.
3. Select **Create**.

The account appears in the list with the status **Active**, and under **Accounts** in the Console switcher.

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-e5bbd366c2ed32b52349e7e360c7b4670ab13935%2Fqore_control-center_org-settings-create-account_rounded_shadow.png?alt=media" alt="The Create Account dialog with a required Name field and Cancel and Create buttons"><figcaption><p>Create Account.</p></figcaption></figure>

#### Rename an account

1. In the account's row, open the actions menu (⋮) and select **Update**.
2. Change the **Name**.
3. Select **Update**. The button is unavailable until the name changes.

#### Set usage limits for an account

In the account's row, open the actions menu (⋮) and select **Usage Limits**. The dialog configures credit usage limits and alerts for that account. This action needs **Set credit limits**. For the fields, see [Usage Limits](/ai-workbench-qore/control-center/cost-control/usage-limits.md).

#### Delete an account

1. In the account's row, open the actions menu (⋮) and select **Delete**.
2. Qore asks *Are you absolutely sure?* and warns: *This action cannot be undone. This will permanently delete this account.* Select **Delete** to confirm.

### Manage this account

Use the relevant Control Center area for each account-management task.

<table data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>Admin</strong></td><td>Manage account members, teams, roles, and API keys.</td><td><a href="/ai-workbench-qore/control-center/admin.md">Admin</a></td></tr><tr><td><strong>Cost Control</strong></td><td>Review credit use and manage spending controls.</td><td><a href="/ai-workbench-qore/control-center/cost-control.md">Cost Control</a></td></tr><tr><td><strong>Credit Usage</strong></td><td>Review consumption trends and transaction history.</td><td><a href="/ai-workbench-qore/control-center/cost-control/credit-usage.md">Credit Usage</a></td></tr><tr><td><strong>Usage Limits</strong></td><td>Set credit spending caps and threshold alerts.</td><td><a href="/ai-workbench-qore/control-center/cost-control/usage-limits.md">Usage Limits</a></td></tr></tbody></table>

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% 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/accounts.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.
