## Overview

The **Profile** page gathers your **personal details** and the **security of your user account**.
It is different from the **Account** settings (company administration, agents and teams): here you
adjust only what belongs to **you**.

In one place you can:

- Update your **name, photo, interface language** and **font size**.
- Set your **message signature**.
- **Change your password**.
- Enable **two-factor authentication (2FA/MFA)** with an authenticator app.
- Review and **end sessions** open on other devices.
- Generate and **regenerate your personal API token**.
- Adjust **sound alerts** and notification preferences.

## Prerequisites

- Be **signed in** with your user (every option is per agent and does not affect the team).
- For 2FA: have an **authenticator app (TOTP)** installed on your phone — for example Google
  Authenticator, Authy or 1Password.
- Some options may be **hidden** when the operator locks profile editing (installs with managed
  login/SSO). In that case, talk to your administrator.

## Step by step

1. Open your user menu and go to **Profile**.
2. In **basic details**, adjust **name**, **display name** and **email**; upload or remove the
   **photo**. Changing the email **ends your session** for security — you will sign in again.
3. In **interface**, choose the **language** and the **font size**.
4. In **message signature**, write the text appended to your replies and save.
5. In **password**, enter your **current password**, set the **new one** (at least 6 characters) and
   **confirm** it.
6. In **security (2FA)**, enable two-factor authentication (see the section below).
7. In **active sessions**, review the devices and **end** any you do not recognize.
8. In **access token**, copy or **regenerate** your personal API token.

## Settings & options

### Profile details
- **Name / display name / email** and **photo**. The display name is what appears in conversations.

### Language and font
- **Interface language**: changes only for your user.
- **Font size**: tunes how the dashboard reads.

### Message signature
- A **rich-text** editor appended to your replies.
- **Pasted images** inside the signature are removed on save (the platform warns you) — use text and
  formatting.

### Password
- Requires your **current password** to confirm the change.
- New password with **at least 6 characters**; the confirmation must **match**.

### Two-factor authentication (2FA/MFA)
- Adds a **temporary code** (from the authenticator app) on top of your password at sign-in.
- **Enable**: the platform shows a **QR Code**; scan it in your authenticator app (or use the
  **manual entry** option with the secret key), type the **6-digit code** and confirm.
- **Recovery codes**: once finished, the platform shows a list of codes — **download** them as a
  `.txt` file or **copy** and store them safely. Each code works **once** and is used when you do not
  have the app at hand.
- **Regenerate codes**: creates a new list (invalidating the previous one) and requires a **valid
  code**.
- **Disable**: requires your **password** and a **valid code** (from the app or a recovery code).
- 2FA may not appear if the operator **did not enable** the feature on the install.

### Active sessions
- Lists each session with **device, browser, approximate location** and **last activity**.
- The **current session** is flagged and cannot be ended from this list.
- **Ending** a session disconnects that device immediately.

### API access token
- A **personal** token to use the API on your behalf.
- **Copy** (with show/hide) and **Regenerate**.
- When you regenerate, the **previous token stops working immediately** — update wherever it is used.
- API usage details live under **Integrations**.

### Sound alerts
- **Audio** preferences for notifications. The remaining notification options are in the
  Notifications article.

## Use cases

- **Protect the account**: enable 2FA and keep the recovery codes.
- **Lost my phone**: end the open sessions and change the password.
- **A token leaked**: regenerate the access token to invalidate the old one.
- **Standardize support**: set a consistent message signature.

## Tips, limits & best practices

- Enable **2FA** whenever possible — it is the most effective protection against unauthorized access.
- **Keep the recovery codes** off your phone (password manager, vault).
- Treat the **API token like a password**: never share it or put it in public code.
- Review **active sessions** from time to time and end anything you do not recognize.
- Remember: changing the **email** ends your current session.

## Troubleshooting

- **Lost my 2FA app**: sign in with a **recovery code**; then, on the security page, **regenerate**
  the codes or **disable and re-enable** 2FA.
- **I don't see the 2FA section**: the feature may not be enabled by the operator on your install.
- **I can't change the password**: confirm the **current password**, use **6+ characters** and check
  that the **confirmation matches**. If the password fields are missing, profile editing may be
  locked by the administrator.
- **Token leaked or stopped working**: **regenerate** the token and update the integrations using it.
- **I don't recognize a session**: **end** that session and then **change the password**.

## See also

- [Notifications and preferences](/hc/ajuda/articles/administration-notificacoes-en)
- [Login, profile and 2FA](/hc/ajuda/articles/getting-started-login-perfil-2fa-en)
- [Integrations: Slack, Dialogflow, webhooks, API](/hc/ajuda/articles/administration-integracoes-en)
- [Account, agents and teams](/hc/ajuda/articles/administration-conta-agentes-equipes-en)