Single Sign-On (SSO) allows your team members to sign in to Formo using your organization’s identity provider. This provides centralized access management, enhanced security, and a seamless sign-in experience.
SSO is available on Enterprise plans.
Contact us to enable SSO for your organization.
Supported providers
Formo supports SAML 2.0 SSO with the following identity providers:
- Google Workspace (formerly G Suite)
- Azure Active Directory
- Okta
How SSO works
When SSO is enabled for your organization:
- Team members visit the Formo sign-in page
- They enter their work email address
- Formo detects the SSO-enabled domain and redirects to your identity provider
- Users authenticate with your identity provider
- Upon successful authentication, users are redirected back to Formo
Setting up SSO
SSO configuration is handled by the Formo team. Here’s what you’ll need to provide:
Reach out to [email protected] or your account manager to request SSO setup.
Step 2: Create a SAML application
In your identity provider (e.g., Okta), create a new SAML 2.0 application with the following settings:
| Setting | Value |
|---|
| Single sign-on URL (ACS URL) | Provided by Formo |
| Audience URI (SP Entity ID) | Provided by Formo |
| Name ID format | EmailAddress |
| Application username | Email |
| SAML Attribute | Value |
|---|
email | User’s email address |
firstName (optional) | User’s first name |
lastName (optional) | User’s last name |
- Metadata URL - Your identity provider’s SAML metadata URL
- Email domains - The email domains to enable for SSO (e.g.,
yourcompany.com)
Step 5: Test and verify
Once configured, Formo will confirm the setup is complete. Test the SSO flow by:
- Signing out of Formo
- Going to app.formo.so
- Entering an email with your SSO-enabled domain
- Verifying you’re redirected to your identity provider
- Authenticating and being redirected back to Formo
Okta setup guide
Here’s a detailed guide for setting up SSO with Okta:
1. Create a new application
- In the Okta Admin Console, go to Applications > Applications
- Click Create App Integration
- Select SAML 2.0 and click Next
- Enter an App name (e.g., “Formo”)
- Optionally upload the Formo logo
- Click Next
Enter the values provided by Formo:
| Field | Value |
|---|
| Single sign on URL | https://[provided].supabase.co/auth/v1/sso/saml/acs |
| Audience URI (SP Entity ID) | https://[provided].supabase.co/auth/v1/sso/saml/metadata |
| Name ID format | EmailAddress |
| Application username | Email |
| Update application username on | Create and update |
- After creating the application, go to the Sign On tab
- Copy the Metadata URL
- Send this URL to Formo along with your email domain(s)
5. Assign users
- Go to the Assignments tab
- Assign the application to users or groups who should have access to Formo
Enforcing SSO
Once SSO is configured, you can optionally enforce SSO for all users on your domain. When enforced:
- Users with matching email domains must authenticate via SSO
- Password-based sign-in is disabled for those users
- New team members are automatically required to use SSO
Before enforcing SSO, ensure all team members can successfully authenticate through your identity provider.
Managing users
Adding users
When SSO is enabled:
- Add users to your SAML application in your identity provider
- Users can then sign in to Formo using SSO
- New users are automatically provisioned on first sign-in
Removing users
To remove a user’s access:
- Remove them from the SAML application in your identity provider
- Optionally, remove them from the Formo team in Team Settings > Members
Troubleshooting
User can’t sign in via SSO
- Verify the user is assigned to the SAML application in your identity provider
- Check that the user’s email domain matches the configured SSO domain
- Ensure the Name ID format is set to “EmailAddress”
SSO redirect not working
- Verify the Single sign-on URL (ACS URL) is correct
- Check that the Audience URI matches exactly
- Ensure there are no trailing slashes or whitespace in the URLs
Need help?
Contact [email protected] for assistance with SSO configuration.
Security benefits
SSO provides several security advantages:
- Centralized access control - Manage all user access from your identity provider
- Automatic deprovisioning - Remove access instantly when employees leave
- Stronger authentication - Leverage your organization’s MFA policies
- Audit trail - Track authentication events in your identity provider logs
- Reduced password fatigue - Users don’t need another password to remember
Next steps
