Single sign-on
SAML 2.0 single sign-on on the Enterprise plan, set up with us. Not yet tested against a live institutional identity provider.
Enterprise only, and set up for you
SSO is not self-serve — there is no SSO panel in your Settings. Email hello@incredify.net and we'll configure it with your identity team.
Incredify supports SAML 2.0 as a service provider. It has not yet been run against a live institutional identity provider, so expect a joint test with your identity team during setup.
What we need from you
- Your IdP metadata URL
- The published SAML metadata endpoint for your identity provider. One URL — we read your entity ID, sign-in endpoint, and signing certificates from it, and pick up certificate rotations automatically.
- Your email domains
- Which domains should route to SSO —
example.edu, and any others your staff use. Anyone signing in with an address at these domains goes to your IdP instead of receiving a code. While SSO is on, the dashboard only accepts a sign-in made through your identity provider; a code does not open it, and a session made with a code cannot read or change your organization's data.
What we give you
Once configured, we send you the three values your identity team needs to register Incredify as a service provider:
- SP Entity ID — how Incredify identifies itself to your IdP.
- ACS URL (Assertion Consumer Service) — where your IdP posts the assertion after authentication.
- SP metadata URL — all of the above as an XML document, if your IdP prefers to import rather than be configured by hand.
How it behaves once live
- 1A user goes to incredify.net/login and enters their institutional address.
- 2We recognize the domain as SSO-enrolled and redirect to your identity provider.
- 3They authenticate however your institution requires, including MFA.
- 4Your IdP posts the assertion back and they land in the dashboard.
SSO authenticates; it does not create accounts or memberships
An admin invites each member first under Settings → Members, which is what assigns the role and any sub-organization. Someone with an open invitation from your organization joins when they first sign in through your IdP; that sign-in accepts it. Signing in through your IdP does not create an account: someone who hasn't been invited is turned away. Just-in-time provisioning isn't supported today. See Settings, members, and roles.
Sign-in always starts from the Incredify login page. Starting from your identity provider's app portal (IdP-initiated sign-in) isn't supported. While SSO is on, every member of your organization must sign in through your IdP to use the dashboard, and is asked to sign in again after 12 hours (save your work before then). A member whose address is not at one of your enrolled domains cannot sign in while SSO is on.
Before SSO is switched on, check that every member's address is at an enrolled domain. An external partner with another address would be locked out; give them an address at your domain, or ask us to leave SSO off.
Related
Still stuck?
Email us at hello@incredify.net — a human will answer.