> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/user-settings/personalizing-the-experience.md).

# Personalizing the Experience

### Overview

Personal settings control profile identity and UI preferences.

Most changes apply to a single Teammate profile.

### Key Concepts

* **Profile settings**: identity fields used in comments, assignments, and audit history
* **Appearance**: UI theme selection for readability
* **Language**: UI label language and locale formatting (when enabled)

### How It’s Used

Use these settings during onboarding.

Revisit settings before governance sessions and training to standardize readability.

### Benefits

* Faster recognition in people pickers and activity feeds
* Improved readability for long working sessions
* Reduced misinterpretation of dates and system labels across regions

### Setup Steps

Start with the matching guide:

* [My Profile](/user-settings/my-profile.md)
* [Appearance](/user-settings/appearance.md)
* [Language](/user-settings/language.md)

### Best Practices

* Use a stable display name for audit continuity.
* Use Light theme during screen sharing in bright rooms.
* Standardize date interpretation across delivery teams when multiple locales exist.

### Summary

Personal settings improve collaboration clarity and UI readability.

Related: [Browser Compatibility](/getting-started/browser-compatibility.md)


---

# 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://help.transform.ai/user-settings/personalizing-the-experience.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.