What this category of data looks like
Data for this category mainly comes from CRM systems, contract order databases, identity management systems, and product backends. Daily associated documents include onboarding application forms, tenant configuration sheets, administrator account lists, and delivery confirmation slips. Common data fields include tenant identifiers, customer entity information, initialization permission configuration items, administrator account lists, onboarding status, and delivery milestones. Data updates occur per order or daily, synced with customer onboarding process progress or daily permission verification.
What constraints do these characteristics impose on permission and data isolation
Data sources for this category are scattered and linked to multiple business systems. Permission isolation must cover cross-system data flow links to prevent cross-leakage of tenant configurations and account information across different customers. Data updates are triggered per order or daily, so permission configurations must support dynamic synchronous updates to ensure new permission rules take effect in a timely manner. Daily documents contain multiple types of sensitive business information. Different on-call operations and maintenance personnel must isolate data access permissions based on their assigned customer scope to prevent unauthorized viewing of other customers’ onboarding applications and delivery confirmation slips. Tenant identifiers and administrator account lists are core sensitive fields, which must be strictly bound to the permission scope of the operating subject to avoid unauthorized modification of initialization configurations.
How to set the configurations
These configurations apply to FastGPT v4.17.0 and above.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
teamId | Bound to the exclusive identifier generated during tenant initialization | Used to accurately distinguish tenant resources of different customers and avoid cross-tenant data confusion |
tmbId | Bound to the team permission identifier of operations and maintenance personnel | Restricts operations and maintenance personnel to only access tenant configuration data for their assigned teams |
| Tenant permission isolation scope | Defined based on assigned customer scope | Aligns with the customer division of labor in daily on-call operations, ensuring permissions match business responsibilities |
| Sensitive field access logs | Enable full recording | Facilitates backtracking of permission operations and troubleshooting of unauthorized access issues |
| Permission verification frequency | Once every 300 seconds | Balances real-time performance and system load, matching the daily permission verification update rhythm |
Three common mistakes
- Phenomenon: Different operations and maintenance personnel can view all customers’ tenant configuration data after logging in. Cause:
teamIdis not bound to the operations and maintenance personnel’s assigned scope, and the permission isolation scope is not defined based on customer division of labor. - Phenomenon: Global variables in workflows are accessed by operations and maintenance personnel from other tenants. Cause: No tenant isolation rule is bound to global variables via
teamId, and the variable scope is not restricted to a specified tenant. - Phenomenon: Customers cannot log in to the system after tenant initialization. Cause: The permission configuration of the administrator account list is not bound to
teamId, resulting in failed permission verification.
How to confirm the configuration is correct
- Log in to accounts with different permission levels, verify that only onboarding application forms and tenant configuration data for their assigned customers are visible.
- Trigger a customer onboarding process, check whether the permission verification logs correctly record the operating subject and tenant identifier.
- Modify the configuration items of a specified tenant, verify that only the assigned operations and maintenance personnel can perform this operation.
- Call tenant-related APIs, check that the returned data only contains tenant information within the current permission scope.
The values given are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.