1. Home
  2. Automation
  3. Employees
  4. Central employee registry

Central employee registry

This post is also available in: Português

The Employees section gathers all data for each employee into a single record, with the email address as a unique identifier.

This record serves as a central hub: from here, you can view the groups the employee belongs to and edit the placeholders used in email signatures.

All changes made there are automatically propagated to connected groups and integrations, avoiding rework and information discrepancies.

Benefits

  • Manage groups and edit placeholders centrally.
  • Maintain consistency across all connected integrations.
  • Detect and merge duplicates more easily.
  • Find users directly from the connected data source.

How it works

  1. You import employee lists from different sources, such as Google Workspace, Zoho Desk, Freshdesk, and others.
  2. During the import, Bybrand automatically attempts to merge duplicate records using email as a reference.
  3. This way, you can edit information at once and sync with all connected groups.

Deleting employees

Warning: Removing an employee is not neutral—it can impact integrations and email signature functionality.

External integrations (e.g., Google Workspace, Zoho CRM, etc.) that depend on this record may fail to sync because they can’t find the removed user.

Email signatures that were configured for that employee will no longer be generated or updated, potentially causing errors in automatic deployment or interruptions in sending.

Before deleting:

  • Review external dependencies: Check for integrations or automations that use this employee as a parameter.
  • Merge data: If this employee has a replacement, update the Merge to point to the new employee before deleting.

Re-adding a deleted employee

If an employee was accidentally deleted, you can add them back to the employee list as a new record.

Employees who came from an integration (such as Google Workspace, for example) must be re-added through the integration itself, not manually.

If the employee is manually recreated after being removed, they will not have internal links to the integration—which may prevent or limit the automatic application of the signature.

Whenever the employee is linked to an integration, use the integration’s own synchronization process to bring them back.

Updated on 20 de March de 2026
Was this article helpful?
Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support