If you receive the error "No Linked Account Found" after configuring Single Sign-On (SSO) and a user attempts to access https://timetabling.education
CAUSE
This message appears when the SSO login is successful, but the user’s identity cannot be matched to an existing user account in our system.
This is typically due to:
A mismatch between the SSO-provided attributes and what is recorded in your school’s Timetabling Solutions user database
The user has not yet been invited or linked to a school account in the Management Portal
Expected SSO Attributes
To successfully link a user, your identity provider must send the following attributes during authentication:
| Attribute | Description | Required |
|---|---|---|
name | Full name of the user | Yes |
givenname | First name | Yes |
surname | Last name | Yes |
emailaddress | User’s full email address | Yes |
We use the email address to link the incoming SSO user to a known user account.
How to Resolve
1. Confirm User Exists in the Management Portal
Ensure the user has already been invited and is listed under Users in your Management Portal.
Go to the Management Portal
Select Users
Verify that the user appears with the correct email address
If the user is not listed, add them manually or invite them from the Management Portal.
2. Verify Email Address Match
Check that the emailaddress being sent by your identity provider matches exactly the user’s login email in the Management Portal.
Common issues include:
Mismatched domains (e.g.
@school.edu.auvs@staff.school.edu.au)Capitalisation differences (SSO is case-sensitive in some configurations)
Typos or alternate addresses (e.g. aliases)
3. Inspect SSO Attribute Mapping
In your identity provider (Azure AD, Google Workspace, etc.), confirm the correct claim mapping:
| Identity Provider Claim | Mapped to Attribute |
|---|---|
name | name |
given_name or givenname | givenname |
family_name or surname | surname |
email or emailaddress | emailaddress |
Ensure these values are being sent to https://timetabling.education during the login process.
4. Test with a Known Working User
Try logging in with a user who has previously accessed the system via SSO. If successful, the issue is likely isolated to one user’s configuration.
Still Need Help?
If you continue to experience issues:
Confirm the affected user’s full name and email in your identity provider
Capture and send us a screenshot of the SSO attributes (or SAML assertion if available)
Create a support ticket, by clicking the Help icon inour application, then clicking Support Tickets and enter this information