What Data for This Category Looks Like
This category of data is created and maintained by customer success managers, training instructors, and product operations teams. It includes four core document types: training courseware, user manuals, training attendance sheets, and problem resolution Q&A lists. Data sources include official content from the product help center, customer organization structure information, training recording files, and historical records from internal ticket systems. Data updates are triggered by customer tickets or product version iterations. Each update covers manual content for the corresponding version or attendance data for a single training batch. Core fields include the customer ID the document belongs to, training batch number, permission role identifier, and ticket association number. Basic units of measurement are characters, items, and hours.
Constraints Imposed on Permission and Data Isolation
Data sources for this category include multiple types of customer-exclusive content and organization structure information. Data must be isolated by customer team to prevent cross-customer leakage of training content and tickets. Document types include sensitive training recordings and customer-exclusive manuals. Access permissions must be assigned based on job roles, allowing only personnel in corresponding roles to view matching content. Data updates are triggered by tickets and product versions, so real-time permission verification must be supported. This ensures updated content is only visible to authorized roles. Global variables related to training parameters and ticket statistics must have their scope isolated by user ID to avoid parameter confusion across different training batches. Internal ticket and training Q&A data must be bound to customer teams. This ensures only duty personnel from the same team can process corresponding tickets.
How to Configure Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
teamId | Bound to the team ID of the customer’s organization structure | Used to isolate training manuals and ticket data by customer team, ensuring cross-customer data is inaccessible |
tmbId | Bound to the role ID of training instructors and duty personnel | Used to limit the document access scope of specific job roles, allowing only authorized roles to view corresponding training content |
| Role Permission Groups | Divided into 3 categories: training instructor, customer success manager, operations duty staff | Matches the typical job roles for this category, ensuring each role can only access documents with matching permissions |
| Global Variable Scope | Bound to teamId and user ID | Ensures identical-named training parameters and ticket statistics variables from different users are isolated from each other |
| Single Query Data Limit | Top 20 items | Calibrated based on actual testing, prevents returning excessive redundant data in a single query |
| Training Courseware Upload Limit | 50 MB per file | Matches the common storage size of documents in this category, avoids excessive resource usage |
| SSO Integration Configuration | Enabled for enterprise edition authorization | Supports unified identity authentication for enterprise customers, aligns with permission management requirements for internal operations duty |
Three Common Misconfiguration Issues
- Issue: Training recording access permissions are mixed across different instructors. Some instructors can view recording files not assigned to their batch. Cause:
tmbIdis not bound to the instructor’s role permission group, leading to ineffective permission configuration. - Issue: An error prompt reading "SSO is only supported in commercial edition" appears when attempting to configure SSO. Cause: The permission configuration scope of the basic edition and commercial edition is confused, and the current FastGPT edition with commercial authorization is not confirmed.
- Issue: Global variables return identical ticket statistics values when called by different operations duty personnel. Cause:
teamIdis not used as a scope binding parameter for global variables, resulting in variables not being isolated by customer team.
How to Verify Successful Configuration
- Log into test accounts with different roles, verify that only training courseware, user manuals, and internal tickets matching the corresponding job role permissions are accessible.
- Navigate to the permission configuration interface of FastGPT v4.17.0, confirm that
teamIdandtmbIdare bound to the corresponding role groups. - Initiate a document query across customer teams, verify that only training data and ticket content belonging to the current team can be viewed.
- Call identical-named global variables, initiate requests using different user IDs, confirm that returned parameter values are independent of each other.
The values listed above are common starting points, and should be validated against the samples of the respective use case.
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.