Single sign-on and MFA with Zoho Directory in short
Single sign-on and MFA with Zoho Directory means that staff sign in once to reach their Zoho apps, with a second check on top of the password. You also manage the rules for that sign-in from one admin panel. The order matters. Verify your domain and get your users in first.
Then set up single sign-on. Then switch on MFA for everyone, but only after your users have enrolled.
The reason for that order is simple. If you enforce MFA before people have set up their second factor, some staff cannot sign in. The same goes for an allowed IP list. If a list is switched on before you have added every office and home connection, sign-ins are refused.
The payoff comes when someone leaves. You disable that person once in Zoho Directory, and they lose access to the linked apps. You do not have to visit each app in turn.
This guide covers the following:
- the terms you need
- the order to follow
- a worked example with the actual settings
- a table of the four security policy components
- the lockout mistakes to avoid
- how leavers, Active Directory and your own apps fit in
Zoho Directory, single sign-on and MFA defined
Zoho Directory is Zoho's centralised identity and access management (IAM) service. IAM means one system decides who a user is and what they may open. Zoho Directory lets you manage users, groups and permissions for Zoho apps and third-party apps from one place, according to Zoho's admin guide to the Zoho Directory integration. It supports single sign-on, security policies and directory integrations such as Active Directory and LDAP.
Single sign-on (SSO) is one sign-in that gives a user secure access to several apps. SSO runs on standard protocols. The two you will meet are SAML and OIDC, which are agreed formats for one system to vouch for a user to another.
Multi-factor authentication (MFA) is a sign-in that asks for a second proof of identity on top of the password. In Zoho Directory, MFA is one part of the security policies.
Security policies are the rules that govern how users authenticate. Zoho lists four components: password policy, MFA, allowed IPs and session management. An allowed IP is a network address you permit sign-ins from. Zoho states that sign-in requests from IPs that are not allowed are denied.
The setup order: domain, users, single sign-on, then security policies
Follow a fixed order: verify the domain, bring users in, set up single sign-on, and enforce security policies last. Each step depends on the one before it. Skipping ahead is where lockouts start.
- Verify your domain. Zoho states that domain verification is mandatory to manage users added with domain-based email addresses, such as name@yourfirm.co.uk.
- Bring users and groups in. Add them by hand, or sync them from Active Directory with ZDSync if you already run one.
- Set up single sign-on. Confirm that staff can reach their Zoho apps with one sign-in before you add any restriction.
- Set the password policy. This gives everyone a known baseline.
- Enrol users in MFA, then enforce it. Enforce it for administrators first and for everyone else once enrolment is complete.
- Add allowed IPs and session rules last. Do this only when you know every network your staff sign in from.
This sequence keeps a working way in at every stage. If one step goes wrong, you still have users who can sign in and an administrator who can fix it. Changing policies in a different order gives you no such fallback.
Treat the order as a plan to agree before you open the admin panel. It is also worth telling staff the date when MFA becomes mandatory. A known date gets more people enrolled early than an unannounced switch does.
Worked example: switching on Zoho Directory from Zoho People
A firm already running Zoho People can reach every Zoho Directory option from one settings page. Take a small UK practice whose HR team uses Zoho People and whose staff also use other Zoho apps.
The administrator goes to Settings > Marketplace > Zoho in Zoho People and selects Configure in the Zoho Directory space. Zoho then shows four options:
- Single Sign-On, for one sign-in across apps
- Security Policies, for password policy, MFA, allowed IPs and session management
- Active Directory Sync, for bringing users across from an existing directory
- Sign-in Activity, for reviewing how people sign in
The practice works through them in the order from the previous section. It verifies its .co.uk domain, checks the staff list, and turns on single sign-on. Next it sets a password policy. It enrols the partners in MFA, then the rest of the team, and enforces MFA only when Sign-in Activity suggests everyone is through.
Two points from Zoho's guide help with budgeting. Zoho People runs without Zoho Directory, so you are not forced to adopt it. Zoho Directory's core features are included with Zoho People, but advanced features need paid Zoho Directory plans or add-ons. Check which features you need before you plan the rollout around them.
A firm with more than one Zoho People portal does not need several directories. Zoho states that you can manage several portals from the same Zoho Directory organisation.
The four security policy components and when to enforce each
Enforce the four security policy components one at a time, in order of lockout risk. Each component changes who can sign in, so each one can stop the wrong person. The table sets out what each component governs and when to switch it on.
| Component | What it governs | Lockout risk | When to enforce |
|---|---|---|---|
| Password policy | The rules a password must meet | Low, users can reset | First, once single sign-on works |
| MFA | A second proof of identity at sign-in | High if users have not enrolled | Admins first, everyone after enrolment |
| Allowed IPs | The networks sign-ins may come from; others are denied | High for remote and travelling staff | Last, after every network is listed |
| Session management | How sign-in sessions are handled | Moderate, depends on your settings | Alongside or after MFA |
The pattern is that the two components most likely to lock someone out are MFA and allowed IPs. Both depend on facts about your staff that the admin panel cannot know. These are whether each person has set up a second factor, and which networks each person uses.
Gather those facts before you enforce. A short message to staff asking them to enrol in MFA and confirm where they work does most of the job. Keep at least one administrator account outside any new IP restriction until you have tested it.
MFA lockouts: why enforcing before enrolment locks staff out
The most common MFA mistake is to enforce it before users have enrolled a second factor. Once MFA is required, a user without a second factor cannot complete sign-in. With single sign-on in place, that one failed sign-in blocks every linked app at once.
At Svennis we enrol the administrators first and confirm that every user has enrolled before we enforce MFA for the whole organisation. The lockouts we see at clients come from switching enforcement on first and telling staff afterwards.
A safe rollout follows the same order every time:
- Enforce MFA for two or more administrator accounts and test that they can sign in.
- Ask all staff to enrol and give them a deadline.
- Use Sign-in Activity to see who has signed in since the request went out.
- Chase the stragglers by name.
- Enforce MFA for everyone on the announced date.
Remote staff need the most help, because nobody can lean over their desk. A remote support tool such as Zoho Assist for secure remote support lets an administrator see the user's screen while they enrol. Plan that support before the deadline, not after the first locked-out call.
The same caution applies to allowed IPs. A sign-in from an address that is not on the list is denied. Someone working from home or a client's office will be refused until their network is added.
Removing a leaver's access in one place
When a member of staff leaves, disabling or deleting them in Zoho Directory removes their access to the linked apps automatically. Zoho's guide states that the change reflects automatically. Disabled or deleted users lose access to Zoho People and the other linked apps.
Without a central directory, offboarding is a list of separate tasks. Someone has to remember the CRM, the accounts package in Zoho Books, the team chat in Zoho Cliq, the dashboards in Zoho Analytics, and anything else the person used. Each app missed is an account that still works after the person has gone.
With Zoho Directory, the leaver process becomes one action in one place. That is a strong argument for setting up the directory early. Apps connected later inherit the same control, so you do not have to rebuild offboarding each time you add an app.
Agree who carries out the action and when. A sensible rule is that the account is disabled at the end of the last working day. Disabling rather than deleting keeps the user record for review. Write the step into your leaver checklist so it does not depend on one person remembering it.
Syncing users from Active Directory with ZDSync
If you already run Active Directory, Zoho Directory Sync (ZDSync) can bring your users across instead of you re-entering them. ZDSync is a directory and password synchronisation tool. It syncs users and their passwords in Active Directory with Zoho accounts.
The sync runs one way. Zoho states that ZDSync performs a one-way synchronisation from your existing LDAP server to the Zoho Directory Admin Panel. LDAP is the standard protocol that Active Directory and similar directories use to share user records.
One-way has a practical consequence. Your existing directory stays the master record. Changes you want to keep should be made there and allowed to flow into Zoho Directory. Edits made only on the Zoho side are not sent back to your server.
ZDSync fits the second step of the setup order, bringing users in. Run it after the domain is verified and before single sign-on is switched on. Then check the synced list before you enforce any security policy. A missing or duplicated user is far easier to fix before MFA is mandatory than after.
A firm without Active Directory can skip this step entirely and add users directly in Zoho Directory.
Connecting your own apps to Zoho Directory with SAML or OIDC
Zoho Directory can also act as the sign-in for applications your developers build, using SAML 2.0 or OIDC. LoginRadius, an identity software vendor, publishes a guide to implementing SSO with Zoho Directory in JavaScript that sets out the steps.
The setup has three parts, according to that guide:
- Create an application in Zoho Directory and configure the SAML or OIDC settings.
- Add the ACS URL, Entity ID and redirect URIs, then download the identity provider metadata.
- Map user claims such as email, name and groups from Zoho Directory to the application.
The same guide lists the common faults and their fixes:
- Login loop after redirect: check the callback URLs and cookie domain settings.
- 401 Unauthorized or invalid token: verify the client ID, issuer and audience.
- SAML certificate or signature error: update or re-upload certificates and reimport the metadata after rotation.
- Missing or incorrect user attributes: verify the attribute mappings on both sides.
Certificate rotation is the one to diarise. It recurs, and the fix is to reimport metadata.
What single sign-on and MFA with Zoho Directory mean for a UK firm
For a UK firm, the practical gains from Zoho Directory are one leaver process, one place for sign-in rules, and control over where staff sign in from. These matter most for small teams where the person managing IT also has another job.
Three local details shape the setup. First, your domain. Most UK firms use a .co.uk or .uk address, and Zoho requires domain verification before you manage users on domain-based email. Do it first, because nothing else in the directory works properly without it.
Second, hybrid working. Many UK teams split their week between office and home. An allowed IP list built only from the office network will deny every sign-in from a home connection. Either list each network or leave the IP rule until you are sure of them.
Third, staff turnover. Every leaver who keeps a working login is a risk to client data. Disabling the user in Zoho Directory removes their access to linked apps in one step. That makes the offboarding step easy to evidence.
The same thinking applies to apps that handle signed documents, such as Zoho Sign for electronic signatures. The sign-in in front of such an app deserves the same MFA as the rest of the suite.
Next steps for your Zoho Directory setup
Start with a short inventory, then follow the setup order without skipping steps. Most of the work is gathering facts about your staff before you change any setting.
- List every Zoho app your staff use and who uses each one.
- Confirm that you control your email domain and can verify it.
- Decide whether users come from Active Directory through ZDSync or are added directly.
- Check which Zoho Directory features your plan includes and which need a paid plan or add-on.
- Name two administrators and enforce MFA on their accounts first.
- Announce an MFA enrolment deadline to staff and track it in Sign-in Activity.
- Add allowed IPs only once you know every network your team uses.
- Write "disable in Zoho Directory" into your leaver checklist.
If you would rather have someone run this with you, read what a Zoho partner does and when to use one. It explains how a partner fits into a rollout like this one and what to expect from the work.


