What this category of data looks like
This category of data is generated around the full process of a single game’s publication declaration, and includes four core document types: declaration request files, game application forms, copyright certificates, and review reports. Data sources include official government service interfaces for publication declaration, copyright registration systems, game package verification tools, and materials from cooperating operation institutions. Data updates are triggered irregularly along with the progress of a single game’s declaration, with no fixed cycle. Each document contains fields such as declaration subject information, game category, license application status, and material verification mark. Each piece of data is bound to the corresponding teamId project ID, with no universal fields shared across projects.
What constraints do these characteristics impose on the permission and data isolation link
The non-public nature of a single game’s declaration data requires strict restrictions to allow only project team members to access the corresponding documents. The irregular nature of data updates requires permission configurations to be dynamically adjusted along with the declaration progress, to prevent unauthorized personnel from accessing sensitive materials during the approval stage. Permission differences for different declaration subjects (such as publishing legal teams, project leads) must be divided based on job responsibilities to restrict field access. For example, only publishing units can modify declaration subject information. Cross-project data isolation requirements prevent confusion of declaration materials from different games, to avoid approval failures caused by material mismatches. At the same time, access permissions for individual documents must be precisely controlled via tmbId.
How to configure the settings
This configuration is implemented based on the permission management module of FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
teamId | Bind to the exclusive team ID of a single game declaration project, use an exclusive project identification string | Ensure only members added to the corresponding teamId can access the declaration data of that project, enabling cross-project isolation |
tmbId | Assign a unique tmbId to each declaration document, use integers in the range 1-1000, calibrated based on actual testing | Precisely control access permissions for individual materials, preventing unauthorized access across documents |
| Login-free link configuration | Set the link validity period to 72 hours, only allow access from specified enterprise internal IP ranges | Meet temporary external collaboration needs while restricting unauthorized access |
| Team member size limit | Configure based on the actual number of collaborators for the declaration project, use values in the range 3-15 | Match the conventional team size for game license number declarations, avoiding excessive permission spread |
| Conversation content export permission | Only project lead roles can trigger export operations | Prevent sensitive declaration materials from being exported and leaked by unauthorized personnel |
| Ticket permission filtering | Filter internal tickets by declaration project tags, only display tickets from the corresponding team | Ensure operations on duty personnel only process tickets related to the current project |
Three Common Misconfigurations
- Symptom: Internal tickets only display declaration content for some projects, and tickets from remaining projects cannot be viewed. Cause: No exclusive
teamIdis configured for the corresponding project, causing tickets from different projects to be grouped under the default team, resulting in failed permission filtering. - Symptom: After a login-free link is generated, unauthorized users can access it indefinitely for more than 7 days. Cause: No link validity period is set, or the validity period is configured to exceed 72 hours, exceeding the security boundary for temporary collaboration.
- Symptom: Team members can export declaration documents from all projects. Cause: Export permissions are not restricted exclusively to project lead roles, causing ordinary members to also have export permissions, violating data isolation requirements.
How to Confirm the Configuration Is Complete
- Access the FastGPT backend via login, enter the permission management page of the corresponding project, and verify that only the authorized member list is visible.
- Generate a login-free link, access the link using an unauthorized browser account, and confirm that the corresponding declaration document cannot be viewed.
- Switch to an ordinary member role, attempt to trigger a conversation content export operation, and confirm that no export permission is available.
- View the internal ticket list, and confirm that only declaration tickets related to the currently configured team are displayed.
The values provided here 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.