Permissions and Data Isolation for Training Provider Scheduling and Lesson Records: Compare Documents and Locate Differences

Training Schedules: review permissions for document checks. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

This page focuses on material verification and discrepancy localization in the context of training institution academic scheduling and class cancellation, involving three types of materials: class schedules, class cancellation records, and class adjustment applications. Class schedules are generated by the academic affairs office during the scheduling process, with fields including course name, class, instructor, class date and time slot; class cancellation records are registered by the instructor or academic affairs office after the class is completed, with fields including student name, course name, cancellation quantity, cancellation date, and signature; class adjustment applications are submitted by the initiator, with fields including original class date, adjusted date, reason for adjustment, and approval receipt. The three types of materials have different update rhythms: class schedules are adjusted in batches weekly or monthly, class cancellation records are generated per session, and class adjustment applications flow with approval. After the materials enter this function, the class schedule serves as the baseline material, and class cancellation records and class adjustment applications serve as comparison materials. Verification is performed based on whether the name, quantity, and date of the same object are consistent across the two materials, and entries missing signatures or receipts are identified.

Configuration and implementation checks

Enable commercial file permissions and give the member read access to the knowledge base.

This step is executed by member permissions and file-level permissions (server-side authentication), outputting a set of visible files filtered by member. The "discrepancy list" is subsequently completed 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, and unauthorized files do not participate in the list and retrieval results.

ObjectCheckVerification action
Class scheduleCourse name, class, instructor, class date and time slot are consistent across the two materials, and the version is the latestUse a restricted member account to view the class schedule file list and details, and compare the course name and class date in the class cancellation records one by one
Class cancellation recordStudent name, course name, cancellation quantity, cancellation date, and signature are consistent across the two materialsConfirm the member's readable scope by teamId and tmbId, and verify whether the cancellation quantity corresponds to the class hours in the class schedule
Class adjustment applicationOriginal class date, adjusted date, reason for adjustment, and approval receipt are complete, and synchronized with the adjusted version of the class scheduleVerify the approval receipt of the class adjustment application against the class schedule change records, and include entries missing signatures or receipts in the discrepancy list
File-level permissionsViewing the list and details requires knowledge base read permission plus file read permission; deletion is limited to the creatorUse a collaborator account to attempt to delete a file; it should be filtered and prompted; use a restricted member account to search for the same issue, and unauthorized files should not be recalled

Three common errors

  • Symptom: A restricted member sees files in the file list that are not within their readable scope. Cause: File-level permissions are not filtered per member, or the workflow does not authenticate by member identity.
  • Symptom: The cancellation quantity and date of the same class cancellation record do not match between the class schedule and the class cancellation record. Cause: Versions are not synchronized, and the adjusted class schedule is not written back, resulting in inconsistent fields between the two materials.
  • Symptom: Class adjustment applications lacking approval signatures or receipts still enter class cancellation statistics. Cause: Material verification does not cover signature and receipt fields, and the discrepancy list does not record missing items.

How to verify the setup

This function acceptance: Use a restricted account to view the file list and perform a retrieval once, and check whether the visible scope only includes files readable by that member, with unauthorized files not occupying a place and not being recalled.

Business test: Use a real record to find fields inconsistent with the ledger, record discrepancies in name, quantity, or date, and submit to the reviewer for confirmation and write-back.

  • Verify the member's readable file set by teamId and tmbId, and confirm that the list and retrieval results are consistent.
  • Use a collaborator account to attempt to delete a file, and confirm that only the creator can delete, and non-creator items are filtered and prompted.