Skip to main content

Enhanced Embedding

In some situations, Intellischool products enable advanced embedding features. These are particularly useful for developers looking to embed a whitelabelled Intellischool product into another interface.

Enhancements are largely driven through JavaScript postMessage events between the parent application, and the Intellischool product embedded in either an iframe or a child window.


Refer to this section if you are a software developer seeking to embed a compatible Intellischool product into your software.



Albitros supports enhanced functionality for all embedded dashboards and whitelabelled consoles.


Dextyr supports enhanced functionality for:

  • Contact update forms
  • Electronic forms
  • Parent-teacher interview/conference bookings
  • Payments

Using postMessage events#

To take advantage of Intellischool's enhanced embedding capabilities, you will need to configure appropriate JavaScript functions within your application. This usually consists of two functions:

  1. A listener that listens for events and emits an action accordingly; and
  2. A dispatcher that send events back to the embedded Intellischool product.

Listener example#

This example listens for events from an Albitros embedded component, ensuring that the event is genuinely from Albitros and triggers a function in response to the event.

window.addEventListener("message", event => {
  // Check that the event is from a trusted source  if (![      "",      ""    ].includes(event.origin)  )    return;    // Act on the event  if ( && && typeof( === "object")  {
    switch (    {
      case "navigate":        if ( {          let { url, pathname, search, hash } =;          // Do something with the url and/or path received        }        return;
      default:        // Unknown event, do nothing        return;
    }  }}, false);

Dispatcher example#

This example dispatches navigate events to an embedded Intellischool product, telling it to navigate to the given destination.

const embedded_iframe = document.getElementById('embedded-iframe-id');
const onButtonClicked = () =>   dispatchIntellischoolEvent('navigate',{ path: '/new/path' });
function dispatchIntellischoolEvent( action, data = {} ){
  embedded_iframe.contentWindow.postMessage({    intellischool: {      action,    }  }, window.location.url);

Object definitions#


Represents a launch event - for example, a user launching into a dashboard in Albitros. When configured, the launch event takes precedence over a navigate event.


This object is only available for partners with a whitelabel agreement, and is emitted by embedded consoles only - for example, a whitelabelled Albitros console within another product.

A launch event is designed to give parent applications the chance to launch the given resource via their own means - for example, in a modal window, or a different frame. They must be acknowledged by the parent application within 500ms (half of one second), or the embedded application will launch the requested resource directly.

Listening for launch events#

Launch event object
{  "intellischool": {    "action": "launch",    "location": {      "url": "",      "pathname": "/pathname",      "search": "?param1=123&param2=abc",      "hash": "#anchor-fragment"    },    "title": "My dashboard",    "authenticated": true  }}

Either the url or a combination of the pathname, search and hash values can be used to determine where your application should be directing the user to launch the dashboard. Where there are no query parameters or no window fragment in the URL, the launch request will omit those parameters.

The title value provides a meaningful name for the resource being launched in to. It can be used for naming modals or windows, or providing other context to your users.

The authenticated value defines whether or not the user has already been authenticated at the destination url through a browser session, cookie or other authentication mechanism. When true, your application should not attempt to alter or attach a token to the given url.

If the authenticated value is false, your application should launch the given url using LTI Launch.

Acknowledging launch events#

Launch response object
{  "intellischool": {    "action": "launch",    "status": "success"  }}

If a parent application is launching the given resource (rather than the embedded application launching), then the parent should send a message to the embedded application that indicates a status of success.

If your application is not launching, but you want to expediate the process and skip the 500ms time-out, respond with a status value of ignored.

Values other than status or ignored will result in an error being logged in the end user's browser console, and the embedded application will continue the launch after the timeout period.


Represents a navigational event - a user changing routes within an embedded application.

These events are bi-directional:

  • Events emitted from an embedded Intellischool product can be used to track a user's location within an iframe element (or other window). This can be particularly useful if integrating Intellischool routes with your own product's routing system in single-page apps.
  • Events dispatched to an embedded Intellischool product inform the product to navigate to the given URL or path.
Navigation event object
{  "intellischool": {    "action": "navigate",    "location": {      "url": "",      "pathname": "/pathname",      "search": "?param1=123&param2=abc",      "hash": "#anchor-fragment"    }  }}

Events emitted from an embedded Intellischool product will always contain the url and pathname + search + hash values.

Events dispatched to an embedded Intellischool product may container either or both of the url and path + search + hash values.