If your company is changing employee email addresses (new email domain, rebrand, acquisition, etc.), two parts of Blissbook are affected: your employee sync and, if enabled, single sign-on (SSO). The steps depend on how your employee list syncs into Blissbook and how your SSO is configured.

How Blissbook handles the transition depends on your sync method.

No action needed on your part. Blissbook uses a unique ID from your HRIS platform to track each employee, so when email addresses change, records update automatically on the next sync.

Blissbook needs a way to match each employee before and after the email change. Add a unique Employee ID column to your sync file if you don't already have one.

If Employee ID isn't in your file today:

Once Employee ID is in place, Blissbook can match employees by that ID instead of email address, and the email address change will flow through cleanly.

Same as SFTP (see above): you need Employee ID in your people list so Blissbook can track employees through the transition.

A quick way to get started: export the current employee list from the People page (click the Add, Import or Export button in the top right corner, then choose "Export Employees"), add the Employee ID column, then re-upload. Or generate a fresh file from your HRIS, AD, or payroll system with Employee ID included.

If you have SSO enabled, your SSO configuration determines whether the email change needs coordination.

This applies if your Unique Employee Identifier is set to Email Address or None, or if you use Google Workspace or Microsoft 365 / Azure SSO.

The email address employees use to log in through SSO must match the email address on file in Blissbook. Coordinate the timing: update your employee list in Blissbook at the same time (or just before) you change emails in your identity provider. If the emails are out of sync, employees won't be able to log in. See email mismatch preventing login for troubleshooting if this happens.

Note: For HRIS-synced customers, Blissbook picks up the new email address on the next sync cycle. Make sure the sync runs before employees try to log in with their new email, our reach out to our support team and ask us to trigger your sync when you're ready.

This applies if you use Okta or SAML 2.0 SSO and your Unique Employee Identifier is set to Employee ID or Employee SSO Identifier.

No timing coordination needed. Blissbook validates users based on their Employee ID or SSO Identifier, not their email address. The email change happens independently on the next sync and doesn't affect login.

If you're currently using email as your identifier and want to switch to Employee ID or Employee SSO Identifier to avoid the timing issue, go to your SSO settings and change the Unique Employee Identifier field. See the Custom SSO ID section of the SSO setup article for details to ensure it's set up right (you'll have to sync an "SSO Identifier" custom field with us).

If you're also migrating your employee sync source, see the companion article on migrating your employee sync. Doing both at once is possible but adds complexity, so handle them in sequence when you can: get the new sync source working first, then change emails (or vice versa).