Email signatures and company templates
Use a consistent signature with the correct person's details.
Create personal signatures, use company templates and choose account or identity-specific defaults for new messages and replies.
The right details below every message
Suggested details still need your review.
Brand consistency needs correct information, not copied fragments.
A signature identifies the person and company behind a message. Different addresses and roles can need different information. Tsumira supports personal signatures and designed signatures using company templates, with scope tied to accounts and sender identities. Decide which information belongs in each signature and who maintains the template, rather than distributing one copied HTML block that everybody edits independently.
Build the signature from reviewed profile information.
The signature generator can begin with member and company profile details such as name, title and phone. Review those values before using them in external mail. A designed signature is rendered from its template, styling and fields, with a plain-text representation alongside HTML. Profile suggestions make preparation easier but do not certify that contact details or required disclosures are complete.
- Designed HTML and plain text with reviewed profile fields
Match signatures to accounts and sending situations.
A signature can apply across accounts or be limited to a particular account and its sender identities. Choose suitable defaults for new messages and replies, including placement in the response. Review the applied signature when switching the sender. An account-management address and a person's direct address may need different details even when the same person operates both.
Keep the maintained company template
When a template is required, only signatures based on it can be offered and sent.
Maintain company rules through the template.
Administrators can manage company templates. Signatures based on a template are rendered using its current definition so a template change reaches their presentation. If a company enforces a template, only signatures based on that template are offered and allowed for sending. This supports a consistent configuration but does not replace legal review, recipient testing or checks in the email clients your customers use.
- Current company templates and optional enforcement
A concrete workflow
Review details
Confirm the person's name, role and contact information.
Choose scope
Select the accounts and identities that should use the signature.
Set defaults
Choose behavior for new mail and replies.
Test presentation
Check HTML, plain text and the applied signature before real use.
An illustrative working example
Illustrative scenario: one team, several customer addresses
A service business maintains a company template with reviewed contact details. One colleague uses a direct account and a shared service identity. The colleague creates the appropriate signature scopes and tests a new message and a reply from each sender. The administrator updates the template centrally. The team checks the current output rather than assuming old copied signatures have changed, and confirms which company rules are enforced at sending.
Questions about this topic
Can I use different signatures per sender?
Yes. Scope can be tied to accounts and sender identities, with suitable defaults for new mail and replies.
Do template changes reach existing template signatures?
Template-based signatures are rendered from the current template. Review the resulting presentation after changes.
Can the company require its template?
Yes. Enforcement restricts offered and sendable signatures to those based on the required template.
Does the generator guarantee legal compliance?
No. Review your required disclosures and actual details separately. A template is not legal advice or a compliance certification.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Gmail
Application concept: Check which maintained signature belongs to each Gmail identity for new messages and replies.
Outlook
Application concept: Compare an Outlook team's existing signature content with reviewed company-template fields and ownership.
Notion
Application concept: Use a maintained Notion brand guide to brief signature appearance without claiming automatic legal completeness.