Front Signatures Explained (Personal, Team & Dynamic)

Personal vs shared signatures: the two layers

Front splits signatures into two settings areas, and knowing which one you're in explains most of the confusion. A personal signature is yours: you create it in your own settings and it follows you across the channels you can access. A shared (team) signature is created at the workspace level by an admin so an entire support or sales channel sends a consistent block — the same disclaimer, the same brand formatting — without every teammate rebuilding it.

The practical rule to remember is precedence. Per Front's Create or edit shared signatures documentation, only company admins or teammates with workspace permissions can create shared signatures, while anyone can create personal ones. And if your personal signature is visible on a shared channel, your personal signature takes precedence over the shared one on that channel. That's a feature — it lets an individual sign with their own name over a team default — but it also means a shared signature is a default, not a lock. Front is explicit that it's not possible to enforce a company-wide signature that teammates can't change.

The four fields in the signature editor

Whether you're building a personal or shared signature, the editor exposes the same handful of fields. Per Front's Create or edit individual signatures guide, you'll set:

• Name — an internal label only. It never appears on the recipient's end; it's just how you find the signature in your list. Name them by purpose ("Support — EU," "Sales outbound") so future-you can tell them apart.
• Sender info — the public-facing display name recipients see in the email header (the "From" name). This is linked to the signature, which matters more than it looks, as you'll see with per-channel defaults below.
• Channel access — which channels are allowed to use this signature. This dropdown is how you scope a signature to one inbox instead of all of them.
• Signature body — the rich-text (or HTML) block itself: your closing, name, title, links, logo, and any legal footer.

To reach these: click the gear icon, go to Personal settings for your own signatures or workspace settings for shared ones, then select Signatures from the left menu and click Create signature.

Dynamic fields: one signature, everyone's name

The reason a shared signature is usable at all is variables. Without them, a team signature would have to hard-code one person's name — useless the moment a second teammate replies. Front's variables solve this by resolving placeholder text against the sender or recipient at send time.

The ones you'll actually use in signatures come from the current-user object. Per Front's Using variables and application objects reference, the key ones are:

• {{user.name}} — the sending teammate's full name
• {{user.first_name}} and {{user.last_name}} — the parts
• {{user.email}} — their email address
• {{user.custom.[field_name]}} — a custom teammate field, e.g. {{user.custom.job_title}} or a phone extension

So an admin can build one shared signature body — Best,\n{{user.name}}\n{{user.custom.title}} · Acme Support — and every teammate who sends from that channel gets their own name and title rendered automatically. You can also personalize the greeting toward the recipient with {{recipient.first_name}}, and guard against blanks using Front's fallback syntax: {{recipient.first_name | 'there'}} renders "there" when no first name exists.

One honest caveat worth designing around: user variables stay blank in automatic replies, because an auto-reply has no tied teammate to resolve {{user.name}} against. If you're building a signature for an automated out-of-office or rule-driven send, don't rely on {{user.*}} — hard-code the team name instead.

Per-channel default signatures

If you manage several email addresses in Front — support@, sales@, billing@ — you rarely want the same signature and display name on all of them. Front lets you set a different default signature per channel, and it's driven by that Channel access field. Per Front's How to set a default signature for a channel guide:

1. Click the gear icon, then go to Personal settings (or workspace settings for a shared signature).
2. Select Signatures from the left menu and open the signature you want to make default.
3. Open the dropdown under Channel access and use the checkboxes to pick the channels this signature applies to.
4. Save.

Because Sender info is linked to the signature, this also sets a different display name per channel — replies from sales@ can go out as "Alex at Acme" while support@ replies go out as "Acme Support." When you compose or reply from a channel, its default signature populates automatically. And remember the precedence rule: if your personal signature is visible on a channel that also has a shared signature, your personal one wins.

HTML tips that don't break in the wild

Front signatures support an HTML mode, which is where teams add logos, buttons, and brand fonts. A few things keep them from rendering as a mangled mess in the recipient's client:

• Use inline styles, not <style> blocks or classes. Email clients (especially Outlook) routinely strip <head> and external CSS. Put styling directly on the element: <span style="color:#7C3AED">.
• Lay out with tables, not flexbox or grid. For a logo-beside-text block, a simple <table> is still the most portable layout primitive in email.
• Host images at a stable public URL. Reference logos as <img src="https://..."> rather than pasting them, so they don't balloon message size or vanish.
• Keep dynamic variables intact in HTML mode. {{user.name}} works inside HTML too — just make sure the toggle didn't wrap your braces in stray tags.
• Test by sending to yourself in Gmail, Outlook, and Apple Mail. What looks perfect in Front's editor can shift in a real client.

The honest limits — where Front's signatures stop

Front's signature system is well-designed for what it's for: consistent, per-channel, variable-driven closing blocks on a shared inbox. But it's worth being clear-eyed about the edges.

It's email-only. Front is clear that signatures apply only to email channels — chat, SMS, Instagram, and other channels don't use them. If your team works those channels, the signature story simply doesn't extend there.

You can't hard-enforce a signature. As covered above, a shared signature is a default, not a policy. A teammate can edit or delete it on any given message, and their personal signature overrides it on a shared channel. For legal disclaimers that must appear, that's a real gap Front doesn't close natively.

A signature is presentation, not content. This is the deeper limit and it's not really a knock on Front — a signature makes the reply look right; it does nothing to produce the reply itself. The {{user.name}} variable resolves who's signing, but the paragraph above it — the actual answer to "where's my order?" — is still 100% human work, and on a busy shared inbox that's where the time goes.

That last gap is exactly where an AI agent layer fits, and it's the honest reason to reach for one — not to replace Front, but to speed up the part signatures can't touch. The broader category of AI agents for customer service exists to do the reasoning-heavy drafting an inbox tool leaves to people. Macha is one such layer: it runs on top of the Front you already use through a live native connector — it does not replace Front, your shared inbox, or your signatures. It reads and drafts against the same conversations, proposing grounded replies for a teammate to review and send, so the answer above your carefully-formatted signature is ready sooner. It can even look up order or account status through a custom tool that turns an internal API into something the agent can call, and you can route which conversations it touches with the same rules logic you already use for signatures. (Credits are consumed per AI action, not per resolution — see the pricing breakdown, and the Macha–Front integration page for how the connector works.)

The clean division of labour: let Front own the signature — the branded, per-channel, variable-driven block that makes every send look consistent — and layer an agent on top for the reply itself.

FAQ

Where do I set up signatures in Front? Click the gear icon, then go to Personal settings for your own signatures or workspace settings for shared ones, select Signatures from the left menu, and click Create signature. Each signature has a Name (internal only), Sender info (the public display name), Channel access, and a rich-text or HTML body.

What's the difference between a personal and a shared signature? A personal signature is yours and follows you across your channels; a shared (team) signature is created by an admin at the workspace level so a whole channel sends a consistent block. Only admins or teammates with workspace permissions can create shared signatures, and a personal signature takes precedence over a shared one on the same channel.

How do dynamic signature variables work? Variables like {{user.name}}, {{user.first_name}}, and {{user.custom.[field]}} resolve to the sending teammate's details at send time, so one shared signature renders correctly for everyone. You can also use {{recipient.first_name}} with a fallback like {{recipient.first_name | 'there'}}. Note that {{user.*}} variables stay blank in automatic replies since there's no tied teammate.

Can I use a different signature for each inbox? Yes. Open a signature, use the Channel access checkboxes to scope it to specific channels, and save — it becomes the default for those channels. Because Sender info is linked to the signature, this also sets a different display name per channel.

Do Front signatures work on chat or SMS? No. Front signatures apply only to email channels. Chat, SMS, Instagram, and other channels don't use them.

Ready to make the reply above your signature as polished as the signature itself? Start a free trial of Macha and connect it to your Front in minutes.