What This Category’s Data Looks Like
Core data for the campaign setup scenario includes four document types: delivery plans, targeting settings, budget scheduling, and conversion tracking configurations. Data sources are advertising platform APIs, internal user profile systems, budget management spreadsheets, and attribution tools. Data updates trigger during the pre-daily-launch configuration phase, or sync per individual campaign. Document fields include targeted audience package identifiers, budget amounts, conversion event IDs, delivery time parameters, and more. There is no unified fixed format; it changes dynamically alongside adjustments to advertising account structures.
What Constraints Do These Characteristics Impose on Permission and Data Isolation
Campaign setup involves sensitive business data such as advertising budgets and targeted audiences. Data ownership is tied to different advertising accounts, agencies, or internal teams, so permission isolation must accurately match business entities. Because data updates rely on real-time API synchronization and manual configuration, permission checks cover the full process of document creation, editing, and viewing to prevent cross-team unauthorized access. Internal tickets are handled by operations duty staff. Permissions are divided by responsible regions to ensure only the corresponding operations team can process abnormal tickets for specified delivery plans. Password-free login links used as internal collaboration entry points are strictly bound to business entities, to prevent unauthorized personnel from accessing sensitive delivery data.
How to Configure Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Password-free login link permission binding | Associate teamId and tmbId, only allow team members to access | Delivery plan data is owned by the team, so links must only correspond to authorized business entities |
| Team data isolation quota | Maximum associated delivery plan data per team is 1000 MB | Matches the average data volume of daily delivery plans, prevents a single team from occupying excessive resources |
| Operations ticket permission grouping | Divide by responsible advertising account regions, each group can only see tickets for its own region | Matches the regional division of operations duty, improves ticket processing efficiency |
| Password-free login link quantity limit | Default 10 for team plans, adjustable to 100 as needed | Balances internal collaboration needs and resource usage, aligns with default subscription plan configuration logic |
| Permission check timeout | Set to 300 seconds | Covers the response duration of regular API synchronization and ticket processing, prevents normal operations from being incorrectly flagged as unauthorized |
Three Common Configuration Mistakes
- Symptom: "No permission to operate this conversation record" appears when accessing a password-free login link. Cause: The
teamIdbound to the link does not match the current user’s team ID, or the user lacks authorization to access the corresponding delivery plan data. - Symptom: Unable to create additional password-free login links after exceeding
10links for a team account. Cause: The team’s link quantity quota parameter was not adjusted in the FastGPT v4.17.0 backend, so the subscription plan’s default limit remains in effect. - Symptom: Cross-operations team access to delivery plan tickets from other regions. Cause: Ticket permission grouping was not configured based on advertising account regions, so the permission check logic does not function as intended.
How to Verify Successful Configuration
- Use a non-team member account to access a password-free login link bound to a specified
teamId, confirm that detailed configuration data for the corresponding delivery plan cannot be viewed. - Log in to the team backend, check the password-free login link quantity configuration setting, confirm it has been adjusted to the target value, such as
100. - Switch to an unauthorized operations team account, attempt to view delivery plan tickets from other regions, confirm that the corresponding content cannot be accessed.
- Check the FastGPT v4.17.0 permission check logs, confirm that the matching check logic for
teamIdandtmbIdis running normally.
The values provided here are common starting points, and should be evaluated against your own specific samples and use cases.
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.