What the documents look like
Export tax rebate filing takes place after goods leave the country and matches tax vouchers to the export record. The working materials come from the electronic tax bureau, the export rebate filing system, customs electronic messages and the financial ledger. Day-to-day documents include the export tax exemption and rebate filing form, the export customs declaration, purchase invoices and foreign exchange receipt vouchers. Updates arrive monthly or per batch. Matching invoices to customs declarations, generating filing data and handling query feedback consume the most time.
These materials sit in different systems and belong to different posts. Access control and data isolation decide which voucher a person can see during handover and who can only submit a request. A tax accountant may hold write permission on one file while a colleague holds read permission on the same file. The colleague's ability to act depends on the actual permission record, not on the handover conversation.
Constraints at the access controls step
FastGPT manages access through three layers. Team permissions cover creating apps, creating knowledge bases, creating team API keys and managing members. Knowledge base permissions cover use, edit and manage. File and folder permissions, called collection permissions, apply only after file-level permission is enabled for that knowledge base. The knowledge base permission is always the threshold; a collection permission cannot bypass it. When file-level permission is enabled, the system generates a full permission snapshot for every file and folder, and list, detail and retrieval recall all authenticate against that snapshot item by item. Retrieval recall filters unreadable files when authentication runs under the current member identity. A relevance score does not act as a permission filter, and a similarity setting does not exclude unauthorized records. A pending review state does not equal granted operating permission, and submitting a request does not equal authorized execution.
Hypothetical paper exercise sample. A foreign trade enterprise tax accountant plans to hand a batch of export rebate filing materials to a colleague. The material text reads: "Export customs declaration number XXX, export date 15 March 2024; purchase invoice number YYY, invoice date 10 March 2024; foreign exchange receipt voucher number ZZZ, receipt amount consistent with invoice amount. This batch is currently held by the tax accountant with file write permission; the colleague holds read permission only." The draft sentence to be judged is: "This batch of export rebate filing materials has completed handover, and the colleague may modify the filing data on behalf." Judging whether this draft sentence holds requires checking whether the colleague holds file write permission and whether the handover request has been approved.
Configuration and implementation checks
| Configuration item | Documented setting or implementation check | Relation to the sample |
|---|---|---|
| Team permission | Creating knowledge bases and managing members are basic team operations | Confirm the team and member permissions of the tax accountant and the colleague |
| Knowledge base permission | Use, edit and manage are the three levels | Confirm the authorization scope of the knowledge base holding this rebate material |
| File-level permission switch | Closed state inherits knowledge base permission; open state authenticates item by item | Confirm whether file-level permission is enabled for this batch |
| Collaborator role | Read, write, admin and creator | Check the colleague's current role, which is read |
| Full overwrite semantics | The submitted collaborator list is the final result | If permission is changed, the list must include the creator to avoid deleting that record |
| Retrieval recall authentication | Unreadable files are filtered when authentication runs under current member identity | Confirm that retrieval results do not replace the permission decision |
Hypothetical starting value for this exercise: change the colleague's role from read to write. This starting point is chosen because the sample states the colleague currently holds read permission only, which contrasts with the write permission the draft sentence requires. The comparison method is to check the actual value of the colleague's role in the collaborator list before and after submission.
Three common errors
- Treating retrieval relevance as an authorization filter. Input: the colleague retrieves this batch while holding read permission. Compare the retrieval settings with the file-level permission record. Observe whether the retrieval result contains a file the colleague cannot read. Judging access by similarity score alone leaves the permission check unfinished.
- Treating a pending request as approved. Input: the handover request sits in pending review. Compare the request state with the authorization record. Observe whether an approved write permission change exists. A pending state does not show that operating permission is absent, and it does not equal granted authorization.
- Treating a full overwrite submission as an incremental addition. Input: the submitted collaborator list does not include the creator. Compare the submitted list with the creator record. Observe whether the system rejects the submission. Under full overwrite semantics, the list is the final result.
How to verify the setup
- Input the sample material text and the draft sentence. Compare the colleague's current role with the write permission the draft sentence requires. Observe whether the colleague's role is write. If it remains read, the draft sentence does not hold.
- Input the handover request from the sample. Compare the request state with the authorization record. Observe whether an approved permission change exists. If the request remains pending review, the handover is not complete.
- Input the collaborator list submission. Compare the submitted list with the creator record. Observe whether the submission is rejected. If the list does not include the creator, the submission is rejected and must be completed before resubmission.