What the Data for This Category Looks Like
Data for this category centers on the full lifecycle of advertising campaigns. Daily documents include advertising review forms, qualification attachments, delivery records, and rectification notices. Data sources include delivery logs exported from advertising platform backends, qualification documents submitted by customers, cooperation agreements synchronized from contract systems, and compliance rule documents publicly released by regulators. Data updates trigger when a single advertising campaign launches, or synchronize in batches on a monthly cycle. Each document corresponds to the full compliance chain information for a single advertising campaign, including core fields such as review number, qualification validity period, and delivery time window.
What Constraints These Characteristics Impose on Permissions and Data Isolation
Data for this category is categorized by advertising campaign and customer entity, and includes sensitive compliance information such as customer qualifications and delivery records. This requires permission isolation to accurately match data attribution dimensions. Data updates trigger on campaign launch or monthly synchronization, so isolation configurations must support dynamic adjustment of permission ranges based on campaign cycles. Sensitivity levels vary across document types: qualification attachments are high-sensitivity data, while delivery records are operational compliance data. Graded permission controls are required to manage access. Unauthorized data access can lead to serious consequences such as regulatory penalties and customer accountability, so the isolation mechanism must include complete operation traceability capabilities.
Configuration Settings
These configurations apply to FastGPT v4.17.0:
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
teamId | Unique identifier bound to the customer entity | Divide permissions by customer entity to match customer qualification attribution in data sources |
tmbId | Unique identifier bound to a single advertising campaign | Isolate data by advertising campaign dimension to match campaign-level trigger logic for data updates |
| Team invitation validity period | 7 days | Balance permission configuration efficiency and security, avoid risks from long-lasting invitation links |
| Account isolation scope | Divided by customer/campaign two levels | Cover the two core data attribution dimensions for this category, adapt to daily document classification logic |
| Permission audit retention period | 12 months | Meet basic compliance evidence retention requirements, match storage periods for compliance materials required by regulators |
| Single team data storage limit | 1000 GB | Adapt to storage scale of single campaign data for this category, avoid insufficient storage impacting data retention |
Three Common Configuration Errors
- Issue: After a team invitation is sent, the invited party does not receive any in-site message or email notification. Cause: Dual push configuration is not enabled, and only a single notification channel is enabled, leading to lost notifications.
- Issue: Multiple teams cannot be created after server setup, or the corresponding team space cannot be switched to after creation. Cause: The account isolation scope divided by
teamIdis not configured, and the system uses the global single-team permission mode by default. - Issue: Cross-customer advertising compliance materials are accessed by unauthorized teams. Cause:
tmbIdis not bound to advertising campaigns, resulting in permission isolation not matching the campaign dimension of data attribution.
How to Verify Proper Configuration
- Send a team invitation, check if the invited party receives both in-site messages and email notifications, to confirm the notification configuration is effective.
- Switch between team spaces corresponding to different
teamIdvalues, check that only advertising compliance materials for the corresponding customer are visible, to verify the permission isolation scope configuration is correct. - View permission audit logs, confirm all team operations are fully recorded, to verify the traceability configuration is enabled.
- Check storage directory structures, confirm independent folders divided by
teamIdandtmbIdexist, to verify storage isolation configuration is effective.
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.