Single Sign On (SSO) configuration is an admin-only feature on upgraded accounts and you can only see the "Security" tab in organizations where you are an organization admin.
To avoid unauthorized logins, we have introduced an organizational level security setting "Configure SSO" to mandate employees to login via SSO. This "Configure SSO" setting will allow configuration at a domain level so an SSO type can be configured independently for each domain. Once SSO is configured for a domain, all employees associated with that particular email domain will:
1. be blocked from using username/password to log into Podio
2. need to mandatorily use only the configured SSO type to log into Podio on both web and mobile.
1. SSO Configuration can be done from the "Security" tab available alongside the Organization settings.
The "Security" tab is available only to organization admins for a paid organization and to all employee users for free organizations.
2. Setting up a domain is a pre-requisite for being able to configure SSO for the organization. If you do not have a domain added to your organization, please contact Support to add the domain(s).
Each domain needs to be configured with the SSO type that matches the identity provider configured for users on the domain. Example: One organization could have different domains across GEO location which might be following different SSO requirements.
3. Currently SSO Configuration is allowed for only 2 identity providers (IdP) that Podio already supports:
- Microsoft (Office 365)
Pro Tip: This could allow you to utilize an alternate IdP indirectly. For example, if your organization supports OKTA SSO and you sign in to O365 using OKTA, you will eventually be able to login to Podio using OKTA via O365. For this, you will need to Configure SSO with Office 365.
Note: Single Sign On (SSO) can be disabled from the Organization Security page by simply clicking the "Disable" button.
User login flow
Step 1: SSO check of email being used to login
- A user enters email with domain @abc.com for username password login.
- System will check if there are any SSO settings for domain @abc.com.
- If SSO setting found, the username password login will be denied
- If no setting found, then Step 2
Step 2: SSO check of all associated emails
- System will check if the user has any other email associated with this user id.
- If no other email found, then user will be allowed to login successfully with username password
- If associated email(s) are found, let's say, the other emails associated have domain @xyz.com and @def.com respectively. Now system will check if there are any SSO settings for either of these domain @xyz.com and @def.com
- If SSO setting found for any of the domains, the username password login will be denied
- If no setting found for either of the domains, then user will be allowed to login successfully with username password
If SSO has been enabled for at least one or more emails associated with the user, then for every case of denied login, an email notification will be sent out to the appropriate email ids associated with the configured SSO.
Advanced Information and FAQs:
Q: Are all members inside of my Podio organization required to use SSO login once this feature has been enabled?
A: Only employee members inside of your Podio organization will be required to use SSO login once this feature has been enabled. This feature will not be applicable to external members within your Podio organization.
Q: Even though my organization uses SSO login, would I still be required to use SSO login if my account is also a member of organizations that don't have this feature enabled?
A: Yes, you'll still be required to use the mandated SSO login linked to one of the organizations that have this feature enabled as Podio will give SSO priority to the higher security constraints.
Q: Can I login to Podio using one of my non Single Sign On (SSO) alternate account email addresses even though I'm an employee member of Single Sign On (SSO) Podio organization?
A: No, if you're an employee member of an organization that has Single Sign On (SSO) enabled, you'll receive an error while attempting to login using the non Single Sign On (SSO) alternate email address.
Error: "Sorry, Single Sign On (SSO) has been enabled by one of your organizations. Please sign-in using the appropriate SSO provider."