Variables and directory data
Fill each signature with the right name, title, phone and more from Microsoft 365.
Signatures use variables, written like {{user.displayName}}. When LlamaSig builds a signature for a person it replaces each variable with that person's value.
Built-in variables
| Variable | Value |
|---|---|
{{user.displayName}} | Display name |
{{user.jobTitle}} | Job title |
{{user.email}} | Email address |
{{user.phone}} | Business phone |
{{user.bookingUrl}} | A booking link, if you map one |
{{company.name}} | Company name (a fixed value you set) |
{{sender.email}} | The address the message is actually sent from, useful for people with aliases |
Your own variables
On the Variables page you can add variables, choose which directory field fills each one, and set a fallback used when a person has no value. A source can be a standard Microsoft Graph user field or a nested path such as onPremisesExtensionAttributes.extensionAttribute10, which is a common place to keep a booking link or a licence number. Other kinds of custom directory data (open extensions, schema extensions) are not read.
Per-person overrides
On the Users page you can override any variable for one person. Overrides are kept when you synchronize again.
Hide empty lines
Each element in the designer can be set to show only when a field has a value, so a missing phone number does not leave an empty line.
Synchronizing
- Select Sync now on the Users page (or Synchronize users on the Microsoft 365 page) whenever your directory changes. Synchronization runs when you ask for it; it is not automatic.
- After synchronizing, publish again to apply changes to Exchange.
- New users start excluded from publishing. Include them individually, or turn on Include new active directory users in publishing on the Users page, which includes newly synchronized, enabled accounts. Disabled accounts stay excluded.
- Your inclusion choices and overrides are preserved across synchronizations.
- LlamaSig reads each person's SMTP aliases at synchronization. Synchronize before publishing if you add or change aliases.