What this category's data looks like
This page focuses on the general higher education institution admissions enrollment and filing category. Materials come from three types: enrollment plans, filing rules, and admission rosters, with an update cadence that rolls forward with batch progression and supplementary volunteer rounds. Field characteristics center on institution-major group codes, planned numbers, filing ratios, minimum score rankings, admission dates, and signed receipts. When entering this function, enrollment plans assume the role of the baseline ledger, filing rules assume the role of the judgment basis, and admission rosters assume the role of result evidence. The three are compared item by item by the name, quantity, and date of the same record, forming a discrepancy list that is written back after confirmation by the reviewer.
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), outputting 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. Team administrators do not bypass file-level permissions, and the system root and team owner are considered to have all permissions on all files.
| Object | Check | Verification action |
|---|---|---|
| Enrollment plans | The name, planned quantity, and execution date of the same institution-major group in the two materials must be consistent | Use a restricted member account to view the list and details, compare the enrollment plans with the ledger field by field, and record inconsistent items |
| Filing rules | The filing ratio, batch date, and signed receipt must correspond to the admission roster, and versions must be synchronized | Check the dates and signature fields of the rule text and the roster, and list entries with missing signatures or receipts separately |
| Admission rosters | The name, quantity, and date of the same record match the enrollment plans, and no unsynchronized versions may appear | Search the same question, verify that unauthorized files are not recalled, and confirm the visible scope by teamId and tmbId |
| File-level permissions | Viewing the list and details requires knowledge base read permission plus file read permission; deletion is limited to the creator | Try deleting with a collaborator account; it should be filtered and prompted; use a restricted member account to search the same question and verify the recall scope |
Three common errors
- Phenomenon: a restricted member saw files they should not see. Cause: file-level permissions were not filtered item by item by member, and the list and details were not validated by knowledge base read permission plus file read permission.
- Phenomenon: the name, quantity, and date of the same record do not match in the two materials. Cause: the enrollment plan and admission roster versions were not synchronized, and the discrepancy list was not written back for reviewer confirmation.
- Phenomenon: retrieval recalled unauthorized files. Cause: the workflow did not authenticate by member identity, and the preselected knowledge base scenario did not perform file-level filtering, still recalling by knowledge base permissions.
How to verify the setup
This function's acceptance: use a restricted account to view the list and search once, and verify 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 name, quantity, or date discrepancies, and submit them to the reviewer for confirmation.
- Check the set of member-visible files by
teamIdandtmbId, and confirm that the list and details are filtered correctly item by item. - Use a collaborator account to try deleting a file, confirm that non-creator items are filtered and prompted, and that deletion is limited to the creator.