> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-multi-tenant-guides/6.15/configure-multi-tenant/configure-user-settings.md).

# Configure User Settings

Cortex XSOAR 6.15 users can control details, preferences, and notifications, by changing the notifications settings in their user profile.

Each user can define their own settings so that a user's preferences do not affect other users. The user can change the following information by clicking the user profile (bottom-left icon on any page):

* **Details**: Change the name, email, password, etc. They can also set their status as active or away, which enables the user to appear active or away in incidents, tasks, etc. The status can also be set by typing **`setYourselfAs`** in the command line.
* **Preferences**: Set the default landing page, theme, time zone, date format, etc. You can [Set the Default Theme for New Users](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/users-and-roles/set-the-default-theme-for-new-users.md).
* **Notifications**: Configure which notifications to receive and through which channels. Notifications are presented by categories. By default, all of the categories and channels are selected.

{% hint style="info" %}
You can only make changes to a user's details in the main account. You cannot make changes in the tenant's account.
{% 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 by asking a question.

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

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-multi-tenant-guides/6.15/configure-multi-tenant/configure-user-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.