Returned-goods inspections: access controls for operations handover

Review access controls for operations handover in Returned-goods inspections. Check sources, input boundaries, error handling and repeatable test evidence.

What the documents look like

Reverse returned-goods warehouse inspection handles returned parcels and product grades; it does not handle new outbound orders. The data comes from the WMS returns module, platform after-sales, carrier return items, and the inspection station. It includes return inbound orders, inspection photos, grade determination sheets, and resale listing orders, updated by item and by day. Scanning returned items, judging status, and deciding resale or scrapping each have their own responsible parties, and handover requires checking authorization status item by item.

A hypothetical drill sample: an after-sales warehouse inspector submits a handover request. The original material reads: “Return inbound order TH-2024-0412, product A, quantity 1 item, return scan time April 12, 2024, status pending inspection. Inspection photo QC-0412-01, taken April 12, 2024, showing product A’s outer packaging damaged. Grade determination sheet pending completion.” The draft sentence is: “Please list product A at the resellable grade; the resale listing order is already available, execute directly.” The question to be determined: whether the resale listing order in this request is in an authorized executable state.

Constraints at the access controls step

The FastGPT permission system combines attribute-based and role-based management paradigms, configuring access permissions through three modes: members, departments, and groups. Member permissions have the highest priority; department and group permissions use a union principle, and final permissions are the combination of the above results. Resource types include team, app, dataset, agentSkill, and collection. Knowledge base file-level permissions are a commercial-edition-specific feature. When disabled by default, collection readability is fully consistent with the knowledge base, and the system does not query collection permission records; when enabled, each file or folder generates a permission snapshot, and lists, details, and retrieval recall are all authorized item by item according to the snapshot. Knowledge base permissions are always the threshold, and collection permissions cannot bypass them. The enablement entry point is the target row menu in the file list on the knowledge base details page, and the permission requirement is knowledge base administrator. Disabling it deletes all collaborator configurations for all files or folders under that knowledge base, and this cannot be rolled back.

Configuration and implementation checks

Configuration itemOfficially stated setting or implementation check itemRelationship to the sample on this page
Resource typeteam, app, dataset, agentSkill, collectionThe return inbound order, inspection photo, grade determination sheet, and resale listing order need clear resource-type ownership
Member permission priorityMember permissions are highest; department and group permissions are unionedThe member permissions of the inspector and inventory administrator need item-by-item checking
Knowledge base file-level permission switchDefault off; enabling requires knowledge base administrator; disabling deletes all collection collaborator configurationsIf inspection materials are stored in the knowledge base, the switch state must be confirmed
Collection permission rolesRead permission, write permission, administrator, creatorThe role required to execute resale listing in the handover request must be clear
Retrieval recall authorizationAfter file-level permissions are enabled, filtering is by files readable by the current member; it takes effect only when authorizing by current member identityRetrieval results cannot replace the authorization status of the resale listing order
Special identitiesSystem root and team owner are treated as having all permissions; team administrators do not bypass file-level permissionsCheck whether both handover parties belong to identities that bypass file-level permissions

Hypothetical test starting point: if the inspector’s permission on the resale listing order is set to read permission, the reason for choosing this value is that this role only needs to view the listing order content, and the comparison object is the administrator permission required by the inventory administrator. This starting point is a setting for this hypothetical drill, not an official default value.

Three common errors

  1. Treating retrieval recall results as authorized execution of the resale listing order. Retrieval filters by files readable by the current member, which only indicates readability, not approval or executable conditions. The sample draft sentence says “the resale listing order is already available, execute directly,” but the original material does not state approval status or authorizing subject, so this statement is unsupported.
  2. Treating knowledge base permissions as collection permissions. Knowledge base permissions are the threshold, and collection permissions cannot bypass them; after file-level permissions are enabled, lists, details, and retrieval recall are all authorized item by item according to snapshots. In the sample, if the inspector only has knowledge base read permission, write permission or administrator permission on the resale listing order collection must be checked separately and cannot be inferred from knowledge base permissions.
  3. Treating pending-completion status as completed determination. In the sample, the grade determination sheet is marked “pending completion,” and the original material does not state a grade determination result. Listing product A at the resellable grade requires the grade determination sheet to be completed and to state the determination result; pending-completion status does not constitute completed determination.

How to verify the setup

  1. Input the sample material’s original text and the draft sentence, and compare the draft sentence’s claim that “the resale listing order is already available” with what the original material states. The original material only states that the return inbound order status is pending inspection, the inspection photo shows outer packaging damage, and the grade determination sheet is pending completion. It does not state the resale listing order’s approval status, authorizing subject, or valid scope. If the comparison shows that the draft sentence’s content has no corresponding record in the original material, then the statement is unsupported, and materials must be supplemented or the draft sentence corrected.
  2. Input the inspector account and the inventory administrator account, and perform view and modify operations on the resale listing order respectively, comparing the actual visible content and operation results of the two accounts. If the inspector account can only view and the inventory administrator account can modify and configure collaborators, then the permission configuration is consistent with the role settings; if the inspector account can modify or configure collaborators, then the actual assignments of member permissions and collection permissions must be checked. Expected results are recorded according to actual observation, without prior assertion.
  3. Input the “pending completion” status of the grade determination sheet in the sample, and compare whether the generation conditions of the resale listing order include the grade determination sheet being completed. If the original material does not state the generation conditions of the resale listing order, then the condition is unknown and must be verified with the material provider; if it states that the generation conditions include the grade determination sheet being completed, then under pending-completion status the resale listing order does not have executable conditions. This comparison only addresses what the sample material’s original text states and does not infer other rules.