What the documents look like
For document comparison in Marketplace promotions, this page examines FastGPT access controls. Inspect users of registration, approval and inventory resources separately, without deriving access from campaign classification or approval titles. The examples are hypothetical.
Constraints at the access controls step
A comparison exercise assigns registration review to operations, approval review to finance and stock review to sales planning. All concern one campaign but need different sources. Test resources individually with actual accounts, recording originals and operations. If a registration-only identity reads internal calculations, retain the response to investigate scope. Campaign labels organize material without granting all members access. A job title in an approval table configures no team role; map responsibilities to specific accounts and resources.
Configuration and implementation checks
| Permission check | Campaign-comparison allocation | Actual evidence |
|---|---|---|
| Reading needs | Operations registration, finance approval, planning stock | Account, resource and operation tests |
| Scope failure | Registration identity reads internal calculation | Retain full response |
| Platform boundary | Separate sources for the same product | No grant merging from a shared name |
| External source | Campaign backend and ERP interface | Separate authentication and internal grants |
| Content and execution | Planned lock, availability and approval differ | Confirm backend records and owner decision |
Documented conditions
| Documented item / implementation check | Condition |
|---|---|
Team roles | Inspect roles for the actual member identity. |
Resource permissions | Inspect reading, editing and management by resource. |
Document classification | Classification and tags do not replace authorization. |
External-system permissions | Verify external-interface authentication separately. |
Per-account validation | Test the same source with authorized and unauthorized accounts. |
Three common errors
- If registration, finance and stock responsibilities become configured roles, inspect actual account resources and operations. Activity labels and titles establish no grants automatically.
- If a registration identity reads internal calculations or another platform’s stock, retain source identities and full response. Shared product names cannot merge platform permissions.
- If ERP or campaign readability becomes internal rights or secured stock, inspect authentication, grants and events separately. Planned locking establishes neither availability nor commercial approval.
How to verify the setup
Ask operations, finance, planning and denied identities about the same campaign, recording sources read, operations allowed and denials. Paraphrased restricted approval text needs full-response inspection even with no displayed attachment. If access works as intended but another period is used, inspect input versions separately. Retain unresolved permission and content items. Actual registration, approval and inventory changes still require backend records and owner confirmation, rather than completion inferred from the comparison conversation.
| Material context | Scope |
|---|---|
| Document types | Activity Registration Form, Promotional Price Approval Form, Inventory Lock Sheet and Activity Review Form |
| Candidate sources | Tmall Marketing Backend, JD Activity Backend, ERP Inventory and Historical Transaction Prices |
| Technical baseline | FastGPT v4.17.2 |