Messaging adapters
Email, WhatsApp, SMS, push and webhook delivery have channel-specific adapters. Sending depends on enabled configuration, credentials, recipient settings and provider acceptance.
Connected with care
Choose the connections your institution can stand behind.
Communications, identity, payments and campus services have different provider requirements. Evaluate each connection with clear ownership, configuration and acceptance evidence before using it with live school operations.
Institution-aware workflows Role-based access
THE CONNECTED INSTITUTION
Clear responsibilities. Informed decisions.- 01Define the purpose and owner
Name the workflow, the team responsible, the information leaving the system and the account that will own provider billing.
- 02Check implementation and configuration
Review the specific adapter or workflow with the deployment team. Enter credentials securely and confirm the correct endpoints and sender identities.
- 03Test actual outcomes
Use controlled records to check delivery or callback behavior, failure handling, recipient preferences and duplicate or retry cases.
- 04Enable and observe
Approve production use only after acceptance, then monitor outcomes and recheck the connection when credentials, provider rules or institutional needs change.
A practical journey to explore
A CLOSER LOOK
A provider option is the beginning of a connection.
VidyOmni separates institutional workflows from external service configuration. Some channels have delivery adapters; other areas currently offer reference records or simulated evaluation flows. Availability on this page does not mean a provider is connected to your institution.
Google sign-in
A configured Google identity connection can appear on the login screen. Client credentials, callback URLs and allowed domains need to be verified for the deployment.
Payment references
Fee workflows can hold provider order and payment references. Payment configuration includes Razorpay settings; this does not establish live checkout, settlement or provider reconciliation.
A visible evaluation mode
Local notification adapters and selected learning flows identify simulated results, helping teams distinguish an evaluation from actual delivery or an external service response.
HOW IT WORKS
Make every connection an owned rollout.
Confirm a real end-to-end outcome, including failures and privacy implications, before enabling a channel for the institution.
- 01
Define the purpose and owner
Name the workflow, the team responsible, the information leaving the system and the account that will own provider billing.
- 02
Check implementation and configuration
Review the specific adapter or workflow with the deployment team. Enter credentials securely and confirm the correct endpoints and sender identities.
- 03
Test actual outcomes
Use controlled records to check delivery or callback behavior, failure handling, recipient preferences and duplicate or retry cases.
- 04
Enable and observe
Approve production use only after acceptance, then monitor outcomes and recheck the connection when credentials, provider rules or institutional needs change.
What to evaluate
Different capabilities need different evidence.
Use these categories to make an implementation plan, rather than assuming every named service is available out of the box.
Messages and notifications
SMTP email, Meta WhatsApp, a generic SMS gateway, Expo push and signed webhooks have delivery adapters. Confirm provider approval, templates, sender configuration and delivery reporting for the chosen channel.
Maps and vehicle location
Transport workflows accept telemetry and present its freshness and simulation status. A real GPS-device feed and map-provider arrangement need separate implementation and validation; a route record is not a live device connection.
Online meetings
Learning workspaces can schedule provider-labelled online-class sessions and store a recording-consent setting. Automatic external meeting provisioning is not represented as a verified live connection.
Files and storage
Storage configuration includes local and S3-compatible options. Confirm the actual file workflow, access controls, object location, backup and recovery arrangements for your deployment.
AI learning assistance
The current tutor workflow uses approved-source answers and marks responses as simulated. AI provider settings are configuration foundations; they do not establish a live model connection or a promise about an external provider’s data handling.
Payments and finance
Invoices, collections and receipts are application workflows. Ask for separate proof of any proposed live gateway, signed webhook, refund and settlement process before relying on online collection.
COMMON QUESTIONS
A few details
worth getting right.
Questions about your institution’s exact setup? Prepare a focused request.
Find the right contact routeAre all integrations included and active when we sign up?
No. Activation depends on the deployed capability, enabled channel, credentials and institutional acceptance. Provider subscriptions, usage charges, approvals and account ownership need to be agreed separately.
How can we tell a demonstration from a live result?
Simulated notification and learning results carry simulation metadata. Ask the implementation team to show the relevant mode and actual provider evidence, such as receipt in a controlled recipient account, rather than relying only on a successful screen action.
Can we bring an existing provider?
Share the provider name, intended workflow and technical requirements during implementation. Existing adapters or configuration may cover part of the need; a connection outside those capabilities needs a scoped technical review before availability can be confirmed.
BUILD A CLEARER OPERATING DAY