The first test email I built from a template in our Developer org had no signature at all. I’d saved a four-line sign-off in My Email Settings ten minutes earlier, and it sat right there in the composer. Then I clicked the template button and Salesforce said: “Inserting this template will overwrite the current email.” It did. The signature went with everything else.
These are the notes we kept while setting up a Salesforce email signature in Lightning. You’ll get the exact clicks, what the plain signature box can and can’t hold, how to keep a sign-off inside templates, where legal disclaimers belong, and which emails never pick up your signature.
Set the signature once in My Email Settings
The signature lives in your personal settings, not in Setup, so every user sets their own. Here is the path we used in Lightning Experience:
- Click your avatar (top right), then Settings.
- In the left panel, open Email and click My Email Settings.
- Under Signature, type your sign-off in the Email Signature box.
- Under Composer, keep Salesforce Email Composer selected so emails are sent and logged from Salesforce.
- Click Save. You should see “Your settings have been successfully saved.”
The box says “1333 characters max”, which is plenty for four lines and not enoug