This post is also available in: Português
In this tutorial, you’ll learn how to manage multiple email signatures for Gmail email aliases using Bybrand’s Automation feature.
Why use email aliases with Automation?
Bybrand allows you to update email signatures for Gmail aliases individually, which works well if users only have a few aliases (e.g., 2 to 5).
However, when your organization has dozens of aliases per user, managing them one by one becomes impractical. For example, the main address “dylan.posse@company.com” might have several aliases:
- dy@company.com
- cmo@company.com
- dylan@company2.com
- dylan.posse@company2.com
In such cases, using Automation helps you manage email signatures more efficiently and in bulk, saving time and ensuring consistency.
Importing email aliases with Automation
Make sure your Bybrand account is integrated with Google Workspace.
We recommend importing aliases into a new Automation. You can do this by cloning an existing email signature, so both Automations use the same template.
How to import:
- Go to the import section of your Automation.
- Select the desired users.
- Check the box labeled Load all user email aliases into the Automation.
Example:

After importing, the aliases will appear as separate entries in the Automation list with a warning icon, indicating that they share the same data as the primary address—except for the email.

Updating email signatures for aliases
One of the main benefits of using email aliases in Automation is the ability to update all related signatures at once.
To perform a bulk update:
- Open the user list within the Automation.
- Click on the “Bulk Update” menu.
- Select the email addresses and their aliases.
- Click “Update selected.”

As a result, both the primary address and all aliases will have the same, up-to-date email signature.
Example:

To finish, click on the button Update to selected.
The result for the user on Gmail account. The primary email account and the alternate address have an identical email signature.

Creating different signatures for aliases
If you need each email alias to have its own unique signature, you’ll need to create and manage separate signatures for each one.
Limitations with alternate domains
Alias importing only works with email addresses under the same domain as the organization (e.g., alias@company.com). Aliases using alternate or secondary domains (like alias@company2.com) are not supported for import within Automation.