This documentation is written for FastGPT v4.17.0.
What this category of data looks like
Data for this category primarily originates from ticketing systems, chat logs, product logs, and customer contract SLAs. Update frequency is daily or real-time. Daily documents include customer tickets, issue tiering tables, processing records, and service reports. Core fields include ticket unique identifiers, customer association identifiers, issue tiering tags, response time limits, SLA compliance status, and more. Data circulates around customer-reported issues, covering the full process from acceptance to closure.
What constraints do these characteristics impose on permission and data isolation
This category of data includes sensitive customer contract SLAs and ticket details, and updates in real time alongside customer feedback. Clear boundaries exist between customer groups managed by different customer service teams. Permission and data isolation must align with team responsibility and authority boundaries. Prevent cross-team access to non-assigned customer tickets and processing records. Isolation rules must not interfere with real-time ticket circulation and tiering operations. Stop response timeouts caused by permission check delays. Ensure consistent isolation for historical ticket data, and avoid cross-team historical data leaks.
How to configure settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
teamId | Bind to the unique identifier of the corresponding customer service team, use the teamId generated when the team is created | Aligns with customer service team responsibility and authority boundaries, ensures only team members can access associated customer ticket data |
tmbId | Associate with the tmbId field of the corresponding customer ticket | Implements data isolation at the individual ticket level, prevents cross-customer ticket data leaks |
| Permission check trigger timing | Trigger during ticket loading, issue tiering, and data export | Covers core operation links, prevents unauthorized access to sensitive ticket data |
| Export data scope | Only allow filtering of tickets from the same team, single export limit is top 500 entries | Limits the scale of sensitive data exports, reduces leakage risks |
| Permission check timeout threshold | 600 seconds | Ensures permission checks do not interfere with real-time ticket processing, avoids response timeouts |
Three common configuration errors
- After configuring permission isolation-related plugins in a workflow, plugin input and output parameters are not displayed, and no error logs are generated. The cause is that
teamIdortmbIdparameters are not correctly bound to the plugin configuration, so the system cannot identify associated data for permission checks. - When multiple accounts log into the same team, users cannot view ticket data for that team. The cause is that the permission mapping for
teamIdis not correctly configured, so the association between accounts and teams does not take effect. - Field missing occurs when exporting historical ticket data. The cause is that older ticket data does not have the
tmbIdfield populated, so permission checks cannot match the corresponding team, leading to data isolation anomalies.
How to confirm correct configuration
- A non-team member account logs in, attempts to access the target team's ticket list, and access is denied or a no permission prompt is displayed.
- Permission check rules are configured, an issue tiering operation is initiated, and the operation log includes check records for
teamIdortmbId. - Ticket data from the same team is exported, and the export results only include tickets associated with the currently configured
teamId, with no cross-team data. - A permission check timeout scenario is simulated, and the system triggers a timeout prompt without interfering with basic ticket acceptance processes.
The values provided 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.