For teachers and students to use the Third Space Learning platform and Virtual classroom, a few simple changes need to be made to your school’s firewall and / or web filtering system. This document lists the essential changes you (or your IT team) will need to make to ensure Third Space Learning sessions can run effectively in your school.

If you have any concerns about the feasibility of implementing these changes in your school then please speak to your program manager or our support team.

The required set up is different depending on whether your school uses a firewall, proxy, web filter or a combination of the three. Please see the relevant sections below.

If you would like more information on why we require the following changes for Third Space Learning to function effectively, please read the Third Space Learning services section below.

If your school uses a firewall, the following destinations and ports need to be whitelisted.

If your school uses a proxy or web filter that blocks HTTPS traffic on port 443 you should put the following urls on an allow list. You need to make sure:

The TSL platform is hosted by Amazon Web Services (AWS) and uses the Simple Storage Service (S3). For the platform to function properly, you need to make the changes outlined in the table above.

The Third Space Learning virtual classroom allows tutors and students to communicate through distinct audio and messaging layers.

Tutors and students communicate through a secure, shared audio-only channel using the Amazon Chime SDK (https://aws.amazon.com/chime/chime-sdk/), which uses WebRTC (https://en.wikipedia.org/wiki/WebRTC).

We use Ably (https://ably.com/) for non-audio classroom communication. The messaging layer works through the *thirdspacelearning.us domain.

We use Rollbar (https://rollbar.com/) for error logging and reporting.

We use LaunchDarkly (https://launchdarkly.com/) to selectively release features and platform changes to our users.

Document version history