Your students sign in with their school account

No new password: students type their school address, authenticate with you, and land on toGaether already attached to the institution.

Three screens, no more

The student types their school address
toGaether recognises the domain (for example @student.your-school.fr) and knows it belongs to your institution.
They authenticate with you
They are sent to your directory's sign-in page, with your rules: two-factor authentication, password policy, access conditions.
They come back signed in and attached
Their account is attached to the school without manual approval. If they already had an account, that is the account they get back, with their associations and roles.

Two standards cover almost every institution. If your identity provider speaks either one, it works with toGaether.

SAML 2.0: Shibboleth, LemonLDAP::NG, ADFS, and academic federation identity providers.
OpenID Connect: Microsoft Entra ID, Google Workspace, Okta, Keycloak and any standard OIDC provider.

Authentication stays with youtoGaether never sees the directory password. It receives an assertion signed by your identity provider.

Only the attributes it needsEmail address, first name and last name are enough. No other attribute is required.

One person, one accountA student who signed up before SSO was enabled gets their existing account back: no duplicate, no lost history.

Web and mobile appThe same sign-in works on the website and in the iOS and Android app.

School SSO

We configure the connection with your IT team. We need:

In return, we send you what to declare on the directory side (service identifier, return URL).

Tell us which identity provider your institution uses: we reply within one business day.