What the data for this category looks like
Core data for campaign performance optimization comes from advertising platforms, attribution systems, CRM leads, and landing page data, with update frequencies of daily or real-time. Daily associated documents include daily and weekly reports divided by campaign period and material groups, price adjustment records, material test sheets, and optimization retrospectives. Data fields include impressions, clicks, conversion costs, budget balances, etc. There is no unified aggregation format, and data is stored split by individual campaign accounts or agency dimensions.
What constraints do these characteristics impose on permission and data isolation
Since data is stored split by campaign account, material group, and team role, and real-time advertising data requires fast permission verification, permission isolation must strictly match the split logic of business data. If the isolation scope does not match the data storage dimension, issues such as unauthorized access to sensitive documents and real-time campaign data leaks will occur. Additionally, internal ticket Q&A must be associated with exclusive campaign data for the corresponding team. The access scope for different job roles must strictly correspond to their assigned campaign account groups, to prevent core campaign data from being viewed by unauthorized personnel.
How to configure the settings
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
teamId | Bind to one or more campaign account group IDs | Match the business characteristic of campaign performance optimization data being divided by account groups |
tmbId | Associate with pre-defined role permission groups | Distinguish access scopes for different job roles such as optimizers, analysts, and interns |
| Team Access Permissions | Allocate by campaign account group | Ensure only the current team can access price adjustment records and daily reports for the corresponding account |
| Reference Source Visibility Scope | Only display documents covered by the current permissions | Prevent returning unauthorized material test sheets or cross-team retrospective documents |
| Session Data Isolation | Isolate session records by team | Avoid mixing Q&A content and data from cross-team tickets |
| Permission Check Trigger Timing | Real-time check | Adapt to real-time updated advertising data scenarios, ensure permission verification is completed before data is returned |
Three common misconfigurations
- Symptom: Intern accounts cannot create or access specified knowledge bases. Cause: The
teamIdis not bound to the campaign account group of the intern's team, and the permission configuration does not cover the corresponding data scope. - Symptom: The assistant's returned reference sources include daily and weekly reports outside the allowed permissions. Cause: No verification for reference source visibility scope is configured; only page access is restricted, not the range of documents matched during retrieval.
- Symptom: Cross-team tickets have mixed campaign data. Cause: Session isolation is not divided by
tmbId, and ticket sessions from different teams are not permission-isolated.
How to confirm correct configuration
- Log in to FastGPT v4.17.0 using an intern account, attempt to retrieve material test sheets from a non-affiliated team, confirm no matching results are returned.
- Enter the permission configuration page, verify that
teamIdhas been bound to the current team's campaign account group. - Switch to accounts with different job roles, verify that session records only display ticket and Q&A content for the corresponding team.
- Trigger a real-time advertising data query, confirm that permission verification is completed before data is returned, with no unauthorized data leaks.
The values provided here 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.