Model Access and Group Authorization

Applicable role: Admin user Last updated: 2026-08-06

Which models you can see in the console depends on the organization's groups, member permissions, and API Key bindings. These three layers have different scopes, and the most common issue is that the admin user can see a model but a member or a specific Key cannot reach it.

How Available Scope Is Determined

For a request to be routed successfully, all of the following must be true:

1. The model has been added to a group available to the organization.
2. The current user has permission to use that group.
3. The API Key is bound to that group, or a viable candidate exists in the default route.
4. The group and the corresponding account are in an available state.

Control	Managed by	Scope of Impact
Organization groups	Platform	Determines which groups the entire organization can see
Member groups	Admin user	Determines which organization groups a specific member can use
Key bound group	Key owner	Determines which group plain model names are prioritized to
Default model config	Admin user or member	Provides fallback routing when the bound group does not have the target model
Account status	Platform	Accounts under maintenance, disabled, or in an abnormal state do not participate in routing

The model plaza displays publicly available models on the platform; the call guide is closer to the actual available scope for the current account. When troubleshooting, prioritize checking the call guide and API Key page.

Viewing Models Available to Your Organization

Admin users can confirm scope from three entry points:

• Model Plaza: View public models and pricing across different groups. This entry is not in the left menu but in the top navigation bar, controlled by a platform toggle, and may be hidden on small screens.
• Call Guide: View the model call names available to copy for the current account.
• Account Status: Confirm whether groups are currently healthy.

deepseek-v4-flash and kimi-k3 may have different available groups in different organizations. When a model does not appear on the page, check the group scope first. Do not manually construct call names based on model names.

Assigning Groups to Members

After the organization obtains a group, it is already granted to members by default, and usually no extra action is needed. Only when the organization has switched "Default Group Assignment for Members" to "Manual Assignment" do exclusive groups need to be authorized individually. Public groups are always available and are not affected by this setting.

When individual authorization or revocation is needed:

1. Open "Member Management".
2. Find the target member and open "Available Groups".
3. Check the groups to enable, or uncheck the groups to disable.
4. After saving, ask the member to refresh the page or re-enter the call guide.
5. The member should use their own Key to send a short test request for verification.

Assigning groups does not change the organization balance or modify historical usage records. It only affects new requests after saving.

Requesting New Models or Groups

When you need to expand the organization's scope, submit a model or group request to the platform. To minimize back-and-forth, include the following:

• Desired models;
• Business use case and primary calling methods;
• Number of users or applications;
• Estimated call volume, concurrency, and stability requirements;
• Whether image input, tool calling, long context, or other capabilities are needed.

After the request is completed, new groups are granted to members by default. If the organization has switched to manual assignment, you still need to authorize per actual usage scope and select the correct group for relevant Keys.

Model Not Visible or Call Fails

Check in this order:

1. Search for the model name in the call guide.
2. Confirm the organization has the corresponding group.
3. Confirm the current member has been assigned that group.
4. Open the API Key page and check Key status and bound group.
5. Check whether the account status is normal.
6. Re-copy the model call name from the call guide and try again.

Symptom	Common Cause	Resolution
Model not in the list	Organization has not enabled it, or member has not been assigned	Contact admin user or platform to confirm group scope
Returns 403	Key, user, or organization does not have permission for the target group	Check Key status, member assignment, and organization groups
Returns 404 / Model Not Found	Model call name is wrong, or the group does not have that model	Re-copy the call name from the call guide
Returns group unreachable	Account maintenance, anomaly, or currently unavailable	Select another available group, or retry later
Request succeeds but routing does not match expectations	Key binding and default model config are inconsistent	Check bound group and default candidate order

For a more complete list of response codes, see Error Codes and Troubleshooting.

Group Management Recommendations

With a larger team, splitting Keys and groups by purpose makes management easier. Use separate Keys for development, testing, and production environments. Applications handling important business data can be further secured with source restrictions, quota limits, and rate limits. This way, when abnormal calls occur, you can quickly trace them to a specific person or application through usage records.

FAQ

Why can the admin user see deepseek-v4-flash but a member cannot? Organization groups are granted to members by default. If the organization has switched "Default Group Assignment for Members" to manual assignment, the admin user needs to enable the corresponding exclusive group in the member's "Available Groups". Also check whether that group was individually disabled.

Can I put kimi-k3 directly into the client? Yes, provided the current Key can reach a group containing that model. The call name should match the value shown in the console's "Call Guide".

Does modifying groups affect the balance? No. Groups determine routing scope; balance and historical records remain unchanged.

Why is it still not visible right after assignment? Refresh the page or log in again first. If it still does not appear, check the group status and confirm the save operation was successful.