Authorized access
Use an individual account and the membership provided for your work or learner relationship. Access to one institution does not authorize access to another.
Service use and responsibilities
Clear expectations make a better working relationship.
Understand how institutional access, responsible use and service arrangements fit together. The agreement accepted by your institution determines its commercial and contractual terms.
Institution-aware workflows Role-based access
THE CONNECTED INSTITUTION
Clear responsibilities. Informed decisions.- 01Confirm the service agreement
Identify the contracting parties and approved scope, including subscription, deployment, support and commercial terms.
- 02Name administrators and decision owners
Decide who manages accounts, approves sensitive changes, publishes institutional information and coordinates privacy enquiries.
- 03Brief staff, learners and guardians
Explain sign-in, appropriate use, record correction, institutional policies and how to report an issue through the agreed channel.
- 04Review changes and departure
Revisit access when a person changes duties or leaves, and use the agreed process for service changes, exports and closure.
A practical journey to explore
A CLOSER LOOK
Use the service within your institutional role.
VidyOmni supports school and education administration through institution-managed workspaces. Access is associated with an account, membership, assigned role and permitted scope. These service-use guidelines explain that model; they do not replace the institution’s executed agreement or policies.
Accurate institutional records
Enter information you are authorized to provide, verify important details and use the correction or approval workflow appropriate to the record.
Responsible handling
Handle exported reports, downloaded documents and contact information with the same care as the records inside the application.
Agreed service scope
Modules, provider connections, support arrangements, fees and any service commitments need to be confirmed for the institution’s actual deployment.
HOW IT WORKS
Agree the operating model before going live.
Make responsibilities clear for the institution, its users and the team operating the service.
- 01
Confirm the service agreement
Identify the contracting parties and approved scope, including subscription, deployment, support and commercial terms.
- 02
Name administrators and decision owners
Decide who manages accounts, approves sensitive changes, publishes institutional information and coordinates privacy enquiries.
- 03
Brief staff, learners and guardians
Explain sign-in, appropriate use, record correction, institutional policies and how to report an issue through the agreed channel.
- 04
Review changes and departure
Revisit access when a person changes duties or leaves, and use the agreed process for service changes, exports and closure.
Everyday expectations
Protect the quality of the shared workspace.
A dependable system depends on responsible actions by the people using it.
Keep credentials personal
Do not share passwords, authenticator codes or another person’s session. Report suspected compromise and use the account controls to revoke affected sessions.
Respect access boundaries
Use only records and functions required for your role. Do not attempt to bypass permissions, impersonate another user, disrupt the service or extract information without authority.
Take care with uploaded content
Upload documents and learning material only when you have authority to use them for the institutional purpose. Check that evidence belongs to the correct person and record.
Treat reports as institutional information
Check scope and recipient before sharing an export. Access checks inside the platform do not control copies after an authorized user downloads them.
Before a commitment
Confirm the details that belong in an agreement.
Public feature descriptions help evaluate the product. They do not establish institution-specific commercial or legal terms.
Providers and dependencies
External services may need separate accounts, approvals, usage charges and terms. A configured or simulated workflow is not proof that the external service is active.
Support and service levels
Confirm support hours, escalation contacts, maintenance arrangements, availability and recovery commitments in the applicable agreement. No universal SLA is created by this page.
Changes, closure and disputes
Use the institution’s agreement for renewal, cancellation, data return, liability and dispute provisions. Request the relevant document from the institution or contracting contact before accepting a commitment.
COMMON QUESTIONS
A few details
worth getting right.
Questions about your institution’s exact setup? Prepare a focused request.
Find the right contact routeDoes creating an account give me every module?
No. Access depends on the institution’s provisioned features, membership, roles and scope. An administrator can explain which functions are available to you and approve access where appropriate.
Are prices, support hours and cancellation terms fixed by this page?
No. Those are institution-specific commercial arrangements and must be confirmed in the applicable agreement or approved offer. This page does not publish a universal price, response time, refund policy or cancellation period.
Which document should our procurement team review?
Request the agreement for the proposed service, the deployment and provider details, the institution’s privacy notice and any agreed support or processing schedules. Confirm the contracting parties and approved commitments before rollout.
BUILD A CLEARER OPERATING DAY