What this category of data looks like
Data for this category primarily comes from level editors, art resource libraries, player test data, and defect systems. Daily produced documents include level design drafts, resource requirement sheets, test feedback forms, and version submission records. Data updates are synchronized once per week or per version iteration cycle. Level design drafts contain level ID, resource reference path, and test node ID. Version submission records contain submitter ID, submission time, and the associated tmbId field. The defect system records associated level batch numbers and problem severity levels.
Constraints on permission and data isolation
Data for this category is bound to unique identifiers via level batches and version submission records. There are strict business boundaries between level resources and test data of different projects. Data updates rely on version submission processes. If permissions are not divided by project, cross-project accidental resource access will occur. Some historical version data lacks the tmbId field. If compatible isolation rules are not configured, old version data cannot be correctly attributed to the corresponding team. For internal deployment scenarios, internal authentication systems must be connected to implement unified permission verification, preventing unauthorized external access to internal level creation data.
How to configure settings
This page’s configuration is based on FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
teamId | Assign a unique 6-12 character string identifier per level project | Matches the project grouping logic of level creation, enabling cross-project data isolation |
tmbId completion rule | Automatically fill the associated project's tmbId for old documents in the MongoAppVersion table that lack the tmbId field | Resolves the issue of missing fields in historical version data, enabling correct data attribution |
| Team role permissions | Divide access scope for corresponding teamId based on planner, scene editor, and operations on-call roles | Matches the operational permissions of different positions, restricting access to sensitive data |
| SSO authentication configuration | Configure the authentication endpoint for the internal network environment, enable unified identity verification | Adapts to internal deployment scenarios, implementing permission verification without additional accounts |
| Data access time limit | Only grant access to version submission records from the last 30 days to on-call operations staff | Restricts access to sensitive historical data, reducing exposure risks |
Three common configuration mistakes
- Phenomenon: When adding team members on the online version, entering an account displays the username as invalid. Cause: The binding relationship between the corresponding
teamIdand member account is not configured, resulting in permission verification failure. - Phenomenon: After internal deployment, calling the authentication interface returns an error, and the log shows MySQL connection refused. Cause: The MySQL connection configuration of the authentication service is not aligned with FastGPT’s database configuration, interrupting the permission verification chain.
- Phenomenon: Historical version level data cannot be correctly attributed to the corresponding project. Cause: The completion operation is not performed for old documents in the MongoAppVersion table that lack the
tmbIdfield, causing the data isolation rule to fail.
How to confirm the configuration is correct
- Log in to test accounts corresponding to different
teamIdvalues, verify that only level design documents and version submission records for the current project can be accessed. - Manually query old documents in the MongoAppVersion table that lack the
tmbIdfield, confirm that the system has automatically filled in the associated project'stmbIdfield. - Log in via the internal network SSO endpoint in the local deployment environment, verify that permission verification can be completed without additional accounts.
- Attempt to add a team member from a different project, confirm that the system prompts insufficient permissions or fails to add.
The values provided here are common starting points and should be evaluated against the samples of the respective deployment environments.
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.