Single Sign-on (SSO)
Last updated
Last updated
Parta.io supports Single Sign-On (SSO). If your Parta.io company is SSO-enabled, users can access the company through your corporate identity provider credentials, instead of Parta.io account credentials. This eliminates the normal login process and enables faster and secure access to your company.
Parta.io uses the most-commonly adopted SSO standard, i.e., Security Assertion Markup Language 2.0 (SAML 2.0). Consequently, our SSO implementation can be integrated with any well-known identity provider (IdP) that supports SAML 2.0 (such as Okta, OneLogin, Azure AD, Google G-Suite, Auth0). You can refer to our Set up SSO in Parta.io section to learn how you can integrate SSO with any IdP.
The SAML configuration in Parta.io allows you to leave logging in via SSO optional for everyone. This means that all users, except commenters, can log in either via SSO or via email and password.
If you have enabled required SSO login for your company, the company can only be accessed using the credentials of your IdP provider. To access the company, users must enter the Company ID on the login page. They will be redirected to your IdP, where they are required to authenticate themselves. However, if the users are already signed in to your IdP while signing into Parta.io via SSO, they will not be asked to log in again and will be redirected to the Company dashboard.
Access to the company via email and password will be blocked for all users. Exception: Company admins and owner will always have the option to bypass SAML SSO by using their email and password credentials. This is to allow them to access Parta.io in the event of SAML failure. They will be able to log in and disable or update their configuration.
Make sure that logging in via SSO works and is set up correctly before enabling "Required SSO" in your company.
To access the company via your IdP provider account, the user needs to be invited to the company on the Leenda platform in advance.
Currently, Parta.io does not support Just In Time provisioning, meaning that the user is not created in Parta.io upon first SSO login if the user does not exist.
