Permissions and Data Isolation for Foreign Teacher Recruitment and Course Scheduling: Compare Documents and Locate Differences

Foreign Teachers: 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 three types of materials in the foreign teacher appointment and course scheduling scenario: appointment contracts, work permit materials, and course scheduling tables. Appointment contracts are usually signed by the hiring department and the teacher, and contain the position, appointment period, compensation, and signature page; work permit materials are submitted by administration, and contain passport information, education and qualifications, acceptance receipt, and dates; course scheduling tables are formed by academic affairs scheduling, and contain course names, classes, number of class hours, assigned teachers, and week dates. The three types of materials enter the knowledge base in batches, and the update rhythm is triggered separately by contract renewal, permit changes, and schedule adjustments, with field characteristics concentrated in names, quantities, dates, and signature receipts. After entering this feature, the three types of materials participate in file-level permission filtering in the form of files, members can only see authorized files, and retrieval also recalls from the same set.

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), 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. Viewing the list and details requires knowledge base read permission plus file read permission, deletion is limited to the creator, and retrieval is filtered by the files readable by the current member and only takes effect when authenticated by member identity.

ObjectCheckVerification action
Appointment contractWhether the contract name, appointment start and end dates, signature page, and receipt are consistent with the ledgerUse a restricted member account to view the file list and details, and check the contract name and date fields; use a collaborator account to attempt deletion, which should be filtered and prompted
Work permit materialsWhether the permit material name, acceptance quantity, acceptance and approval dates, and receipt signature are consistent with the ledgerUse a restricted member account to retrieve the same question, and check that unauthorized files are not recalled; check the authentication configuration of the workflow and nodes
Course scheduling tableWhether the course name, number of class hours, week dates, and assigned teacher signature are consistent with the ledgerUse one real record to compare the schedule and ledger field by field, and mark items where the name, quantity, or date is inconsistent
File-level permission filteringWhether the name, quantity, and date of the same record match across the two materials, and whether the versions are synchronizedUse a restricted member account to view the list and retrieve, and check the visible scope and recall set; check member affiliation by teamId and tmbId

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, and viewing the list and details did not simultaneously verify knowledge base read permission and file read permission.
  • Symptom: retrieval recalled unauthorized files. Cause: retrieval was not filtered by the files readable by the current member, or the workflow was not authenticated by member identity, so unauthorized files were still recalled.
  • Symptom: the name, quantity, and date of the same record do not match across the two materials. Cause: versions were not synchronized, or the contract, permit materials, and schedule were updated separately without writing back to the ledger, lacking signatures or receipts.

How to verify the setup

Feature acceptance: use a restricted account to view the list and retrieve once, check the visible scope and recall set, and confirm that unauthorized files do not occupy a place and are not recalled; deletion is limited to the creator, and a collaborator's attempted deletion should be filtered and prompted.

Business test: use one real record to find fields inconsistent with the ledger, and check item by item the names, quantities, dates, and signature receipts of the appointment contract, work permit materials, and course scheduling table.

  • Check member and file collaborator configuration by teamId and tmbId, and confirm that restricted members only have read permission for authorized files
  • Use a restricted member account to view the list and details and retrieve the same question, record the visible file set and recall results, and submit them to the reviewer for confirmation and write-back