> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/settings/personal-settings.md).

# Personal settings

Your profile, password, two-factor authentication and sessions.

Your personal settings are only yours: admins can't change them. Open them from your avatar at the top right.

{% embed url="<https://app.screendesk.io/recordings/97e3a86c-4f66-4349-8054-78d016ea33ef>" %}

| Page                | What it's for                                                                                                                                                          |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **My profile**      | Name and photo, sign-in security, and your [video call preferences](https://docs.screendesk.io/video-calls/video-call-settings.md#your-preferences-as-a-host)          |
| **My availability** | When people can book you. See [Schedules and calendars](https://docs.screendesk.io/scheduling/connect-your-calendar.md#my-availability).                               |
| **Notifications**   | Which emails you get. See [Notifications](https://docs.screendesk.io/settings/personal-settings/notifications.md).                                                     |
| **Connected apps**  | Your own Google or Outlook calendar, and your own Linear, GitHub or Jira account                                                                                       |
| **MCP** and **CLI** | Use Screendesk from AI tools and your terminal. See [MCP](https://docs.screendesk.io/debug-with-ai/mcp.md) and [CLI](https://docs.screendesk.io/debug-with-ai/cli.md). |
| **API tokens**      | See [API tokens](https://docs.screendesk.io/settings/personal-settings/api-tokens.md).                                                                                 |

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2FuVrwDqJRx3Lqe5crHHj9%2Fdocs-panel-profile.png?alt=media" alt="Your avatar, My profile"><figcaption></figcaption></figure>

***

### Password

In **My profile → Security**, enter your current password and the new one. If your workspace signs in with SSO, you won't see this.

### Two-factor authentication

Available on Plus, Pro and Enterprise.

1. In **My profile → Security**, click **Set up** next to two-factor authentication.
2. Save your recovery codes somewhere safe. Each works once, if you lose your phone.
3. Scan the QR code with an authenticator app such as 1Password, Authy or Google Authenticator.
4. Enter the 6-digit code it shows.

From then on, Screendesk asks for a code after your password. To stop, click **Turn off**.

### Log out everywhere

Available on Plus, Pro and Enterprise. In **My profile → Security**, click **Log out everywhere** to sign out of every browser, app and extension, this one included. Use it if you lose a device or think someone else has access.

### Delete your account

At the bottom of **My profile**, click **Delete your account**. It removes your account and all your data, and can't be undone.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/settings/personal-settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
