> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/maiagent-user-guide/en/org/overview/organization-overview.md).

# Organization Overview

View your organization's plan, usage, enabled features, and common management shortcuts on one page

Organization Overview is the first page you see when you open <mark style="color:blue;">Organization Settings</mark>. It brings together basic organization information, plan history, this month's usage, enabled advanced features, and common management shortcuts so you can see your organization's overall status at a glance.

## How to Access <a href="#how-to-access" id="how-to-access"></a>

In the left menu, click <mark style="color:blue;">Organization Settings</mark> → <mark style="color:blue;">Organization Overview</mark>.

***

## Top of the Page: Organization Information <a href="#org-info" id="org-info"></a>

The top of the page shows basic information about this organization:

| Item                                                  | Description                                                                                                                                            |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Organization Name                                     | To change the name, click <mark style="color:blue;">Edit Organization</mark> in the upper right. See [Edit Organization](#edit-organization)           |
| Plan                                                  | Shows the current subscription plan (for example, Enterprise)                                                                                          |
| Organization ID                                       | The organization's unique identifier. Click the icon next to it to copy it with one click. You may need it for integrations or when contacting support |
| Created At                                            | The date the organization was created                                                                                                                  |
| <mark style="color:blue;">Plan Available Until</mark> | Shows the last usable date and the number of days remaining from today (including today), helping you renew in advance                                 |

***

## Edit Organization <a href="#edit-organization" id="edit-organization"></a>

Use the <mark style="color:blue;">Edit Organization</mark> page to change the organization's name, logos, theme color, and rules such as disabling Chinese models, enabling channels for new assistants by default, and resource limits. Only roles with Organization Overview permission can see this button. Organization owners have this permission by default. See [Role and Permission Management](https://docs.maiagent.ai/maiagent-user-guide/en/org/roles/role-permission.md).

1. Go to <mark style="color:blue;">Organization Settings</mark> → <mark style="color:blue;">Organization Overview</mark>, then click <mark style="color:blue;">Edit Organization</mark> at the top right of the page.

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-d15fdb58ba38e736deac20098bdcda4bc834fa1f%2Forg-edit-entry-button.png?alt=media" alt="Organization information row at the top of Organization Overview: Enterprise plan badge and creation date, with a blue Edit Organization button and Plan Available Until date on the right; organization name, logo, and ID are masked"><figcaption><p>The Edit Organization button is at the top right of Organization Overview (organization name, logo, and ID are masked)</p></figcaption></figure>

2. The page has two tabs. <mark style="color:blue;">Basic Information and Appearance</mark> opens by default:

| Tab                                                               | What You Can Do                                                                                                                                                                                                                                                                                                                 |
| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <mark style="color:blue;">Basic Information and Appearance</mark> | Change the organization name. Enterprise organizations can also configure [Organization Branding](#org-branding) (logos and theme color). The <mark style="color:blue;">Application Information</mark> below (company name, business registration number, and contact phone number) is read-only. Contact MaiAgent to change it |
| <mark style="color:blue;">Rules and Resource Limits</mark>        | <mark style="color:blue;">Disable Chinese Models</mark> (see [Model Access Permissions](https://docs.maiagent.ai/maiagent-user-guide/en/org/model-access.md#toggle-china-models)), [Enable Channels and API Integration for New Assistants by Default](#new-agent-channel-default), and [Resource Limits](#resource-limits)     |

3. After making changes, click <mark style="color:blue;">Save</mark> at the bottom right of that tab. Each tab saves independently. <mark style="color:blue;">Save</mark> is disabled when there are no changes. To return to Organization Overview, click the <mark style="color:blue;">Organization Overview</mark> link at the top of the page.

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-53a323e3600eb42340f5c83ad81ec9b45ee6eadd%2Forg-edit-basic-tab.png?alt=media" alt="Basic Information and Appearance tab on the Edit Organization page: name field, explanation that system settings apply when unset, square and horizontal logo upload fields, theme color field, read-only application information table, and Save button; name and application information values are masked"><figcaption><p>The Basic Information and Appearance tab for an Enterprise organization (name and application information values are masked)</p></figcaption></figure>

{% hint style="info" %}
If you switch tabs or leave the page with unsaved changes, an Unsaved Changes dialog appears first. Choose <mark style="color:blue;">Stay and Continue Editing</mark> to return and save, or <mark style="color:blue;">Leave Without Saving</mark> to discard your changes.
{% endhint %}

***

## Check the Plan's Last Usable Day <a href="#plan-last-usable-day" id="plan-last-usable-day"></a>

When planning a renewal, organization administrators can open <mark style="color:blue;">Organization Overview</mark>, check <mark style="color:blue;">Plan Available Until</mark> at the top, then compare it with the current plan and <mark style="color:blue;">N Days Remaining</mark> in <mark style="color:blue;">Plan History</mark>. Both use the last usable day as their reference so administrators know which dates the service is still available.

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-3b59222fb535b9ec132e513f6ac133cd19eef055%2Forg-plan-last-usable-day.png?alt=media" alt="Plan Available Until section showing the last usable date with the number of usable days below"><figcaption><p>The date is the last usable day; the remaining day count includes today and updates as the date changes</p></figcaption></figure>

{% hint style="info" %}
Plan Available Until shows the last usable date, rather than the time the service stops. If the plan expires early the next morning, this shows the previous day. The remaining day count starts today and includes today. The actual stop time still follows the plan settings; if it expires during the day, service may stop partway through that day. Plans without an expiration date show <mark style="color:blue;">Permanent</mark> in Plan History.
{% endhint %}

***

## Enable Channels for New Assistants by Default <a href="#new-agent-channel-default" id="new-agent-channel-default"></a>

On the <mark style="color:blue;">Rules and Resource Limits</mark> tab of <mark style="color:blue;">Edit Organization</mark>, <mark style="color:blue;">Enable Channels and API Integration for New Assistants by Default</mark> determines whether the web Widget and API integration are enabled immediately for Agents created or duplicated in this organization from then on:

* **Off (platform default)**: New Agents have only internal chat enabled. The web Widget and API integration start disabled, and a member must enable them manually on the Agent's <mark style="color:blue;">Channels</mark> tab.
* **On**: The web Widget and API integration are enabled as soon as a new Agent is created.
* **Admin console chat is unaffected**: Internal chat is always enabled.
* **Existing Agents are unaffected**: Changes apply only to Agents created or duplicated afterward. Existing Agents retain their channel status.

Members can still adjust each option in the <mark style="color:blue;">Create AI Assistant</mark> dialog. This setting only determines the initial values of the two switches in <mark style="color:blue;">Channel Activation</mark>. See [Create an Agent: Configure Channel Activation](https://docs.maiagent.ai/maiagent-user-guide/en/build/agent/setup.md#channel-activation).

### How to Configure <a href="#new-agent-channel-default-how-to" id="new-agent-channel-default-how-to"></a>

A role with Organization Overview permission is required to access this page and make changes. Organization owners have it by default. Unlike Disable Chinese Models, this setting is not restricted to organization owners. For permissions, see [Role and Permission Management](https://docs.maiagent.ai/maiagent-user-guide/en/org/roles/role-permission.md).

1. Go to <mark style="color:blue;">Organization Settings</mark> → <mark style="color:blue;">Organization Overview</mark>, click <mark style="color:blue;">Edit Organization</mark>, and switch to <mark style="color:blue;">Rules and Resource Limits</mark>.
2. Turn <mark style="color:blue;">Enable Channels and API Integration for New Assistants by Default</mark> on or off.
3. Click <mark style="color:blue;">Save</mark>.

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-3e4633f037bb5df7951b4345111b536108ce3eeb%2Forg-edit-rules-switches.png?alt=media" alt="Two switches in the rules section: Disable Chinese Models and Enable Channels and API Integration for New Assistants by Default, both off and each accompanied by explanatory text"><figcaption><p>The rules section of the Rules and Resource Limits tab; both switches are off in this image</p></figcaption></figure>

For example, a company's IT director wants all new Agents tested internally before they become publicly available. He checks that this switch remains off in <mark style="color:blue;">Edit Organization</mark>. When colleagues later open <mark style="color:blue;">Create AI Assistant</mark>, <mark style="color:blue;">Channel Activation</mark> shows <mark style="color:blue;">Internal Chat Only</mark>, with both the web Widget and API integration switches off. Colleagues can enable them when they are ready to open access externally.

{% hint style="info" %}
This switch appears only on the <mark style="color:blue;">Edit Organization</mark> page for existing organizations. It is not available in the dialog for creating an organization.
{% endhint %}

***

## Organization Branding: Logos and Theme Color <a href="#org-branding" id="org-branding"></a>

Enterprise organizations can customize the admin console with their company's logos and primary color. After members sign in and enter the organization, the logo in the upper left and interface elements that support branding, such as buttons, selection states, links, and key numbers, use the organization's settings.

### How to Configure <a href="#org-branding-how-to" id="org-branding-how-to"></a>

A role with Organization Overview permission is required to access this page and make changes. Organization owners have it by default. See [Role and Permission Management](https://docs.maiagent.ai/maiagent-user-guide/en/org/roles/role-permission.md).

1. Go to <mark style="color:blue;">Organization Settings</mark> → <mark style="color:blue;">Organization Overview</mark>, click <mark style="color:blue;">Edit Organization</mark>, and stay on <mark style="color:blue;">Basic Information and Appearance</mark>.
2. Configure the following items and click <mark style="color:blue;">Save</mark>. You cannot save while a logo is uploading; wait until the upload finishes.

<table><thead><tr><th width="150">Setting</th><th width="220">Recommended Specifications</th><th>Where It Appears</th></tr></thead><tbody><tr><td>Square Logo</td><td>1:1 ratio, 128×128 or 256×256 px</td><td>Organization icon at the top of Organization Overview</td></tr><tr><td>Horizontal Logo</td><td>3:1 ~ 5:1 ratio, at least 32 px tall</td><td>Logo at the top left of the left menu; on mobile, it appears in the top bar and at the top of the expanded menu</td></tr><tr><td>Theme Color</td><td>Use the color picker, click a preset swatch, or enter a color code directly (for example, <code>#0960bd</code>); leave blank to use system settings</td><td>Accent color for admin console buttons, selection states, links, and key numbers. The Button and Selection preview labels next to the field reflect the color immediately</td></tr></tbody></table>

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-adff3307b57743dabe8df146ef4fbe69cac1df3c%2Forg-branding-square-field.png?alt=media" alt="Square logo upload field labeled with a 1:1 ratio"><figcaption><p>The square logo upload field</p></figcaption></figure>

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-611b0f5ac91e223dfaa90acdcffe0da39588b4e5%2Forg-branding-horizontal-field.png?alt=media" alt="Horizontal logo upload field labeled with a 3:1 to 5:1 ratio"><figcaption><p>The horizontal logo upload field</p></figcaption></figure>

No logo appears when the desktop left menu is collapsed to a narrow sidebar.

If no logos are uploaded, the platform's original logo appears in the upper left, and the first character of the organization name appears at the top of Organization Overview. This is what Use System Settings When Unset above the branding fields means.

### Leave the Theme Color Blank to Use the System Primary Color <a href="#org-theme-color-fallback" id="org-theme-color-fallback"></a>

Like logos, the theme color is optional. Organizations without a theme color use the site's system primary color for admin console accents. Organizations with an explicit color retain their own. For white-label or self-hosted site customers, this means there is no need to configure each organization's theme color individually: new organizations use the site's brand color from the start.

To return an organization with a configured theme color to system settings:

1. Go to <mark style="color:blue;">Organization Settings</mark> → <mark style="color:blue;">Organization Overview</mark>, click <mark style="color:blue;">Edit Organization</mark>, and stay on <mark style="color:blue;">Basic Information and Appearance</mark>.
2. Click <mark style="color:blue;">Clear (Use System Settings)</mark> to the right of the Theme Color code field. The color picker and Button and Selection previews immediately switch to the color that will apply once the field is cleared.
3. Click <mark style="color:blue;">Save</mark>. Admin console accents revert to the system primary color.

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-c772484133203b363b7667eb3646caafbc16fdd0%2Forg-theme-color-field.png?alt=media" alt="Theme Color field with a clear icon to the right of the color code and Button and Selection previews farther right"><figcaption><p>The clear icon and two previews for the Theme Color field; the image is cropped to the settings being introduced</p></figcaption></figure>

{% hint style="info" %}
Organizations that already had a theme color before the upgrade are treated as having an explicit setting, so their appearance does not change after the upgrade. They switch to system settings only when the color is deliberately cleared. If the site's system settings also have no primary color, the admin console uses the platform's built-in default color.
{% endhint %}

### Scope <a href="#org-branding-scope" id="org-branding-scope"></a>

{% hint style="info" %}
**Organization branding applies only to the admin console after sign-in**

The sign-in page, browser tab icon and title, and system notification emails still use platform branding. When these appear, the system does not yet know which organization the user belongs to, so it cannot apply organization settings.
{% endhint %}

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-4e0aceec863413e36fdc025e7cca36ff8dfcc817%2Forg-branding-login-panel.png?alt=media" alt="Production sign-in panel with the platform logo above an empty company email field and Continue button"><figcaption><p>The sign-in page does not use organization branding. The organization's logos and theme color apply after members sign in and enter the organization</p></figcaption></figure>

* **Plan**: Square logos, horizontal logos, and theme colors are Enterprise features. Other plans can only change the name on <mark style="color:blue;">Edit Organization</mark> and see This plan does not support organization-level branding; system settings will be used. Contact your sales representative to upgrade.
* **Who it applies to**: Settings belong to the organization. When a member switches organizations, they see the other organization's branding.
* **External chat windows have separate settings**: Web chat windows on your company website for customers are configured in each channel's [Appearance Settings](https://docs.maiagent.ai/maiagent-user-guide/en/build/conversation-settings/platform-settings/appearance-settings.md) and do not follow organization branding. All plans can configure the logo, avatar, chat button icon, and colors. The Support Logo at the bottom of the chat window and Show Support Branding switch are Enterprise features.

***

## Resource Limits: Attachment Size and Timeouts <a href="#resource-limits" id="resource-limits"></a>

The <mark style="color:blue;">Resource Limits</mark> table at the bottom of <mark style="color:blue;">Rules and Resource Limits</mark> lets organization administrators adjust three limits within their plan's allowances without asking MaiAgent to do it:

| Item                                                             | What It Controls                                                                                                                                                         | Minimum Value |
| ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------- |
| <mark style="color:blue;">Chat Attachment per File (MB)</mark>   | Maximum size of a single attachment (document or audio file) that members upload in chat                                                                                 | 1 MB          |
| <mark style="color:blue;">File Parsing Timeout (Seconds)</mark>  | Maximum wait for a single conversion step when parsing knowledge base files or chat attachments; exceeding it causes a timeout                                           | 60 seconds    |
| <mark style="color:blue;">API Tool Call Timeout (Seconds)</mark> | Maximum wait for a response when an Agent calls an [API tool](https://docs.maiagent.ai/maiagent-user-guide/en/build/tools.md#api-tool); exceeding it interrupts the call | 5 seconds     |

Each row has four columns:

* <mark style="color:blue;">Plan Limit</mark>: The maximum allowed by the organization's plan. Contact MaiAgent to adjust the plan if you need a higher value.
* <mark style="color:blue;">Organization Setting</mark>: The organization's custom value. Blank means no custom value; the plan limit applies directly.
* <mark style="color:blue;">Effective Value</mark>: The value actually applied. A label next to it identifies the source as <mark style="color:blue;">Plan Limit</mark> or <mark style="color:blue;">Organization Setting</mark>.
* <mark style="color:blue;">Reset to Plan Limit</mark>: Clears the organization setting and returns to the plan limit.

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-6bdc52fc773246e1584bae53fe59ed0828515f33%2Forg-edit-rules-tab.png?alt=media" alt="Rules and Resource Limits tab: two rule switches above a resource limits table, with the chat attachment per-file plan limit set to 10, organization setting set to 9, and effective value of 9 labeled Organization Setting; the other two rows use plan limits"><figcaption><p>After setting chat attachments to 9 MB per file, Effective Value is labeled Organization Setting; the other two rows continue to use plan limits</p></figcaption></figure>

### Example: Limit Members' Attachment Upload Sizes <a href="#resource-limits-scenario" id="resource-limits-scenario"></a>

An IT director notices that colleagues often drop scanned files of several MB directly into chat, taking a long time to parse and consuming resources. She wants large files placed in the knowledge base instead. She opens <mark style="color:blue;">Rules and Resource Limits</mark> in <mark style="color:blue;">Edit Organization</mark>, enters 5 as the organization setting for <mark style="color:blue;">Chat Attachment per File (MB)</mark>, and clicks <mark style="color:blue;">Save</mark>. The confirmation dialog shows the old and new attachment limits and warns that members' attachments over 5 MB will be blocked. She clicks <mark style="color:blue;">Confirm</mark>. When colleagues later upload files over 5 MB in chat, a message says the file exceeds 5 MB and must be parsed using the knowledge base. To relax the limit later, click <mark style="color:blue;">Reset to Plan Limit</mark> and save.

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-0fcaa7dd0bdbf41fe552acca8b1be85f4fa1629c%2Forg-resource-limits-upload-blocked.png?alt=media" alt="Use the knowledge base to parse this file dialog: example filename 示範附件-9.5MB.txt, explanation that the file exceeds 9 MB and must be parsed using the knowledge base, with Got It and Go to Knowledge Base buttons below"><figcaption><p>The message members see when uploading a file over the limit in chat; here the organization setting is 9 MB and the uploaded file is 9.5 MB</p></figcaption></figure>

### How to Adjust <a href="#resource-limits-how-to" id="resource-limits-how-to"></a>

The same permissions as Edit Organization apply: a role with Organization Overview permission is required.

1. Go to <mark style="color:blue;">Organization Settings</mark> → <mark style="color:blue;">Organization Overview</mark>, click <mark style="color:blue;">Edit Organization</mark>, and switch to <mark style="color:blue;">Rules and Resource Limits</mark>.
2. Enter an integer in <mark style="color:blue;">Organization Setting</mark> for the item you want to adjust. To return to the plan limit, click <mark style="color:blue;">Reset to Plan Limit</mark> on that row or clear the input.
3. Click <mark style="color:blue;">Save</mark>. A <mark style="color:blue;">Confirm Resource Limit Changes</mark> dialog first lists the old and new effective values and the impact of each change. Review them, then click <mark style="color:blue;">Confirm</mark>.

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-1a458ca766686f0b6dbc2acb05dd13bcd42b1430%2Forg-resource-limits-confirm-lower.png?alt=media" alt="Confirm Resource Limit Changes dialog: Chat Attachment per File (MB) changes from 10 to 5, with an explanation that attachments over 5 MB will be blocked and Cancel and Confirm buttons below"><figcaption><p>When lowering a limit, the confirmation dialog explains which cases will be blocked or time out afterward</p></figcaption></figure>

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-49ba27de12c0a9b83e87db4f6c961461c7bb13af%2Forg-resource-limits-confirm-raise.png?alt=media" alt="Confirm Resource Limit Changes dialog: Chat Attachment per File (MB) changes from 9 to 10, explaining that larger attachments can be uploaded and larger files take longer to parse, with notes that increases within the plan incur no extra charge and uploads or parsing in progress are unaffected"><figcaption><p>When raising a limit, the confirmation dialog also states that increases within the plan incur no extra charge</p></figcaption></figure>

Clicking <mark style="color:blue;">Cancel</mark> saves no settings. Entered values stay on the page so you can revise and save them later. Rule switches and resource limits share one <mark style="color:blue;">Save</mark> button: if both have changes, they are saved together. If rules save successfully but resource limits fail, a message says Rules saved, but resource limits could not be saved. Please try again later. Click <mark style="color:blue;">Save</mark> again.

### Input Validation <a href="#resource-limits-validation" id="resource-limits-validation"></a>

If an input is invalid, red text below the field explains why, and <mark style="color:blue;">Save</mark> is disabled:

* Above the plan limit: Exceeds the plan limit of … Contact MaiAgent to adjust your plan if you need a higher value
* Below the minimum: Cannot be less than …
* Not an integer: Enter an integer

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-96aec28e69c68b660174cc432591aa4b51ecb531%2Forg-resource-limits-error.png?alt=media" alt="Resource limits table with 30 entered as the organization setting for file parsing timeout; the input is red with Cannot be less than 60, and Save at the bottom right is disabled"><figcaption><p>Entering 30 seconds for file parsing timeout shows Cannot be less than 60 and prevents saving</p></figcaption></figure>

{% hint style="info" %}

* **When the plan limit is lowered**: If the plan limit later falls below the organization setting, the plan limit takes precedence. That row shows a yellow warning: Organization setting exceeds the current plan limit; the plan limit has been applied. This is only a reminder and does not prevent saving other rows. The organization setting is retained and takes effect again if the plan limit is restored.
* **Work in progress is unaffected**: Adjustments apply only to subsequent uploads, parsing, and API tool calls.
* **Web chat visitors**: When an organization lowers the attachment limit, visitors who are not signed in to the web chat window are also subject to it. Higher limits apply only to signed-in members.
  {% endhint %}

***

## Plan History <a href="#plan-lifecycle" id="plan-lifecycle"></a>

Plan History presents the organization's **past, current, and scheduled future plans** on a timeline:

* **Scroll horizontally** through the timeline. A Today marker shows the current position; click <mark style="color:blue;">Back to Today</mark> if you scroll far away
* Each plan shows its name and validity period. Trial plans have a Trial badge, plans with no expiration show Permanent, and active plans show <mark style="color:blue;">N Days Remaining</mark>
* Older records are collapsed by default when there are many. Click <mark style="color:blue;">Show N Earlier Records</mark> to expand them

***

## Usage Overview (This Month) <a href="#usage-overview" id="usage-overview"></a>

Three cards show this month's key usage figures:

| Card                            | Content                                                                                                                                   |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Current AI Assistant Count**  | Number of Agents created. Plans with a limit show Used / Limit; unlimited plans show No Usage Limit                                       |
| **Conversations This Month**    | Total number of conversation messages this month                                                                                          |
| **Knowledge Base Storage Used** | Storage currently occupied by the knowledge base. Organizations not billed in Credits also see available capacity and the percentage used |

When the plan limits the number of AI assistants, the card also shows these messages below the count:

| Message                                                              | Meaning                                                                                                                                                                                                                     |
| -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <mark style="color:blue;">N More Can Be Created</mark>               | How many more Agents can be created before reaching the limit                                                                                                                                                               |
| <mark style="color:blue;">N More ○○ Assistants Can Be Created</mark> | If the plan allows only certain response modes, also identifies which modes can still be created                                                                                                                            |
| <mark style="color:blue;">Limit Reached</mark>                       | All slots are used. Delete existing Agents or upgrade the plan first                                                                                                                                                        |
| <mark style="color:blue;">N Additional Existing Assistants</mark>    | These Agents use response modes outside those currently allowed by the plan (for example, created before a downgrade). They are retained as read-only and do not count toward the limit; the next line lists counts by mode |

{% hint style="info" %}
For more complete historical trends and details, go to <mark style="color:blue;">Organization Settings</mark> → <mark style="color:blue;">Usage Statistics</mark>.
{% endhint %}

***

## Advanced Features and Credits <a href="#advanced-features-and-credits" id="advanced-features-and-credits"></a>

### Advanced Features <a href="#advanced-features" id="advanced-features"></a>

Advanced Features lists the organization's enabled advanced capabilities in a fixed order:

| Feature                               | Notes                    |
| ------------------------------------- | ------------------------ |
| Call Center                           | Hidden when not enabled  |
| AI Voice Assistant                    | Beta                     |
| Meeting Notes                         |                          |
| Hook Message Interception / Rewriting | Enterprise feature       |
| AI Gateway                            | Enterprise feature, Beta |
| Teams (Agent Teams)                   | Beta                     |
| Custom Vector Database Connection     | Enterprise feature       |

Enabled features appear normally; disabled features appear gray, and Enterprise-only features carry an Enterprise badge. Features still in Beta (currently AI Voice Assistant, AI Gateway, and Teams) have a <mark style="color:blue;">Beta</mark> label next to their names. Hovering over a disabled Beta feature shows Beta feature. Contact your sales representative to enable it (for Enterprise-only features, it shows Enterprise only. Contact your sales representative to enable it).

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-ac04f426ad843b46b88703191cdc1a1bd1b095f0%2Frelease-stage-badge-advanced-features.png?alt=media" alt="Advanced Features section in Organization Overview: AI Voice Assistant, AI Gateway, and Teams (Agent Teams) have Beta labels; Custom Vector Database Connection is gray with an Enterprise badge"><figcaption><p>Advanced Features section: features in Beta have a Beta label next to their names</p></figcaption></figure>

{% hint style="info" %}
To enable an advanced feature that is currently disabled, contact your sales representative.
{% endhint %}

### Release Stage Badges (Beta / Alpha) <a href="#release-stage-badges" id="release-stage-badges"></a>

The left sidebar menu and the tab at the top of each page display a stage badge next to features that have not yet reached general availability, so you can quickly identify features that are still being refined:

| Badge                                  | Meaning                                                                     | Where It Appears                                                                               |
| -------------------------------------- | --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| <mark style="color:blue;">Beta</mark>  | Available for use but still being refined; screens and workflows may change | Left sidebar menu, page tabs, and the Advanced Features section above                          |
| <mark style="color:blue;">Alpha</mark> | Available only to selected organizations and still in testing               | Left sidebar menu and page tabs only; the Advanced Features section does not show Alpha badges |

Features without a badge are generally available. Badges are informational and do not affect access: whether a feature appears in the menu still depends on whether it is enabled for your organization and on your role permissions. Current Beta features include <mark style="color:blue;">Voice Agent</mark> (shown as AI Voice Assistant in Organization Overview), <mark style="color:blue;">Teams</mark>, and <mark style="color:blue;">AI Gateway</mark>. The badge disappears automatically when a feature reaches general availability.

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-17f64705126923774fb386c68ff4f5c7250007a5%2Frelease-stage-badge-sidebar.png?alt=media" alt="Beta labels next to Voice Agent and Teams under AI Features in the left sidebar menu"><figcaption><p>Beta badges in the left sidebar menu</p></figcaption></figure>

**Use case**: An organization administrator in a customer service department plans to include telephone voice support in next quarter's roadmap and wants to check how mature the capability is. She opens <mark style="color:blue;">Organization Settings</mark> → <mark style="color:blue;">Organization Overview</mark> and sees that AI Voice Assistant is enabled with a Beta badge under Advanced Features. She then opens <mark style="color:blue;">AI Features</mark> → <mark style="color:blue;">Voice Agent</mark> from the left sidebar menu, where both the menu and page tab also show Beta. She therefore allows time for testing and adjustments in her plan and checks the general availability timeline with her sales representative.

### Credits <a href="#credits" id="credits"></a>

The Credits card on the right shows the current <mark style="color:blue;">billing mode</mark> (credits mode or character count mode) and provides a <mark style="color:blue;">Go to Credits Wallet</mark> button. Click it to view your credit balance and usage details. For more information, see [Credits Billing](https://docs.maiagent.ai/maiagent-user-guide/en/others/credits.md).

***

## Management Actions <a href="#management-actions" id="management-actions"></a>

Management Actions provides shortcuts to common organization settings. Click a shortcut to open the corresponding page:

| Shortcut                   | Destination Page                                                                                                                                                                          |
| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Edit Members               | [Member Management](https://docs.maiagent.ai/maiagent-user-guide/en/org/overview/member.md)                                                                                               |
| Edit Role Permissions      | [Role Permission Management](https://docs.maiagent.ai/maiagent-user-guide/en/org/roles/role-permission.md)                                                                                |
| Third-Party Login Settings | [Third-Party Login (SSO)](https://docs.maiagent.ai/maiagent-user-guide/en/org/sso.md) (shown only for Enterprise organizations)                                                           |
| Identity Synchronization   | [Identity Synchronization (LDAP / SCIM)](https://docs.maiagent.ai/maiagent-user-guide/en/org/identity-sync.md) (shown only for Enterprise organizations)                                  |
| Announcement Management    | [Announcement Management](https://docs.maiagent.ai/maiagent-user-guide/en/org/overview/announcements.md): publish announcements for the entire organization or specific roles and members |
| OAuth Applications         | [OAuth Applications](https://docs.maiagent.ai/maiagent-user-guide/en/org/developer/oauth-applications.md): allow external systems to call APIs as organization members                    |

None of these six pages has an entry in the left sidebar menu; access them from here. After you open one, the left sidebar menu continues to show Organization Overview as the current location.

***

## Delete Organization <a href="#delete-organization" id="delete-organization"></a>

The Delete Organization section is at the bottom of the page. Only the organization owner can perform this action, and they must enter the organization name to confirm.

{% hint style="danger" %}
Deleting an organization permanently removes all Agents, knowledge bases, and member data. This action cannot be undone. Confirm carefully before proceeding. For the detailed procedure, see [Delete Organization](https://docs.maiagent.ai/maiagent-user-guide/en/org/overview/organization-management.md).
{% endhint %}


---

# 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.maiagent.ai/maiagent-user-guide/en/org/overview/organization-overview.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.
