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

# Accounts

Understand the account boundary and find its Control Center management areas.

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. Use the linked Control Center areas to administer it.

### 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. 

Tenant administrators create and manage accounts. 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 %}

### 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="/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="/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="/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="/control-center/cost-control/usage-limits.md">Usage Limits</a></td></tr></tbody></table>


---

# 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/accounts.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.