What this category's data looks like
This page covers three types of materials for enterprise compliance and security training: compliance training courseware, security operating procedures, and exam records. Courseware usually comes from the policy department and is revised on a quarterly basis or triggered by regulatory updates; its fields include course name, applicable positions, effective date, and approval signature field. Procedures come from the security management department and are updated in sync with equipment or process changes; their fields include step number, operation quantity, version number, and signature field. Exam records are compiled by the training executor and generated by session; their fields include personnel name, score, date, and receipt signature. When these three types of materials enter this feature, courseware and procedures serve as the baseline to be checked against, and exam records serve as the object to be compared, together forming the comparison surface for the name, quantity, date, and signature of the same object across two materials. In terms of update cadence, courseware and procedures are version-based, while exam records are session-based; unsynchronized versions and missing signatures are the main sources of discrepancies.
Configuration and implementation checks
Enable commercial file permissions and give the member read access to the knowledge base.
This step is enforced by member permissions and file-level permissions (server-side authentication), and outputs the set of visible files filtered by member. The "discrepancy list" is then completed by subsequent AI nodes, code nodes, or manual work; the file list and retrieval only return the readable set filtered by member. The file list and details require knowledge base read permission plus file read permission; retrieval is filtered by the files readable by the current member, and only takes effect when authenticated by member identity.
| Object | Check | Verification action |
|---|---|---|
| Compliance training courseware | Check whether the course name, applicable positions, effective date, and approval signature field in the courseware and exam records are consistent | Use a restricted member account to view the courseware list and details, confirm that only files readable by that member are returned, and then compare the fields one by one |
| Security operating procedures | Check whether the step number, operation quantity, version number, and signature field in the procedures and the ledger match | Use a collaborator account to try deleting a file not created by that person, confirm that it is filtered and a prompt is shown; then check the version number and signature field |
| Exam records | Check whether the name, score, date, and receipt signature in the exam records and the courseware and procedures are consistent | Use a restricted member account to search the same question, confirm that unauthorized files are not recalled, and then locate the inconsistent fields |
| File-level permissions | Viewing the list and details requires knowledge base read permission plus file read permission; deletion is limited to the creator | Check the authentication configuration of the workflow and nodes, confirm authentication by member identity, and check the ownership of teamId and tmbId |
Three common errors
- Symptom: a restricted member sees files in the list that they should not see. Cause: file-level permissions are not filtered item by item by member, or the list is not returned according to the current member's readable scope.
- Symptom: the name, quantity, and date of the same record do not match between the courseware and the exam records. Cause: the two materials were revised separately, without version synchronization and field-level comparison.
- Symptom: retrieval recalls unauthorized files, or a collaborator cannot delete a file. Cause: retrieval is not authenticated by member identity, and deletion is not filtered by the creator-only rule.
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 fields inconsistent with the ledger, record the discrepancies in name, quantity, date, and signature, submit them to the reviewer for confirmation, and write them back.
- Use a restricted member account to view the file list and details, check whether the returned set is consistent with file read permissions, and check the ownership of
teamIdandtmbId. - Use a collaborator account to try deleting a file not created by that person, confirm that it is filtered and a prompt is shown; then check whether the retrieval entry is authenticated by member identity.