What data for this category looks like
Data for this category mainly comes from art asset libraries, project management systems, engine resource packages, and outsourced delivery packages. Daily output documents include art requirement sheets, asset specification sheets, outsourced feedback sheets, and acceptance records. Fields cover asset unique identifiers, version numbers, outsourcer permission identifiers, acceptance status, polygon count, texture resolution, and more. Data update frequency is mostly daily or weekly. Some urgent outsourced delivery packages are updated per single task.
What constraints do these characteristics impose on the permission and data isolation link
Art asset production management involves core visual project resources, and includes scenarios for internal team and outsourced collaboration. The resource access scope of different roles (art PM, concept artist, 3D artist, outsourced project manager) must be strictly differentiated. Documents such as asset specifications and acceptance records contain sensitive project parameters, so access must be restricted for unauthorized roles. If batch asset data updated daily or weekly is not permission-isolated, cross-project resource misuse is likely. Permissions for outsourced delivery packages must be bound to corresponding projects to prevent unauthorized cross-project access to outsourced materials.
How to configure
The following configurations apply to FastGPT v4.17.0
| Configuration Item | Suggested Setting | Rationale |
|---|---|---|
| Team permission binding | Bind to project-specific teamId | Art assets are grouped by project to prevent cross-project resource access |
| Asset visibility scope | Limit to current project-associated tmbId | Match the project attribution logic of art assets to isolate cross-project data |
| Login-free link validity period | Set to 24 hours | Adapt to temporary access needs for outsourced collaboration, avoid long-term link exposure |
| Conversation context isolation | Divide boundaries by teamId | Internal work order Q&A needs to isolate operation and maintenance communication content for different projects |
| Resource return limit | Top 10 entries | Control the amount of asset data returned per query to reduce the risk of sensitive information leakage |
| Data update permission | Only open to art PM roles | Match the approval process for art asset updates to prevent unauthorized modifications |
Three common mistakes
- Phenomenon: When a non-project member attempts to access a specified art asset, the interface returns "no permission to access" but team permissions have already been configured. Cause: The asset is not bound to
teamId, and the permission check does not associate the project grouping rule. - Phenomenon: Login-free links do not have an effective time limit, and external personnel can access unauthorized outsourced delivery packages for a long time. Cause: The access scope bound to
tmbIdis not configured, causing the link to access full asset data. - Phenomenon: Internal operation and maintenance work orders contain art asset specification parameters from other projects. Cause: Conversation context is not divided by
teamId, resulting in no isolation of work order Q&A content for different projects.
How to confirm the configuration is complete
- Log in to the platform with a non-project member account, attempt to access the art assets of a specified project, and confirm that the corresponding resources cannot be viewed.
- Create a login-free link, set the validity period to
24 hours, and verify that the link cannot access the target resource after the validity period expires. - Initiate an internal operation and maintenance work order, query asset information for a specified project, and confirm that only asset data associated with the current
teamIdis returned in the conversation. - Attempt to modify the asset configuration of a non-current project, and confirm that the operation is intercepted by the system.
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.