> ## Documentation Index
> Fetch the complete documentation index at: https://docs.emailux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Email signature management for Google Workspace

> How EmailUX Signatures designs one email signature, fills it from your Google Workspace or Workday directory, and publishes it to every Gmail mailbox.

**EmailUX Signatures** lets one person design a company email signature and publish it to every Gmail mailbox in a Google Workspace domain. Each person's name, title, phone and address come from your directory, so nobody edits a signature by hand.

## How it works

1. **Design** one signature in the same drag-and-drop editor used for emails, with merge fields where a name or phone number belongs.
2. **Connect** your Google Workspace directory, and optionally Workday, so EmailUX knows each person's details.
3. **Assign** signatures with rules, for example one design for Sales and another for everyone else.
4. **Publish.** EmailUX writes each person's rendered signature to their Gmail mailbox through the Gmail settings API.

EmailUX does not send or route your mail. Signatures are written into Gmail, and Gmail adds them to messages as usual.

## What you get

| Capability | Details |
| - | - |
| Visual editor | Twelve layouts, logo, banners and links, with a code preview. |
| Person fields | Sixteen built-in fields: name, first and last name, email, job title, department, employee ID, manager, location, phone, mobile and a full address. |
| Custom fields | Add your own for pronouns, certifications or a booking link. |
| Shared assets | Upload the logo and banners once. Every signature uses the same files. |
| Directory sources | Google Workspace and Workday, with a field order you control. |
| Assignment rules | Match on directory fields or groups. The first matching rule wins. |
| Queued sync | Changes go into a queue per mailbox. Unchanged signatures are skipped and failures show an error. |
| Team roles | Admin, Editor and Finance roles for the organization. |

## Step-by-step guides

> [card] [1. Create an organization](https://docs.emailux.com/signatures/create-organization.md)
>
> Set up your workspace and invite teammates.

> [card] [2. Design a signature](https://docs.emailux.com/signatures/design-a-signature.md)
>
> Build the layout and add merge fields.

> [card] [3. Connect Google Workspace](https://docs.emailux.com/signatures/connect-google-workspace.md)
>
> Authorize the directory and Gmail access.

> [card] [4. Add data sources](https://docs.emailux.com/signatures/data-sources.md)
>
> Map fields and set which source wins.

> [card] [5. Assign with rules](https://docs.emailux.com/signatures/assignment-rules.md)
>
> Give each team the right signature.

> [card] [6. Publish to Gmail](https://docs.emailux.com/signatures/publish-to-gmail.md)
>
> Sync signatures and fix failures.

## Frequently asked questions

> [accordion] Where are signatures published?
>
> To Gmail and Google Workspace. EmailUX writes each person's rendered signature to their mailbox through the Gmail settings API.

> [accordion] Where does the employee data come from?
>
> From your Google Workspace directory or Workday, mapped to the fields your signature uses. You choose which source wins when they overlap.

> [accordion] Will the signature look the same in every email client?
>
> The signature is generated as table-based HTML with inline styles, which mail clients handle most consistently. Test with the clients your recipients use before rolling it out.

> [accordion] Can different teams have different signatures?
>
> Yes. Assignment rules match on directory fields or groups, and the first matching rule decides which signature a person gets.

> [accordion] What happens when someone leaves or changes role?
>
> Update the directory and the next sync applies the new title or removes the person from a rule. You can also exclude people from publishing.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.