tencent cloud

User Group Overview

Download
Focus Mode
Font Size
Last updated: 2026-11-17 14:27:53
AI-Translated & Reviewed
User groups are used to manage CMR access keys (API Keys) in groups. You can create user groups by team, business line, project, or environment, and centrally configure the models, intent routing rules, and resource limits that API Keys within a group can access.

Feature Overview

Group management: Centrally manage API keys by organizational or business boundaries.
Access control: Limit the models and intent routing rules that API keys within a group can access.
Resource control: Control the overall resource consumption of user groups through credit budgets and rate limits.
Flexible configuration: Supports classifying user groups by tags to meet management requirements in different business scenarios.

Core Features

1. API Key Group Management

A CMR instance can create multiple user groups, and a user group can be associated with multiple API keys. You can assign an API Key to the corresponding user group based on its team, business line, project, application, or environment.
Each API Key can belong to only one user group. After an API Key is assigned to another user group, it is removed from the original user group and added to the new one.
Newly created or imported API keys are assigned to the system-built-in "Ungrouped API Keys" user group by default. You can later assign them to custom user groups based on business needs.

2. Model Access Control

You can specify the models or intent routing rules that a user group is allowed to access. API Keys within the group can only use the models and intent routing rules that the user group is allowed to access.
If no models or intent routing rules are specified when a user group is created, API Keys within the group can use all models and intent routing rules under the current CMR instance by default.
You can configure model access scopes through user groups to provide different model capabilities for different teams or business lines. For example, you can provide low-cost models for development and testing teams, and designated high-availability models or intent routing rules for production business.

3. User Group Limits

A user group can be associated with a credit budget to limit the overall credit consumption and call rate of API keys within the group.
A credit budget can include the following limits:
Maximum credit quota.
Credit reset cycle.
TPM (Tokens per minute) limit.
RPM (Requests per minute) limit.
A CMR instance, user group, and API Key can each be configured with a credit budget and rate limits. When an API Key initiates a call, it must simultaneously satisfy the limit conditions at all three tiers: the instance, the user group it belongs to, and the API Key itself. Once any tier reaches its credit quota or rate limit, all related calls are restricted.

4. Tag Management

You can configure tags for user groups to classify them by dimensions such as department, project, environment, or cost center, making it easier to search for and manage related resources.

Typical Scenarios

Create separate user groups for different teams or business lines, assign the corresponding API Keys to the respective user groups, and configure the accessible models and credit budgets separately to achieve resource isolation between different teams.
Create user groups based on business environments, and configure independent model access scopes, credit budgets, and rate limits for each environment to prevent development and testing traffic from affecting production business.
Authorize high-cost models or specific intent routing rules only to designated user groups, while other user groups use general-purpose or more cost-effective models to achieve on-demand access to model capabilities.
Control overall resource consumption at the instance tier, control resource consumption of teams or business lines at the user group tier, and control the call behavior of specific applications, employees, or scripts at the API Key tier to achieve tiered resource governance.

FAQs

1. Which User Group Does a New API Key Belong To?

When you create or import an API key without specifying a user group, the API key is assigned to the system-built-in "Ungrouped API Keys" user group by default. If you create or import the API key under a target user group, it is directly assigned to that user group. After creation, you can also adjust its user group based on business needs.

2. Can an API Key Belong to Multiple User Groups at the Same Time?

No. Each API Key can belong to only one user group. After an API Key is assigned to a new user group, it is removed from the original user group.

3. Which Models Can API Keys Access When No Model or Intent Routing Rules Are Specified for the User Group?

If no models or intent routing rules are specified for a user group, API Keys within the group can use all models and intent routing rules under the current CMR instance by default.

4. What Happens When a User Group's Credit Budget Is Exhausted?

When the credit budget associated with a user group is exhausted, API Keys within the group cannot continue to call models until the budget quota is reset or adjusted.

References



Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback