Adding Users

A fresh EUnifyer organisation has exactly one person in it: the admin who created it. From there you have four ways to bring everyone else in.

The Users page at Admin → Users shows a picker on first visit. This page explains which path to pick.

Decision tree

It’s fine to combine paths. A common setup:

1. Federate sign-in to Entra so users log in with their existing Microsoft credentials.
2. Add SCIM on top so disabling a user in Entra disables them in EUnifyer within minutes.
3. Still invite contractors manually (they don’t exist in your IdP).

Path 1 — Invite individually

Admin → Users → Invite User.

Fill in the email (required) and optionally first/last name, department, job title, phone, employee ID. Pick a role (default: Member). Click Create.

The user gets an email with a set-password link. They click it, set their password, and land in EUnifyer. Until they accept, their row in the Users table is marked Pending Setup.

Resend the invitation from the row’s action menu if they didn’t get the email. Copy invitation link gets you a fresh link to hand over directly (e.g. in Slack).

Path 2 — Bulk import from CSV

Admin → Users → Bulk import.

Upload a CSV with one user per row. EUnifyer parses the file, shows you a preview of the first five rows, lets you pick a default role for rows without an explicit one, and on confirmation invites everyone in one pass. You get a per-row result table back so you can see who was invited, who was skipped as a duplicate, and any errors.

Full format reference: Bulk Import (CSV).

Good for: migrating from a spreadsheet export of your current HR system, or onboarding a department of dozens at once.

Path 3 — Federate to your IdP (SSO)

Admin → Identity → Single Sign-On.

Configure the connection to your identity provider (Entra ID, Google Workspace, Okta, ADFS, or any generic OIDC/SAML 2.0 IdP). Turn on Auto-create users on first SSO login.

From then on:

• Users sign in via your IdP — Microsoft/Google/Okta login screen, their existing password, their existing MFA.
• EUnifyer creates the user row automatically on first sign-in.
• They never have a separate EUnifyer password.

Full step-by-step for the most common IdPs:

• Microsoft Entra ID
• Federating Other Providers

Good for: any organisation that already has an identity provider. Users sign in once with credentials they already know.

Path 4 — SCIM provisioning

Admin → Identity → SCIM provisioning.

SSO covers sign-in (users land in EUnifyer the first time they sign in). SCIM covers the roster: your IdP pushes user lifecycle changes to EUnifyer continuously.

• New hire appears in your IdP at 09:00 → exists in EUnifyer by 09:01.
• Offboarded at 17:00 → disabled in EUnifyer within minutes.
• Department or role changes propagate immediately.

You generate a bearer token in EUnifyer, paste it into your IdP’s provisioning configuration with the SCIM endpoint URL, and assign users on the IdP side.

Full setup guide: SCIM 2.0 provisioning.

Good for: enterprises with strict on-/off-boarding SLAs, or any team that wants the IdP to be the single source of truth.

Day-to-day management

Once users are in:

• Edit (row action menu) — name, department, title, role, phone, employee ID. The dialog also shows last sign-in, last activity, and an effective-permissions preview.
• Activate / Deactivate — flip is_active. Deactivated users keep their data but can’t sign in. Reactivating is one click from the same menu.
• Resend invitation — for pending users whose set-password email got lost.
• Force sign-out — kicks the user out of all active sessions immediately. Use during incident response or rapid offboarding.
• Delete — permanent. Removes the user from every service (identity, drive, mail, chat). GDPR-cascade safe.

What the row’s status badges mean

Adjacent topics

• Bulk Import (CSV) — full CSV format reference.
• Microsoft Entra ID setup — federation walkthrough.
• SCIM provisioning — automatic roster sync.
• Identity overview — what EUnifyer’s built-in identity layer can do.