What this category of data looks like
This category of data is generated around the publication approval process for a single game. Core documents include declaration request files, game application forms, copyright certificates, and review reports. Data sources include the National Press and Publication Administration's official service platform, copyright registration archives, game package files, and qualification materials submitted by cooperative operating institutions. The data update rhythm is adjusted irregularly according to the declaration progress of a single game. Each piece of data includes exclusive fields such as declaration number, game name, copyright registration number, and provincial preliminary review opinions. There is no universal cross-category unified format.
What constraints do these characteristics impose on the permission and data isolation link
The data characteristics of this category impose multiple constraints on permission and data isolation. Qualification materials from official sources and operating materials submitted by cooperative institutions contain sensitive compliance information. It is necessary to strictly isolate materials from different declaration projects to prevent cross-project data leaks. Single-game declaration data includes exclusive fields, so permissions must be divided according to declaration subject and project leader dimensions to avoid unauthorized personnel accessing uncompleted approval materials. The data update rhythm is adjusted irregularly according to the declaration progress, so permission configuration must support temporary authorization and regular recovery to adapt to process changes. At the same time, document export and copy operations must be restricted to prevent sensitive materials from being leaked externally.
How to configure settings
This configuration is compatible with FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
teamId | Assign a unique teamId for each game declaration project | Data in this category is divided by single-game declaration projects. Binding teamId enables precise isolation of materials and conversations across different projects |
tmbId | Only allow teams corresponding to the declaration project to use tmbId to access data | Data in this category involves sensitive approval qualifications, so the scope of access subjects for tmbId must be strictly restricted |
| Session data retention period | 30 days | Chat records during game declaration are only used for internal project communication and do not need long-term storage |
| Single-session context limit | 8000 token | Adapts to the document length of declaration materials to avoid loss of key information due to exceeded context |
| Project document storage limit | 1000 MB | Matches the conventional storage scale of single-game declaration materials to prevent resource overflow |
| Sensitive material export restriction | Disable document export functions for unauthorized roles | Declaration materials include sensitive information such as copyright certificates, so unauthorized external circulation must be prevented |
Three common mistakes
- Issue: After generating a publicly accessible link, unauthorized external personnel can view chat records and materials related to game declarations. Cause: An independent
teamIdis not assigned to each declaration project, so sessions and data from different projects are not isolated, and the public link shares full project data by default. - Issue: An error prompting "no permission to access resources" appears when testing access after configuring permissions. The content can be run after forcibly ignoring the prompt. Cause:
tmbIdis not correctly bound to the team of the declaration project, so the permission verification logic does not match the correct access scope. - Issue: Unable to invite team members to configure permissions after local deployment. Cause: The local deployment switch for the team permission module is not enabled, so the permission isolation function does not take effect.
How to confirm the configuration is complete
- Attempt to access documents and sessions under the corresponding
teamIdusing an account that is not a project member, and confirm that no declaration-related materials or chat records can be viewed. - Generate a project-specific access link, and verify that only the
teamIdof the current declaration project is bound, and data from other projects is not included. - Check the export permissions of sensitive documents, and confirm that unauthorized roles cannot perform export operations.
- View the session data retention period, and confirm that it matches the communication cycle of the current declaration project.
The values provided here are common starting points and should be evaluated 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.