Permissions and Data Isolation for Continuing Education Training Hour Recognition: Compare Documents and Locate Differences

Continuing Education: 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 addresses the continuing education credit recognition scenario, where materials come from three categories: course filing forms, study certificates, and credit recognition forms. Course filing forms are submitted by the course-offering unit and record the course name, class hours, and filing date; study certificates are issued by the learner or the unit and record the study start and end dates and completion status; credit recognition forms are summarized by the recognition institution and record the recognized quantity, signature, and receipt. The three types of materials enter the feature in batches, and the update cadence follows the application cycle and review write-back. Field characteristics are concentrated in four categories: name, quantity, date, and signature. The same record often appears in different materials with inconsistent name spellings, different quantity calibers, dates spanning months or years, unsynchronized versions, and missing signatures or receipts. When materials enter this feature, each has a different role: course filing forms are used to compare course calibers, study certificates are used to verify study facts, and credit recognition forms are used to confirm recognition results. Together, the three support discrepancy localization.

Configuration and implementation checks

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

This link 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 subsequently completed by AI nodes, code nodes, or manual work; the file list and retrieval only return the readable set filtered by member. Member permissions and file-level permissions only determine the visible scope and do not judge whether material content is consistent, and team administrators do not bypass file-level permissions.

ObjectCheckVerification action
Course filing formWhether the course name, class hours, filing date, and signature correspond to the study certificateUse a restricted member account to view the list and details, and check whether the file read permission covers only the scope that should be visible
Study certificateWhether the study start and end dates, completion quantity, and issuing signature are consistent with the credit recognition formUse a collaborator account to attempt deletion, confirm that only the creator can delete, and that non-creator items are filtered out with a prompt
Credit recognition formWhether the recognized quantity, recognition date, signature, and receipt align field by field with the ledgerUse a restricted member account to search for the same issue, check that unauthorized files are not recalled, and that the authentication method follows member identity
File list and retrievalWhether the list and retrieval return according to the member-readable set, and whether paginated results are correctCheck the authentication configuration of the workflow and nodes, and confirm that authentication by member identity takes effect

Three common errors

  • Symptom: a restricted member sees files they should not see. Cause: file-level permissions are not filtered member by member, and the list and details do not simultaneously verify knowledge base read permission and file read permission.
  • Symptom: the name, quantity, and date of the same record do not match across two materials. Cause: the course filing form and study certificate versions are not synchronized, and write-back does not check ledger fields item by item.
  • Symptom: the credit recognition form lacks a signature or receipt. Cause: signature collection is not completed before materials enter review, the discrepancy list does not mark missing items, and the write-back step is not closed-loop.

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 returns 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, locate name, quantity, or date discrepancies, and hand them to the reviewer for confirmation and write-back.

  • Check the member-visible set by teamId and tmbId, and confirm that the list and retrieval return according to that set.
  • Use one real record to compare the course filing form, study certificate, and credit recognition form field by field, mark discrepancies, and write back the review result.