Purpose-specific consent
Consent records capture a purpose, stated basis, notice version, status, evidence and optional expiry. Authorized staff can record granted, denied, withdrawn and expired states.
Stewardship in daily work
Give every sensitive record a purpose and an owner.
Responsible education administration connects access, consent, careful collection and record review. VidyOmni provides specific controls to help institutions put those responsibilities into practice.
Institution-aware workflows Role-based access
THE CONNECTED INSTITUTION
Clear responsibilities. Informed decisions.- 01Map the purpose
Identify the workflow and necessary fields. Separate an operational need from optional information and identify records that need additional care.
- 02Explain and record
Publish the institution’s notice and capture consent evidence where the process calls for it, using a meaningful purpose and notice version.
- 03Limit access and sharing
Assign roles and scopes deliberately. Check exports, recipients and external providers before information leaves the application.
- 04Review corrections and retention
Use an authorized review to handle inaccuracies, consent changes and closure requests, recording what was decided and any reason for retaining information.
A practical journey to explore
A CLOSER LOOK
A control works best inside a clear institutional process.
The platform can restrict a record, capture a consent decision or record an approval. The institution still needs to decide what information it needs, who may use it, how long it should be kept and who answers a learner or guardian’s questions.
Restricted identifiers
PEN, APAAR, ABC and scholarship identifier creation requires a matching active consent. Values are encrypted, with masked display values used for presentation.
Relationship-aware access
Permissions and scope checks govern staff actions and applicable learner or guardian access. Restricted care information has additional role-sensitive handling.
Recorded decisions
Governed record changes preserve decision context through history and audit events, helping authorized teams explain what happened and why.
HOW IT WORKS
Make data review a repeatable practice.
Assign practical ownership at the point information enters, changes and leaves the workspace.
- 01
Map the purpose
Identify the workflow and necessary fields. Separate an operational need from optional information and identify records that need additional care.
- 02
Explain and record
Publish the institution’s notice and capture consent evidence where the process calls for it, using a meaningful purpose and notice version.
- 03
Limit access and sharing
Assign roles and scopes deliberately. Check exports, recipients and external providers before information leaves the application.
- 04
Review corrections and retention
Use an authorized review to handle inaccuracies, consent changes and closure requests, recording what was decided and any reason for retaining information.
A shared operating discipline
Know which decisions the institution must make.
Software capabilities support stewardship; they do not establish a blanket legal compliance outcome.
Notice and points of contact
Identify the organization responsible for the records, its contact route, purposes and applicable policies. Admission notices can be configured on institution public sites.
Guardian and requester checks
Confirm that someone requesting access or a change is entitled to act for the record. Use a secure institutional channel to review identity or guardian evidence.
Retention and exceptions
Set a record-specific retention approach and review any requirement to preserve a record. This product page does not claim an automated retention schedule, legal-hold engine or universal deletion period.
Providers and downloaded copies
Review what enabled services receive and how authorized staff handle exports. Access protections inside VidyOmni do not automatically govern a downloaded copy or a separate provider account.
COMMON QUESTIONS
A few details
worth getting right.
Questions about your institution’s exact setup? Prepare a focused request.
Find the right contact routeDoes the consent record prove every privacy requirement is satisfied?
No. It records the institution’s stated purpose, basis, notice and decision evidence. Whether a particular collection or use is appropriate depends on the facts and requirements applicable to that institution.
Can a guardian directly delete the learner record?
There is no general self-service deletion workflow represented here. A guardian should contact the institution, which must verify the relationship, review the request and explain what can be removed or must be preserved.
Are retention and data-rights requests fully automated?
No. Purpose-specific consent and access controls are implemented, but a general automated retention or data-rights request engine is not claimed. Route those requests through the institution’s designated administrator and keep a record of the review.
BUILD A CLEARER OPERATING DAY