Browse help docs
Connecting the systems you already run
How a connection is set up and what its health means. Read the last step first if you are evaluating: credentials are yours, and connecting is a setup conversation rather than a switch.
For IT leads and school administrators · reviewed 23 August 2026
The 1 points where someone must decide
Everything else can be worked on in any order. These cannot move without a person.
- ConnectingAvailable → Connected
Pick from the catalogue
/admin/integrations
Mrs. Johnson
Teacher
Catalogue
Catalogued is not running
Google Workspace
Not connected
Microsoft 365
Not connected
Student information system
Not connected
Student information systems, Google Workspace, Microsoft 365, payment providers and messaging tools appear as available until a school connects them. Available means catalogued, not running.
Register your own application with the provider
/admin/integrations
Mrs. Johnson
Teacher
Register your own application
The credentials are yours, not ours
Client ID
Issued from your Google admin console
Client secret
Never stored by skodle
Redirect URI
Registered with the provider
This is the step that blocks go-live when nobody was told about it.
A real connection needs credentials the school issues from its own provider account. skodle never stores them for you and cannot create them on your behalf — this is the step that makes the connection yours rather than ours.
Plan for this in an implementation. It is usually a short task for whoever administers your Google or Microsoft tenancy, and it is the thing that blocks go-live when nobody was told.
Gate · Connecting
Available → Connected
The connection record holds configuration and health, never credentials. Connecting requires the school to register its own application with the provider, which is why this cannot be completed from inside skodle alone.
Watch the health
/admin/integrations
Mrs. Johnson
Teacher
Health
Failing and switched off are different
Google Workspace
Syncing · last run 09:05
Payment provider
Credentials expired 3 days ago
Legacy SIS
Turned off deliberately
A live connection is connected; one that is failing is in error; one deliberately switched off is disconnected. Error and disconnected are kept apart so a broken sync is not mistaken for an intentional pause.
Know what is honest about this today
/admin/integrations
Mrs. Johnson
Teacher
What is honest today
Ask for it against your own stack
Connection management
Built and working
Catalogue and health
Built and working
Moving live data
Needs your credentials configured
Treat integration as an implementation task with a date, not a switch.
Connection management is built and the catalogue is real. Moving live data depends on your credentials being configured, so treat integration as an implementation task with a date rather than something that works on the first sign-in.
Ask for it to be demonstrated against your own stack during evaluation. That is a fair request and the honest answer is more useful than a green tick.
Who can approve what
Designations are assigned in IB roles and are separate from the account role somebody signs in with.
| Designation | Sees | Approves |
|---|---|---|
| Admin and IT | Every connection and its health | Connecting and disconnecting |
| Everybody else | Nothing | Nothing |
If something looks empty
A connection sits at available
It is catalogued but not connected. Connecting needs credentials from your own provider account.
A connection shows error
It was connected and is now failing, which is different from being switched off. Check the credentials first — they expire.
Still stuck?
Bring the unit you are working on. Thirty minutes with someone who has taught the programme.