> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aihubmix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Management keys

> Use management keys with the CLI and management APIs. Learn how they differ from model API keys and how to create, store, expire, and revoke them.

Management keys authenticate CLI and management API operations, such as reading account information and managing API keys. Use an [API key](/en/console/api-keys) for model requests.

<h2 id="create-and-use">
  Create and use a key
</h2>

1. Switch to the account you want to manage and open **Management keys**.
2. Create a credential with a descriptive name and expiration.
3. Store the full key immediately after creation. The list shows only a masked value afterward.
4. Follow the [AIHubMix CLI guide](/en/api/aihubmix-cli) to sign in or configure a management tool.

Some existing tools call this credential an **Access Key** or **Manage Key**. Check which credential a tool expects before configuring it.

<h2 id="permissions">
  Who can manage keys
</h2>

Personal account owners and organization administrators can manage keys for their respective accounts. Regular organization members do not have this entry. Credentials follow current account and role permissions and cannot bypass workspace or member restrictions.

Name credentials separately for each management tool so you can revoke one when it is no longer needed.

<h2 id="revoke-and-replace">
  Expire, revoke, and replace
</h2>

Management requests using an expired or deleted credential are rejected. To replace one, create a new credential, update and verify the tool, then delete the old credential.

If a credential is exposed, revoke it promptly and review related administrative activity. Keep management keys out of public repositories, frontend code, and logs.

Related: [API key management](/en/console/api-keys) · [Members and permissions](/en/enterprise/members) · [Audit logs](/en/enterprise/audit)

Last updated: 2026-10-13


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.