What the documents look like
The operational boundary for this category sits at the point where a parcel leaves the warehouse, and carrier scan records mark where responsibility passes. The working materials are electronic waybills, handover lists, pickup scan records and exception-item registers. These come from courier systems, WMS shipment records, GB/T courier service standards and carrier billing. The brief states that updates run per batch and per day. That cadence does not change the access-control task described here, so it is noted only as a property of the source material.
For access control, the practical consequence is that visibility of waybills and handover lists, read access to pickup scan records, and edit access to exception-item registers each need checking at the team, dataset and file levels. A person who can read a dataset is not automatically able to read every file inside it once file-level permissions are enabled.
Constraints at the access controls step
FastGPT permissions combine attribute-based and role-based management. Configuration runs through members, departments and groups. Member permissions carry the highest priority; department and group permissions combine as a union; the final permission is the combination of these results. Resource types include team, app, dataset and collection.
File-level permissions are a commercial-edition feature. In the default closed state, a collection's readability matches the dataset and no collection permission records are queried. When enabled, each file or folder generates a full permission snapshot, and lists, details and retrieval recall are authorized item by item against that snapshot. Dataset permission is always the threshold: a collection permission cannot bypass dataset permission. Retrieval recall filters by the current member's readable files, and this applies only when authorization uses the current member identity. A workflow that preselects a dataset without member-identity authorization does not apply file-level filtering. A team administrator does not bypass file-level permissions.
Hypothetical paper exercise sample: a warehouse shipment group handles handover batch A-0603 on 3 June 2025. The source text reads: "Handover list A-0603 lists 120 parcels; the carrier scan record shows 118 parcels collected; the exception-item register shows 2 items pending verification." The proposed determination sentence reads: "All parcels in this batch have completed pickup handover." Comparing the sentence with the source: the source records only 118 collected and 2 pending verification, and does not state that all parcels are complete. The determination is unsupported.
Configuration and implementation checks
| Setting or check item | Related material on this page | How to check |
|---|---|---|
| Dataset manage permission | The dataset holding waybills and handover lists | Confirm the operator holds dataset manage permission, then inspect the file-level permission switch state |
| File-level permission switch | The pickup scan record file | In the closed state the collection inherits dataset permission; in the open state verify the collaborator snapshot per file |
| Collaborator configuration | The exception-item register file | Full-overwrite semantics; the submitted list must contain the current creator or it is rejected |
| Retrieval recall authorization | The pickup scan record retrieval entry | Filters unauthorized files when the current member identity is used; a preselected dataset without member authorization does not filter |
| Team administrator boundary | Datasets and files within the team | A team administrator does not bypass file-level permissions and is authorized by each collaborator configuration |
| Hypothetical exercise starting point | Visibility scope of handover batch A-0603 | This exercise uses 118 collected as the comparison starting point against 120 on the handover list; the difference of 2 corresponds to the exception-item register |
Three common errors
- Treating a retrieval relevance score as a permission filter. Input: a member searches pickup scan records and the retrieval settings include a relevance threshold. Compare: the relevance score against the file-level permission snapshot. Observable result: a relevance score does not perform permission or entity isolation; whether an unauthorized file is recalled depends on whether authorization uses member identity, not on the similarity setting.
- Treating a pending request as an approved action. Input: 2 items in the exception-item register carry the status pending verification. Compare: the pending-verification status against the completed handover status. Observable result: pending verification does not demonstrate a lack of operating permission and does not equal completed handover; the determination is unsupported.
- Treating a team administrator as exempt from file-level permissions. Input: a team administrator account accesses a dataset file. Compare: the team administrator role against the file collaborator configuration. Observable result: a team administrator does not bypass file-level permissions; the dataset and file remain authorized by their respective collaborator configurations.
How to verify the setup
- Input the hypothetical sample source text "Handover list A-0603 lists 120 parcels; the carrier scan record shows 118 parcels collected; the exception-item register shows 2 items pending verification" together with the proposed determination sentence "All parcels in this batch have completed pickup handover." Compare the proposed sentence against the source on the collected count and the pending-verification count. Condition satisfied: the proposed sentence is identified as unsupported, because the source does not state that all parcels are complete.
- Input a member account searching pickup scan records, where that account has no read permission on the target file. Compare the retrieval result against the file-level permission snapshot. Condition satisfied: if the retrieval entry authorizes by member identity, the file is not recalled; if it is a preselected dataset without member authorization, record the actual observation without inferring that recall must or must not occur.
- Input the collaborator submission list for the exception-item register file, where the list omits the current creator. Compare the submitted list against the creator record. Condition satisfied: the submission is rejected, because collaborator configuration uses full-overwrite semantics and the list must contain the current creator.