> ## Documentation Index
> Fetch the complete documentation index at: https://docs.typewise.app/llms.txt
> Use this file to discover all available pages before exploring further.

# User properties

> Define the details your agents carry, and reference them once in a signature

User properties are the extra details your organization keeps about each agent:
job title, department, direct phone number, a personal sign-off. You declare
each property once, every agent fills in their own value on their
[profile](/documentation/settings/profile), and you reference it once in the
email signature.

The alternative is maintaining a separate signature per person. With user
properties, one template covers the whole team, including people who join later.

<Note>
  User properties describe your own agents. To declare the customer data your
  app sends, use [Context Variables](/documentation/settings/context-variables)
  instead.
</Note>

***

## Define a property

<Steps>
  <Step title="Open User properties">
    Go to **Settings > Organization > User properties**. The page is available
    to admins.
  </Step>

  <Step title="Add a row">
    Click **Add item** and fill in the fields below. Each row is one property.
  </Step>

  <Step title="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.
  </Step>
</Steps>

| Field           | Description                                                                                                                        |
| :-------------- | :--------------------------------------------------------------------------------------------------------------------------------- |
| **Name**        | What the field is called on the agent's profile, for example `Job title`.                                                          |
| **Description** | What the agent should enter. Shown to them as a tooltip on the field. Optional, but it saves you from answering the same question. |
| **Type**        | Text, Number, or Date. Determines the input agents get.                                                                            |
| **Translate**   | Yes translates the value into the language of the conversation. No keeps it exactly as the agent typed it.                         |

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

| Change                | Effect                                                                                                                                                 |
| :-------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Rename** a property | The label changes on every profile. Values agents already entered are kept, and signatures that use the property keep working.                         |
| **Delete** a property | The field disappears from every profile, and the value each agent filled in is deleted with it. Signatures referencing it render nothing in its place. |

<Warning>
  Deleting a property removes the value every agent has entered for it.
  Recreating a property with the same name does not bring those values back:
  each agent has to fill it in again.
</Warning>

***

## Example

An organization wants each reply signed with the agent's role and their team's
phone number.

1. An admin defines two properties: `Job title` (Text, Translate: Yes) and
   `Direct line` (Text, Translate: No).
2. Each agent opens **Settings > Personal > Profile** and fills both in under
   **Additional details**.
3. The admin edits the workspace's email signature once, inserting **Name**,
   **Job title**, and **Direct line**.

Every agent now signs with their own role and number, and a German customer sees
the job title in German while the phone number stays untouched.

## See also

* [Profile](/documentation/settings/profile): where agents fill in their values
* [Email configuration](/documentation/behavior/email#signatures): reference
  properties in a signature
* [User management](/documentation/settings/user-management): invite agents and
  manage their access
* [Context Variables](/documentation/settings/context-variables): declare
  customer data sent by your app