> For the complete documentation index, see [llms.txt](https://guides.tability.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.tability.io/docs/become-a-tability-power-user/features/account/account-settings.md).

# Account settings

You account settings is where you can configure parts of the app that are specific to you. Your Tability account is not tied to any specific workspace, and your settings here will apply across all of your workspaces.

{% hint style="info" %}
If you're looking for how to configure settings for your workspace go to [Workspace Settings](/docs/become-a-tability-power-user/features/workspace-settings.md)
{% endhint %}

Your **account settings** consists for 4 main settings:

* Your account details and profile settings
* Notification settings
* Managing your standups
* Personal integrations

To access your account settings, click on your **profile picture** in the top right corner of the app. A sliding panel will appear from the right.

<figure><img src="/files/ceWSfag85tOk5wc5XvUc" alt=""><figcaption><p>Account settings menu in Tability</p></figcaption></figure>

## Manage your Tability account

To manage your account details like email, name, or password, click on the **manage your Tability account** option.

<figure><img src="/files/zUyNiA6Of3PM9vrWtm5s" alt=""><figcaption></figcaption></figure>

In your Tability account settings you'll be able to:

* Change your profile image
* Change your name and how it appears in Tability
* Update your primary email. This is where you will receive all of your notifications.
* Enable 2-Factor Authentication
* Delete your account

## Notification settings

In your notification settings, you'll be able to configure exactly what type of notifications you would like to receive.

There are 4 main ways to receive notifications from Tability:

* **Email notifications:** Standard email notifications you'll receive to your account email address
* **Chat notifications:** Notifications sent through integtated apps (ie. Slack or Microsoft Teams)
* **Mobile notifications:** Push notifications sent if you have the Tability mobile app installed on iOS or Android
* **System notifications:** Notifications for admins to receive tips or about changes to your workspace (ie. when new users join your workspace)

## Managing Standups

Here you'll be able to change the frequency of your standups. This changes how often you receive notifications to post a new standup.

## Personal integrations

Most integrations in Tability are managed at the workspace level. However, some apps have differnet requirements and permission levels and require you to log in via your own account. This is where you will find integrations that are set at an account level.

Currently, Google is the only integration that requires this. Learn more about the Google Sheets integration.

{% hint style="info" %}
For all other integrations, you can find them in [Workspace Settings](/docs/become-a-tability-power-user/features/workspace-settings.md)
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guides.tability.io/docs/become-a-tability-power-user/features/account/account-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.