What Data Looks Like for This Category
This category's data primarily comes from advertising platform APIs, user profile datasets, internal budget spreadsheets, and attribution tools. Core daily output documents include campaign plans, targeting setting rules, budget scheduling tables, and conversion tracking configuration items. Data update frequency is mostly daily synchronization or triggered updates per individual campaign. Data fields include campaign plan IDs, targeted audience tags, budget amounts, conversion event IDs, etc. Field formats must strictly match the definitions of their corresponding data sources.
Constraints Imposed on Permissions and Data Isolation
Campaign setup scenario data involves sensitive content such as advertising account permissions, budget amounts, and targeted audience rules. The operational scope of different teams or members must be strictly differentiated. Data sources include multiple external advertising platforms and internal tools, so cross-team data calls must avoid data leakage risks. Campaign plans have a high update frequency, so permission checks must adapt to near-real-time operation scenarios to prevent permission conflicts caused by delays. The sensitivity level varies across different documents; targeting settings and budget schedules require higher permission tiers than basic campaign plans to prevent unauthorized modification of core campaign parameters.
Configuration Settings
This document applies to FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Team Permission Partitioning | Create independent permission groups for each advertising agency or growth team using teamId | Campaign plan data is stored under the ownership of teamId, enabling precise isolation of campaign resources across different teams |
| Member Permission Binding | Bind members to corresponding permission groups via tmbId, allowing only group members to operate data belonging to their team | The member unique identifier tmbId clearly defines the operating subject, preventing cross-team unauthorized access |
| Data Storage Limit | Configure a single-team data storage threshold of 1000 MB | The total storage volume of documents such as single-team campaign plans and targeting settings typically falls in the hundreds of MB range; 1000 MB covers conventional scenarios |
| Permission Check Timing | Trigger checks each time a campaign plan modification request is submitted | Campaign plans have a high update frequency; real-time checks can promptly intercept unauthorized operations |
| Cross-Team Data Switch | Disable cross-team data query permissions by default, only allowing manual activation by administrators | Campaign plans include sensitive information such as budgets and targeting settings; default isolation reduces data leakage risks |
| Permission Cache Duration | Configure permission check cache to 600 seconds | Balances real-time performance and system load, adapting to the near-real-time update rhythm of campaign plans |
Three Common Misconfigurations
- Scenario: Empty results are returned when cross-team calls are made to attribution data associated with a campaign plan. Cause: The binding relationship between
teamIdandtmbIdwas not configured correctly, resulting in permission checks blocking cross-team data requests. - Scenario: The front-end page cannot display the campaign plan creation entry. Cause: The member was not bound to the corresponding permission group via
tmbId, resulting in failed permission checks. - Scenario: Permission check results are not updated promptly after modifying a campaign plan. Cause: The permission cache duration was set too long, causing old permission cache to not refresh in a timely manner.
How to Verify Successful Configuration
- Access the permission group linked to a specified
teamId, attempt to access campaign plan data belonging to a different team, and confirm that the operation is blocked. - Bind a member to the corresponding permission group via
tmbId, and verify that the member can normally edit documents related to their team’s campaign plans. - Submit a campaign plan modification request, confirm that the permission check process triggers normally with no abnormal errors.
- Adjust the permission cache duration configuration, and verify that system behavior matches the recommended setting.
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.