User properties describe your own agents. To declare the customer data your
app sends, use Context Variables
instead.
Define a property
1
Open User properties
Go to Settings > Organization > User properties. The page is available
to admins.
2
Add a row
Click Add item and fill in the fields below. Each row is one property.
3
Save
Click Save. The property appears under Additional details on every
agent’s profile, and becomes available as a variable in the email signature
editor.
To remove a property, use the delete control on its row and confirm.
Choosing a name
Names must be unique, and each one must contain at least one letter or number. These names are reserved, because the signature editor already offers them as built-in variables:avatar, company, firstName, lastName, name, and
workspace. Saving a property with a reserved name fails with an error on that
row.
Translate
Turn Translate on for values that read as language rather than as data: a sign-off like “Happy to help”, or a job title you want localized. Turn it off for anything that should stay identical everywhere, such as a phone number, an employee ID, or a name. When a property is translated, each agent can review and override the wording for their own value from their profile, so a translation that misses the mark gets corrected by the person it belongs to.Renaming and deleting
Example
An organization wants each reply signed with the agent’s role and their team’s phone number.- An admin defines two properties:
Job title(Text, Translate: Yes) andDirect line(Text, Translate: No). - Each agent opens Settings > Personal > Profile and fills both in under Additional details.
- The admin edits the workspace’s email signature once, inserting Name, Job title, and Direct line.
See also
- Profile: where agents fill in their values
- Email configuration: reference properties in a signature
- User management: invite agents and manage their access
- Context Variables: declare customer data sent by your app