What this category's data looks like
This page focuses on material verification and discrepancy location in credit management for primary and secondary school teacher training. Materials come from three categories: training notices, credit recognition forms, and participant lists. They enter the system by project batch, and the update cadence is synchronized with the training cycle. Training notices provide the course name, start and end dates, and signature; credit recognition forms carry teacher names, credit amounts, recognition dates, and review signatures; participant lists record registrants, attendance, and receipts. When the three material categories enter this feature, the notice serves as the baseline source, the recognition form serves as the object to be verified, and the list serves as cross-corroboration. Field characteristics center on four categories: names, quantities, dates, and signatures. The same record often appears in two materials with different name spellings, inconsistent quantity definitions, dates spanning months, or missing signatures. File-level permissions filter item by item by member, so different roles can only see the material versions within their scope of responsibility, providing a controllable comparison set for discrepancy location.
Configuration and implementation checks
Enable commercial file permissions and give the member read access to the knowledge base.
This link is executed by member permissions and file-level permissions (server-side authentication), and outputs the visible file set filtered by member. The discrepancy list is completed subsequently by AI nodes, code nodes, or manual work; the file list and retrieval only return the readable set filtered by member. Team administrators do not bypass file-level permissions; the system root and team owner are treated as having all permissions on all files.
| Object | Check | Verification action |
|---|---|---|
| Training notice | The course name, start and end dates, and signature are consistent across the three material categories, and the version is the latest synchronized version | Use a restricted member account to view the list and details, and check the read permission and date fields of this notice |
| Credit recognition form | Teacher names, credit amounts, recognition dates, and review signatures correspond item by item with the participant list | Use the creator account to compare the recognition form with the list, and mark records with inconsistent quantities or dates |
| Participant list | Registrants, attendance records, and receipt signatures are complete, and the set is the same as the recognition form list although the order is irrelevant | Use a collaborator account to try deleting a list file; it should be filtered and prompted, confirming that deletion is limited to the creator |
| Retrieval entry | When authenticating by the current member identity, unauthorized files will not be recalled, covering the workflow knowledge base search node and search test | Use a restricted member account to search the same question, and check whether the recall results fall within the visible set |
Three common errors
- Symptom: A restricted member saw files they should not see. Cause: File-level permissions were not filtered item by item by member, or authentication was not executed by the current member identity.
- Symptom: The name, quantity, or date of the same record does not match between the notice and the recognition form. Cause: The version was not synchronized, and old-version materials remain in the visible set.
- Symptom: Retrieval recalled unauthorized files. Cause: The workflow preselected the knowledge base without authenticating by member identity, and retrieval was not filtered by readable files.
How to verify the setup
Feature acceptance: Use a restricted account to view the list and perform one retrieval, and check whether the visible scope contains only files readable by that member, with unauthorized files neither occupying a place nor being recalled.
Business test: Use one real record to find a field inconsistent with the ledger, record its name, quantity, or date discrepancy, and hand it to the reviewer for confirmation and write-back.
- Check the authentication configuration of the workflow and nodes, confirm authentication by member identity, and check whether the passing of
teamIdandtmbIdconforms to the member scope. - Use a collaborator account to try deleting a file, confirm that deletion is limited to the creator, and that non-creator items are filtered and prompted; use a restricted member account to search the same question, and confirm that unauthorized files are not recalled.