This document applies to FastGPT v4.17.0.
What this category of data looks like
Data for this category typically comes from a customer’s existing legacy systems, custom CSV/Excel templates, database export files, and FastGPT product import run logs. Daily supporting documents include standardized data import templates, migration execution plans, field mapping comparison tables, and migration effect verification reports. Data update schedules are adjusted irregularly per project, with no fixed cycle. Data fields include customer business entity attributes, mapping rule configurations, import batch identifiers, verification results, and other items. There are no unified fixed units, and they vary based on the customer’s business scenarios.
Constraints for permission and data isolation from these characteristics
Data for this category comes from scattered sources and includes the customer’s own business data. Permission configurations must strictly isolate imported datasets of different customers to prevent cross-customer data leaks. Data updates are irregular per project, so permission rules must support dynamic adjustment per individual migration project to adapt to temporarily added implementation tasks. Supporting documents include sensitive configurations such as field mappings. Operation permission levels must be differentiated between implementation consultants and customer IT liaisons to prevent unauthorized modification of mapping rules. Import run logs include operation traces and data details. Access to logs across different teams must be isolated to ensure that only in-scope task statuses can be viewed during on-duty operations.
How to set configurations
| Configuration item | Recommended setting | Rationale |
|---|---|---|
| Team data isolation scope | Divide independent data domains by teamId. Each team can only view import data and logs for its own projects | Data for this category is bound to project teams per task. Isolating by team ID accurately matches project ownership and avoids cross-team data confusion |
| Guest link quota | Bind team quotas by tmbId. Each team can create up to 100 guest links at maximum | Customer data import and migration typically associates a single project with one team. The quota limit matches the batch access needs of a single project |
| Field mapping edit permission | Only project leads can modify field mapping tables. Regular members can only view | Field mapping is a core migration configuration. Accidental changes can cause data misalignment, so edit permissions must be strictly controlled |
| Import log view permission | Only on-duty operations staff and project-related members can view import logs for their corresponding teamId | Import logs include customer data details, so access scope must be restricted to prevent data leaks |
| Cross-team data sharing | Disable cross-teamId data sharing by default. Manually enable temporary permissions only during project collaboration | Data for this category is mostly customer-exclusive. Isolation must be maintained unless special requirements apply |
Three common mistakes
- The symptom is a pop-up prompt reading "No permission to operate this conversation record". The cause is that the migration project associated with the conversation is not bound by
teamId, and unauthorized members attempt to access cross-team import ticket conversations. - The symptom is that the number of guest links created cannot exceed 10. The cause is that the quota is not adjusted by
tmbIdfor the team. The default 10-link limit of the basic team edition is enabled, failing to accommodate batch import requirements. - The symptom is a permission error during import testing after local deployment model configuration is completed. The cause is that model call permissions are not bound to the corresponding
teamId, causing the import task to fail to call the configured model for the data verification link.
How to confirm the configuration is correct
- Log in to accounts under different
teamIds. Verify that only import data and logs for the corresponding team can be viewed, and tasks from other teams cannot be accessed. - Go to the team settings page. Check the guest link quota configuration item. Confirm that it has been adjusted to a value matching project requirements.
- Attempt to modify the field mapping table with a regular member account. Verify that editing operations cannot be performed, only project leads can perform the operation.
- Initiate a test import task. Confirm that only authorized on-duty operations staff can view the running logs and results of the task.
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.