> 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/my-profile.md).

# My Profile

### Overview

Profile settings define how a Teammate appears across Projects.

Accurate profile fields improve collaboration and auditability.

### Key Concepts

* **Display name**: appears in assignments, comments, and mentions
* **Profile photo**: improves recognition in people pickers
* **Security settings**: sign-in and authentication controls (when enabled)

### How It’s Used

Use profile settings during onboarding.

Update profile settings when a name, role, or security policy changes.

### Benefits

* Faster recognition during reviews and handoffs
* Cleaner audit history with stable identity details
* Reduced sign-in risk when security controls are enabled

### Setup Steps

Use the full setup guide:

* [My Profile Configuration](/getting-started/profile-configuration.md)

### Best Practices

* Use a stable display name for audit continuity.
* Avoid storing sensitive information in profile fields.
* Prefer SSO-managed identity fields as the source of truth when enabled.

### Summary

Profile settings control identity fields used across collaboration and audit history.


---

# 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/my-profile.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.