Integrations overview
Omniscol integrates with your IT system through several channels, depending on the need.
For examples of third-party tools and partners regularly connected to Omniscol, see also integrations.partners.
At a glance
| Mechanism | What it is for | Flow direction |
|---|---|---|
| iCal | Let teachers / students see their timetable in their personal calendar | Omniscol → calendar |
| Share links | Distribute a read-only timetable or open targeted data entry depending on the context | Omniscol → public web |
| Iframe | Embed a timetable in a page on the same domain as Omniscol; blocked on an external site (security) | Omniscol → same domain |
| Omniscol API | System-to-system integrations according to the account's rights and options | Depends on configuration |
| MCP | Connect an MCP-compatible AI agent to Omniscol | AI agent ↔ Omniscol |
| OAuth2 / OIDC (server) | Connect a third-party service identified by a registered client + consent + scoped token (the foundation of MCP and OneRoster) | Service ↔ Omniscol |
| OIDC / SSO (sign-in) | User authentication via an identity provider (Google Workspace, Microsoft Entra ID, generic OIDC) | Depends on configuration |
| Synchronization with external systems | ERP connector framework: Aurion, Auriga, new connectors on a project basis | Bidirectional |
| Display panels | Show the timetable on public screens | Omniscol → screens |
Choosing the right integration
- Distribute a timetable to a teacher / student — an iCal subscription.
- Give read access to a parent / an auditor — share link.
- Synchronize learners from your ERP / IT system — see Synchronization with external systems, which lists the available connectors. If your ERP is not listed, adding a connector is scoped with Omniscol support.
- Single sign-on — OIDC / SSO.
- External AI assistant on the account, when the option is enabled — MCP for compatible clients.
- Public display on the premises — display panels.
Security best practices
- Use OIDC / SSO, when the option is enabled, to authenticate real users.
- Reserve API tokens for system-to-system integrations, with minimal scope and periodic rotation.
- Set short expiry dates on share links.
- Never put an API token in a public Git repository.