> 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/start-here/org-settings/accounts.md).

# Accounts

Create accounts, set credit limits, and receive usage threshold alerts.

An account is a business unit inside your organization, not the organization itself — it divides the organization's Qore platform usage into separately billed units. Each account has its own credit limits and alerts.

| Topic              | Details                                                                               | Outcome                                    |
| ------------------ | ------------------------------------------------------------------------------------- | ------------------------------------------ |
| Access             | Super admins can manage tenant accounts at `/platform/super-admin-settings/accounts`. | Keep tenant usage organized.               |
| Account management | Create accounts, change account names, and find accounts by name or status.           | Maintain named accounts.                   |
| Access management  | Create users, assign roles, and create teams with users.                              | Manage tenant access.                      |
| Usage control      | Set limits and alerts for each account.                                               | Cap consumption or receive warning emails. |

## Overview

Organization-level accounts are managed by super admins. Within an account, super admins can create users, assign roles, and create teams with users.

An account's scope stops at its own boundary — it does not reach the rest of the organization. It tracks credit usage for platform billing, scoped to itself. Super admins can set per-period consumption caps and alerts per account.

### Key concepts

| Concept     | Meaning                                                               | Key details                                                                                                                       |
| ----------- | --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Account     | A business unit inside the organization, with its own billable usage. | Names are unique within the organization. Status is currently active. Each account records its creation time, limits, and alerts. |
| Credit      | Qore's consumption unit.                                              | Every agent and model call deducts a whole number of credits. Accounts don't set credit prices or budgets.                        |
| Usage limit | A per-account credit cap for a period.                                | Qore rejects requests that exceed the cap.                                                                                        |
| Usage alert | An email notification threshold.                                      | Every **Account Admin** role holder on the account receives an email — not every super admin. Alerts never reject requests.       |
| Duration    | An evaluation period.                                                 | Choose `Daily`, `Weekly`, or `Monthly`.                                                                                           |
| Metric type | An alert threshold method.                                            | Choose `Absolute Credits` or `Percentage of Limit`.                                                                               |

> Periods reset on UTC calendar boundaries. Daily resets at 00:00 UTC. Weekly resets at 00:00 UTC on Monday. Monthly resets at 00:00 UTC on the first day.

`Percentage of Limit` uses the account's usage limit with the same duration.

## Find and manage accounts

The account directory lists every tenant account. It shows each account's name, creation time, status, and management options. Newer accounts appear first.

When no account matches the query and status, Qore shows `No results.`. Clear the query or reset the status to restore accounts.

### Create an account

Create an account to separate a workload's credit consumption.

{% stepper %}
{% step %}

### Start account creation

From the account directory, begin account creation.
{% endstep %}

{% step %}

### Provide a name

Enter a unique tenant-wide display name. You can't save an empty name.
{% endstep %}

{% step %}

### Save the account

Save the account.
{% endstep %}
{% endstepper %}

Qore adds the account with active status and a creation timestamp. New accounts have no limits or alerts. Until you add limits, only platform-level limits apply.

### Rename an account

Start a rename from the account's management options. Change the existing name, then save it. The name must remain unique within the tenant.

The account keeps its status, creation time, limits, and alerts. Discarding or closing the change keeps the existing name.

## Set usage limits

A usage limit caps an account's Qore platform credits during a period. Qore evaluates limits before deducting credits. It rejects a request that would exceed a limit.

Platform-level limits also apply. The stricter limit takes precedence. Adding a limit affects future requests, but credits already consumed count toward the new cap. If usage already exceeds the cap, Qore rejects requests until the period resets.

{% hint style="info" %}
Accounts have no limits by default. Add a limit to prevent unexpected consumption.
{% endhint %}

### Add a limit

Open the account's management options and start a usage limit. Then provide the required values.

| Value        | Accepted input                  | Effect                                                 |
| ------------ | ------------------------------- | ------------------------------------------------------ |
| Duration     | `Daily`, `Weekly`, or `Monthly` | Defines the evaluation period. `Daily` is the default. |
| Credit limit | A positive integer              | Sets the maximum credits for that period.              |

Save the limit, or discard it. Both values are required.

You can add several limits to an account. Qore evaluates every limit for each request. The strictest applicable limit takes precedence.

{% tabs %}
{% tab title="Daily" %}
Use for unpredictable or burst-heavy workloads. A daily cap bounds consumption for one day.
{% endtab %}

{% tab title="Weekly" %}
Use when consumption follows a weekly work pattern.
{% endtab %}

{% tab title="Monthly" %}
Use for billing cycles and longer budget horizons.
{% endtab %}
{% endtabs %}

Combine durations for production workloads. A daily cap protects against spikes. A monthly cap controls total spending.

## Set usage alerts

An alert emails every **Account Admin** role holder on the account — not every super admin in the organization — when account usage crosses a threshold. Alerts notify only. Usage limits enforce consumption caps.

### Add an alert

Open the account's usage limits and start a new alert. Then set these values:

| Value       | Accepted input                              | Effect                                                          |
| ----------- | ------------------------------------------- | --------------------------------------------------------------- |
| Duration    | `Daily`, `Weekly`, or `Monthly`             | Defines the threshold period. `Daily` is the default.           |
| Metric type | `Absolute Credits` or `Percentage of Limit` | Defines how Qore measures the threshold.                        |
| Threshold   | Positive integer                            | Provide a credit count or percentage, based on the metric type. |

Save the alert, or discard it. Every value is required.

{% tabs %}
{% tab title="Absolute Credits" %}
Enter a positive credit count. Qore sends an email when usage reaches that count. This alert works without a matching usage limit.
{% endtab %}

{% tab title="Percentage of Limit" %}
Enter a percentage. Set a usage limit with the same duration first. Without one, Qore has no matching limit to measure.
{% endtab %}
{% endtabs %}

An alert sends at most one email per period. Repeated threshold crossings don't send another email until the period resets. You can add multiple alerts. Qore evaluates each one independently.

### Related

<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>Cost Management</td><td>Track platform credit consumption and control spending.</td><td><a href="/control-center/cost-control.md">Cost Control</a></td></tr><tr><td>Credit usage</td><td>See consumption trends and transaction history.</td><td><a href="/control-center/cost-control/credit-usage.md">Credit Usage</a></td></tr><tr><td>Usage Limits</td><td>Set platform credit caps and threshold alerts.</td><td><a href="/control-center/cost-control/usage-limits.md">Usage Limits</a></td></tr><tr><td>Branding</td><td>Manage tenant branding and related configuration.</td><td><a href="/start-here/org-settings/brands.md">Brands</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/start-here/org-settings/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.