Tenant Settings
Feature Overview
| Item | Content |
|---|---|
| Applicable Role | Model Consumer |
| Navigation path | Settings > Tenants & Settings > Tenant Settings |
| Page route | /user/user-space/settings |
| Managed objects | Credit-balance alerts, project defaults, member quota policy, and tenant-level defaults |
Beginner Explanation
Tenant Settings is the tenant default-rule panel. It defines the initial policy for new projects, new members, and quota requests. A change usually affects objects created later; verify existing objects on their own pages.
Terms Quick Reference
| Term | Description |
|---|---|
| Tenant Settings | The entry for tenant-level default configuration.; Confirm the applicable scope before changing it. |
| Default rule | A rule inherited when a new object is created.; It does not necessarily update existing objects. |
| Tenant context | The tenant that owns the current settings.; Confirm it before switching tenant scope. |
| Member default policy | The initial rule applied when a new member joins.; Verify it with a new member after a change. |
Prerequisites
- The current account can view and maintain Tenant Settings.
- Before saving, you have confirmed the impact on projects, member quotas, and the quota-request flow.
- Before resetting defaults, you have confirmed that the current configuration can be overwritten.
Page Description
| Tab | Description |
|---|---|
| Credit Balance Alert | Configures an alert when tenant balance falls below a threshold. |
| Project Defaults | Configures the reset cycle, alert threshold, and limit policy for new projects. |
| Member Quota Defaults | Configures initial quota, reset cycle, and limit policy for new members. |
| Quota Request Settings | Configures automatic expiration and request rules for pending requests. |
| Bottom actions | Reset to Defaults and Save Settings |
Main Operations
View Tenant Settings
- Go to
Settings > Tenants and Settings > Tenant Settings. - Review organization information, quota-request settings, project defaults, and member-quota defaults.
- Record the current state and confirm that each setting applies to the current tenant.
- If information is missing, refresh and check administrative permission. Hide organization identifiers and quota before screenshots or sharing.
Edit Tenant Settings
- Go to
Tenants & Settings > Tenant Settings. - On
Credit Balance Alert, configure the alert threshold.
The following screenshot shows the balance-alert tab.

- Open
Project Defaultsand configure the reset cycle, alert threshold, and limit policy for new projects.
The following screenshot shows Project Defaults.

- Open
Member Quota Defaultsand configure initial quota, reset cycle, and limit policy for new members.
The following screenshot shows Member Quota Defaults.

- Open
Quota Request Settingsand configure automatic expiration for pending requests.
The following screenshot shows Quota Request Settings.

- After reviewing all tabs, select
Save Settings.
Verify Tenant Settings
- After an approved change, reopen Tenant Settings.
- Compare switches, defaults, and update time with the change record.
- Before creating a project or member, confirm that the new defaults take effect as expected.
- If not applied, check the save message, permission, and cache. Do not submit repeatedly.
Parameter Quick Reference
| Field Name | Required | Field Type | Example | Description |
|---|---|---|---|---|
| Tenant name | System-generated | Text | Example Tenant A | Identifies the tenant to which the settings apply. |
| Default project rule | No | Configuration | Enabled | Applies to projects created after the rule takes effect. |
| Default member policy | No | Configuration | Standard member | Applies to members added after the policy takes effect. |
| Quota rule | No | Configuration | Default quota | Controls quota allocation or request behavior. |
| Save | No | Button | Save | Submits changes made to tenant settings. |
Pitfalls
- Do not change roles, members, login policies, Keys, or API rate-control rules without confirming the affected users and systems.
- UI entries can differ by role and tenant scope; verify the current account context before troubleshooting.
- Never copy complete Keys, AK/SK, tokens, or secrets into documentation, tickets, or screenshots.
Result Validation
| Check Item | Success Signal | If Abnormal |
|---|---|---|
| Saved | The new values remain after saving and reopening the page. | Check whether the page reports a save failure. |
| Defaults effective | A new project or member inherits the tenant defaults. | Check the tenant scope and defaults selected during creation. |
| Request flow | Quota requests follow the configured expiration time. | Check request status and time on Quota Requests. |
FAQ
Existing projects do not change after settings are saved
Symptom:
Existing projects or members still show the old configuration.
Possible cause:
- Tenant Settings provides defaults mainly for objects created later.
- Existing projects or members have independent configuration on their detail pages.
Resolution:
- Change the existing object on Project Details or Member Quotas.
- When creating a new object, confirm that it inherits the latest defaults.
Why is no configuration loaded?
Symptom:
Default quota, request expiration, or project defaults are absent.
Possible cause:
The current account lacks Tenant Settings permission, defaults are not initialized, or the page still shows another tenant's data.
Resolution:
Confirm the current tenant and Tenant Settings permission. If the configuration is empty, ask the tenant owner to complete and save the defaults.
Why is Save Settings unavailable?
Symptom:
Settings are visible, but Save, Reset, or a default-rule field cannot be selected.
Possible cause:
The current account lacks Tenant Settings permission, an upstream platform manages the policy, or the configuration is in approval.
Resolution:
Verify Tenant Settings permission and configuration source. Ask the platform operator to change managed configuration, or wait until approval finishes.
How should the Tenant Settings page be exported or captured safely?
Symptom:
Page information is needed for troubleshooting, audit, or delivery.
Possible causes:
The page may contain accounts, email addresses, IP addresses, internal paths, tenant identifiers, Keys, or amounts.
Resolution:
Keep only the necessary fields and action context. Use opaque light-gray pixel mosaics for sensitive text and never share complete credentials or internal addresses.
What should I do when the Tenant Settings page shows unexpected data?
Symptom:
A field, status, metric, or related object differs from the expectation.
Possible causes:
The page scope, time condition, role permission, or upstream setting does not match.
Resolution:
Record the redacted object, time, and result. Verify the entry and filters first, then check related pages and Operation Logs.
Notes
- Saving settings affects later tenant-management flows. Confirm each value first.
Reset to Defaultsoverwrites the current page values. Confirm whether they must be retained before resetting.
Next Steps
- Create a new project to verify Project Defaults.
- Add a new member to verify Member Quota Defaults.
- Review Quota Requests to verify request rules.