What data for this category looks like
Data for this category primarily originates from game text, art assets, plot scripts, and publicly available regulatory requirements. The update cycle follows each version or event cycle. Daily maintained documents include content self-check lists, sensitive content modification records, user agreements, and compliance review minutes. Each document contains fields such as content classification tags, modification time, reviewer identifiers, and associated version numbers. Art asset data also includes resolution, file format, and associated plot node information.
What constraints do these characteristics impose on permission and data isolation
Because data is updated by version and event cycle and linked to specific business entities, compliance self-check data from different project teams must be strictly isolated to prevent information leaks across versions or projects. Documents contain sensitive fields such as reviewers and associated versions, so access must be limited to only operations and review personnel from the corresponding project. Art asset data varies widely in size, so different storage permission quotas must be matched. Additionally, due to the high update frequency, associated rules for permission configurations must be updated synchronously to prevent permission loopholes left by old version data.
How to configure the settings
This configuration is based on FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
teamId | Unique identifier bound to the project version | Matches the data isolation requirement of this category updated by version or event cycle, ensuring that self-check data for different projects is only visible to authorized members |
tmbId | Permission group divided by compliance review role | Documents in this category contain sensitive content such as reviewers and review minutes, so access scope must be restricted by role |
| Data storage quota | 1000 MB, calibrated based on actual measurements | Art asset data varies widely in size, so sufficient space must be reserved while avoiding resource waste |
| Invitation notification trigger rule | In-site push bound to teamId | Ensures invited members can receive notifications under the corresponding team, resolving the issue of no notifications after invitation |
| Account isolation configuration | Divided by server deployment node | Meets account isolation requirements for local deployment scenarios, preventing data leaks across servers |
| Notification delay threshold | 60 seconds | Ensures invited members receive permission notifications in a timely manner, avoiding delays that impact work processes |
Three common configuration errors
- Issue: After invited members access the FastGPT platform, no team invitation messages appear in the notification center, and access to the corresponding compliance self-check project is unavailable. Cause: The invitation notification trigger scope is not bound to the
teamIdconfiguration, causing notifications to only be sent under the default team. - Issue: When attempting to add a second compliance self-check team, the system prompts a configuration conflict and creation fails. Cause: Each team is not assigned an independent
tmbId, causing the system to fail to identify permission boundaries for different teams. - Issue: After FastGPT is deployed locally, cross-account access to content self-check lists or art asset data from other projects is possible. Cause: Account isolation rules are not configured by server deployment node, causing default permissions to override cross-node access scope.
How to confirm the configuration is properly set up
A designated test member is invited to join the target compliance self-check team, and the FastGPT notification center is checked for the corresponding invitation message to confirm the invitation configuration is effective. Test accounts with different roles are logged into, and it is verified that only corresponding roles can access documents such as content self-check lists and compliance review minutes. Art asset files are uploaded, and verification is completed that the storage quota takes effect as configured, with no over-limit error prompts displayed. Different accounts for local deployment are switched between, and verification is completed that version self-check data from other accounts cannot be accessed.
The values provided 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.