What are directory integrations?
A directory integration syncs people into Velory from your identity provider — the system that decides who can sign in — rather than from an HR system.
Connect one and the accounts in your directory become employees in Velory, with their directory groups alongside them.
In this guide
Supported directories
| Directory | Syncs | Connects with |
|---|---|---|
| Google Workspace | Users and groups, via the Admin Directory API | Google sign-in |
| Microsoft Entra ID | Users and groups, via Microsoft Graph | Microsoft sign-in |
Both need an admin account in that directory to grant access. Neither can be connected with an API key.
What a directory brings that an HR system does not
Real groups. This is the substantive difference. An HR system has no groups, so Velory derives one per department. A directory has actual groups and syncs them as they are, which is why a directory sync reports groups where an HR sync reports departments.
Groups matter because they usually describe access — who is in which team, which distribution list, which access group — and that is information an HR record does not carry.
Current sign-in state. A directory reflects who can log in right now. An HR system reflects who is employed, which is not always the same thing: a leaver may still have an active account, and a new hire may have an HR record weeks before an account.
What it does not do
- It does not sync devices. Google Workspace devices come from a separate integration, Google Workspace Endpoint Manager, under MDM. See How do I connect Google Workspace Endpoint Manager?.
- It does not carry employment data. Job title, cost centre, employee number, and start and end dates come from an HR system. A directory generally does not have them.
Setting one up
- How do I connect a directory integration?
- How does directory syncing work?
- How do I disconnect a directory integration?
For which of the two families to use, and what happens when you connect both, see What is the difference between HR and Directories?.
Good to know
Can I connect both Google Workspace and Microsoft Entra ID?
Yes. They are separate connections, each syncing its own users and groups.
Should I use a directory as my only employee source?
You can, and for a company without a formal HR system it is often the practical choice. Be aware of what you give up: no start or end dates, no job titles, and no record of a hire until their account exists.
Do the groups it syncs do anything in Velory?
They arrive as groups on the employee records, so you can use them the way you use any other group — filtering, and as conditions in workflows.
Does connecting a directory give employees single sign-on?
Connecting Google Workspace makes the directory available as an identity source, but how sign-in is configured for your company is a separate setting from this integration. Ask Velory support if you are not sure how yours is set up.
Was this article helpful?