Unifize supports Single Sign-On (SSO), allowing you to log in with your existing company credentials β such as those you use for Microsoft 365, Google Workspace, or another identity provider. This feature replaces the need for a separate Unifize password and allows seamless access to the platform.
If your organisation has SSO enabled, you will be automatically routed through your companyβs login page after entering your work email address. If your organisation has configured more than one SSO connection, Unifize will detect your email domain and route you to the correct login portal automatically. This applies to both the web platform and the mobile app.
SSO enhances the login experience by integrating with your organisationβs existing authentication system. Hereβs why it matters:
Secure by default: Your credentials never pass through Unifize. Authentication is handled directly by your companyβs identity provider.
Simplifies access: No need to create or remember a separate password for Unifize.
IT-aligned: Helps organisations manage access centrally using existing systems like Azure AD or Google Workspace.
Supports MFA (Multi-Factor Authentication): If your company uses 2FA, SSO supports that too β providing added security.
You can use SSO to log into Unifize if:
Your organisation has enabled SSO in their Org Settings
Your email domain (e.g., @yourcompany.com) has been configured for SSO
You have been added as a user in your companyβs identity provider system (e.g., Azure AD)
If youβre not sure whether your company uses SSO, ask your IT administrator or Unifize workspace admin.
Open your browser and go to https://app.unifize.com
Enter your work email address
Unifize checks if your domain is SSO-enabled:
If yes, you are redirected to your companyβs login portal
Open the Unifize app on your phone or tablet
Enter your work email address
Youβll be redirected to your companyβs login page within the app
Complete your usual login flow and MFA (if applicable)
In Unifize, some workflows require digital signature confirmation during approvals.
Because your password is managed outside Unifize when using SSO, you canβt re-enter a password to validate signatures. Instead:
Youβll receive a One-Time Passcode (OTP) to your registered email
The OTP is valid for 2 minutes
Enter the 6-digit code to confirm your signature
This ensures your approvals remain secure and traceable even when using SSO.
If no, youβll see the traditional password field (for standard users)
Log in using your corporate credentials (email + password)
Complete any required MFA (multi-factor authentication) steps
Youβll be logged into Unifize and redirected to your workspace
Once authenticated, youβll return to the app β logged in and ready to go
βΉοΈ Even if itβs your first time using Unifize, you donβt need to create a new password β SSO will handle the login.
βΉοΈ Mobile login flow is nearly identical to the web experience, adapted for mobile screens.
Issue
What to Try
Not redirected to your company login
Make sure your email domain is registered for SSO. Ask your admin to confirm the domain is configured in Org Settings β SSO.
See password field instead of SSO login
Clear browser cache and retry, or confirm with your admin that your domain is mapped to an SSO tenant.
Didnβt receive OTP
Check your spam/junk folder, or request a resend. Confirm your email in Unifize matches your work email exactly.
Login loop or error from IdP
Make sure your browser or app allows third-party cookies/redirects.
Mobile login stalls after IdP redirect
Force-close and reopen the Unifize app, and update to the latest version.
Redirected to the wrong company login page
Your email domain may be mapped to the wrong SSO tenant. Contact your admin to review domain assignments in Org Settings β SSO.
Feature ID: FU-1051
Document Version: 3.0
Date: 24-03-2026
Unifize supports Single Sign-On (SSO) integration using the SAML 2.0 protocol. This allows users to authenticate with existing identity providers (IdPs) such as Microsoft Entra ID (formerly Azure AD), Google Workspace, or other SAML-compatible systems.
It has full SSO support on desktop and mobile browser. Approvals are done via OTP-based digital signature. The authentication method is admin-configured per org. Users do not get to choose between SSO or password-based login.
User navigates to their Unifize portal
Enters your email address
If the domain has SSO configured:
User is redirected to the corresponding IdP login
Completes password entry and 2FA if required
Redirects to Unifize as logged in user
Note: The login screen may still display the "Sign Up Now!" prompt. However, SSO-configured domains will bypass this once the email is validated.
User opens the Unifize mobile app
Enters your email address
If SSO is configured for the domain:
User is redirected to the corresponding IdP login
Open
Enter your email address
If your domain is SSO-enabled you'll be redirected to the same enterprise IdP login as the Web App.
After authentication, redirected back to PWA.The PWA supports full SSO-based login and authorization flow identical to the Web App.
SSO users can do 2FA for authorising their digital signature using email-based OTP flow:
Upon initiating a digital signature, the user receives a 6-digit OTP at their registered email
The OTP is valid for 2 minutes
Once entered, the βConfirm and Signβ button becomes active
Note: Only org admin can set up SSO configuration. Please reach out to your admin for the following steps:
Configure Azure Entra Id following the .
In Azure, configure the following using values from Unifize (Org Settings β SSO):
Entity ID : Service Provider Entity ID from Unifize
Reply URL(s):
Go to Users and Groups in the created Enterprise Application
Add relevant users to grant them access to Unifize
Ensure the users' email domains match the configured domain
Only Org Admins can access and configure SSO settings
Users are automatically routed to SSO based on their email domain
For SSO access, users must:
Be added to the Unifize app group in the IdP
Completes password entry and 2FA if required
Redirects to Unifize mobile app as logged in user
Add additional Reply URL for PWA: https://pwa.unifize.com/__/auth/handler
Sign-on URL : Org SSO URL from Unifize
Configure Unifize SSO Settings Go to Org Settings β SSO in Unifize
Choose Domain from the drop down. In case the domain is not listed, please reach out to your Unifize account manager.
Fill the following values from Azure to unifize
Entity ID : Microsoft Entra Identifier on Azure
SSO URL : Login URL on Azure
Certificate :
Download the "Base64 certificate" from Azure.
Copy paste the content of the file in the text area on Unifize.
Have an email address matching the configured domain


This guide walks Unifize workspace admins through setting up Single Sign-On (SSO) using SAML 2.0. When SSO is enabled, users in your org are authenticated through your company's identity provider (IdP)βsuch as Microsoft Entra ID, Okta, or Google Workspaceβrather than with a Unifize password.
You can configure one or more SSO tenants under a single org. This is useful when your users are spread across multiple IdP tenants (for example, separate Microsoft Entra ID directories for different subsidiaries). Each tenant is mapped to specific email domains, so users are always routed to the right login portal.
Make sure you have the following ready before opening the SSO configuration page:
Access to your IdP admin console (e.g., Microsoft Entra ID, Okta, Google Workspace)
The email domain(s) you want to route through SSO (e.g., yourcompany.com)
Permission to create an enterprise application in your IdP
Unifize workspace admin role
Log in to Unifize as a workspace admin.
Navigate to Org Settings β SSO.
Click Add Tenant to begin configuring your first (or additional) SSO tenant.
Before filling in your IdP details, copy the following values from the Unifize SSO configuration panel. You will need to enter these into your IdP's enterprise application setup.
In your identity provider's admin console, create or open the enterprise application you will use for Unifize SSO, and enter the Unifize values from Step 2. The specific steps vary by IdP:
Go to Microsoft Entra ID β Enterprise applications β New application.
Select Create your own application and choose Integrate any other application you don't find in the gallery.
Under Single sign-on, choose SAML.
In Basic SAML Configuration, enter:
Identifier (Entity ID): paste the Identifier value from Unifize
Reply URL (ACS URL): paste the Reply URL from Unifize
Sign on URL: paste the Sign on URL from Unifize
Save the configuration.
Download the Certificate (Base64) from the SAML Signing Certificate section.
Copy the Microsoft Entra Identifier (Entity ID) and Login URL from the Set up section.
Go to Applications β Create App Integration β SAML 2.0.
In the SAML Settings step, enter:
Single sign-on URL: paste the Reply URL from Unifize
Audience URI (SP Entity ID): paste the Identifier from Unifize
Complete setup and go to the Sign On tab.
Download the Signing Certificate and copy the Identity Provider Entity ID and Login URL.
Go to Admin Console β Apps β Web and mobile apps β Add app β Add custom SAML app.
Copy the SSO URL and Certificate from the Google IdP details pageβyou will need these in Step 4.
In the Service Provider Details step, enter:
ACS URL: paste the Reply URL from Unifize
Entity ID: paste the Identifier from Unifize
Complete setup.
Return to the Unifize SSO configuration page and fill in the tenant fields with the values from your IdP:
Click Save in the Unifize SSO configuration panel.
Open a new private/incognito browser window.
Go to https://app.unifize.com and enter an email address that belongs to the domain you configured.
You should be redirected to your IdP's login page.
If your organization uses more than one identity provider tenant (for example, separate Entra ID directories for different business units), you can add multiple tenants to a single Unifize org.
In Org Settings β SSO, click Add Tenant.
Repeat Steps 2β5 for each additional tenant, using the credentials and domain(s) for that tenant.
Each tenant will have its own Domain, Microsoft Entra Identifier, Login URL, and Certificate.
This table describes every field in the SSO tenant configuration panel and what is expected in each.
The SSO configuration page labels were updated to match Microsoft Entra ID's SAML setup terminology. If you configured SSO previously, use this table to find the fields you are familiar with.
Understanding the flow helps you diagnose issues and configure your IdP correctly.
User enters their work email on the Unifize login screen.
Unifize checks the email domain against all configured SSO tenants for your org.
If a matching tenant is found, the user is redirected to that tenant's Login URL.
The IdP authenticates the user (with MFA if your IdP policy requires it).
If a user's email address is updated in Unifize and their new domain belongs to a different SSO tenant, Unifize will automatically migrate them to the correct tenant.
Practically, this means:
Updating a user's email in Unifize will re-evaluate which tenant they belong to.
If their new domain maps to a different tenant, their account is migrated to that tenant automatically.
No manual re-configuration is needed after an email domain change.
Log in with your corporate credentials and confirm you land back in Unifize.
The IdP sends a SAML assertion back to Unifize's Reply URL (ACS URL).
Unifize validates the assertion using the Certificate (Base64) you provided.
The user is logged in and redirected to their workspace.
Field in Unifize
Where to use it in your IdP
Example value
Identifier (Entity ID)
Application Entity ID / Audience URI
unifize-866-saml
Reply URL (Assertion Consumer Service URL)
ACS URL / Reply URL
Field in Unifize
What to enter
Where to find it in your IdP
Domain
The email domain for this tenant (e.g., yourcompany.com). Users with this domain will be routed to this tenant's IdP.
Your org's email domain β not from the IdP
Microsoft Entra Identifier
The Entity ID of your IdP application
Field
Description
Required
Domain
The email domain mapped to this tenant. Users with this domain are forced through SSO. Example: yourcompany.com
Yes β per tenant
Microsoft Entra Identifier
Previous Label
Current Label
Service Provider Entity ID
Reply URL (Assertion Consumer Service URL)
Org SSO URL
Sign on URL
Entity ID
Symptom
Likely Cause
What to Check
User not redirected to IdP β sees password field instead
Email domain not mapped to any SSO tenant
Confirm the domain is entered correctly in the tenant's Domain field in Org Settings β SSO
SAML error / assertion validation failure
https://app.unifize.com/__/auth/handler
Sign on URL
Sign-on URL / Login initiation URL
https://app.unifize.com/sso-redirect?slug=<your-org-slug>
Entra: 'Microsoft Entra Identifier' in the Set up section
Login URL
The IdP's SAML login endpoint
Entra: 'Login URL' in the Set up section
Certificate (Base64)
The SAML signing certificate from your IdP. Must begin with -----BEGIN CERTIFICATE----- and end with -----END CERTIFICATE-----
Downloaded from IdP in Step 3
The Entity ID from your IdP. Identifies the IdP application to Unifize. Also called 'Identity Provider Entity ID' in Okta and 'Entity ID' in Google Workspace.
Yes
Login URL
The SAML login endpoint of your IdP. Unifize redirects users to this URL to begin authentication.
Yes
Certificate (Base64)
The X.509 signing certificate from your IdP, in Base64 format. Used to verify the SAML response. Must start with -----BEGIN CERTIFICATE----- and end with -----END CERTIFICATE-----
Yes
Identifier (Entity ID)
Read-only. Unifize's own SAML Entity ID. Copy this into your IdP's enterprise application configuration.
Provided by Unifize
Reply URL (ACS URL)
Read-only. The Assertion Consumer Service URL where your IdP sends the SAML response. Copy this into your IdP.
Provided by Unifize
Sign on URL
Read-only. A direct login link that triggers SSO for your org. Unique to the org; defaults to the first configured tenant. For tenant-specific links, append &domain=<domain>.
Provided by Unifize
Microsoft Entra Identifier
SSO URL
Login URL
Certificate
Certificate (Base64)
Certificate mismatch or expired certificate
Re-download the Base64 certificate from your IdP and update it in Unifize
Login loop β user keeps being redirected
ACS URL or Identifier mismatch between IdP and Unifize
Verify the Reply URL and Identifier in your IdP match exactly what Unifize shows
User redirected to wrong tenant's login
Email domain mapped to the wrong tenant
Review domain assignments across all configured tenants in Org Settings β SSO
Sign on URL routes to wrong tenant
URL defaults to first tenant when multiple are configured
Use the domain-scoped URL format: /sso-redirect?slug=<nick-name>&domain=<domain>
User cannot complete digital signature
OTP not delivered β email mismatch or spam filter
Verify the user's email in Unifize matches their IdP email; check spam/junk folder
Mobile login stalls after IdP redirect
Outdated app version or redirect handling issue
Ask the user to force-close and reopen the Unifize app, and update to the latest version