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

# My Profile

Getting Here Settings \&gt; My Profile \&gt; Details The Details page under the "My Profile" category displays and allows editing of user-specific information, including contact details, account role, a

**Settings > My Profile > Details**

The **Details** page under the "My Profile" category displays and allows editing of user-specific information, including contact details, account role, and login history.

***

## Page Overview <a href="#page-overview" id="page-overview"></a>

### Top Information Bar <a href="#top-information-bar" id="top-information-bar"></a>

The top section displays key account information:

* **Member Since**: The date the user account was created.
* **Last Login IP**: The IP address from which the user last logged in.
* **Last Login**: The date and time of the user's most recent login.

***

## Profile Details <a href="#profile-details" id="profile-details"></a>

1. **Profile Avatar**
   * **Description**: Displays a circle with the user's initials.
   * **Badge**: Shows the user role in a tag format (e.g., **ADMIN**).
2. **Email**
   * **Description**: Displays the user's email address.
   * **Example**: `peter.paul@netography.com`

***

## Editable Fields <a href="#editable-fields" id="editable-fields"></a>

The following fields can be updated:

1. **First Name\***
   * **Description**: The user's first name.
   * **Example**: `Peter`
   * **Required**: Yes
2. **Last Name\***
   * **Description**: The user's last name.
   * **Example**: `Paul`
   * **Required**: Yes
3. **Nickname**
   * **Description**: An optional nickname for the user.
   * **Required**: No
4. **Phone Number**
   * **Description**: Enter the user's phone number.
   * **Options**: Includes a dropdown to select the country flag/phone code.
   * **Required**: No
5. **Job Title**
   * **Description**: The user's professional title or position.
   * **Required**: No
6. **Picture URL**
   * **Description**: Input a URL to link to a custom profile picture.
   * **Required**: No

***

## Actions <a href="#actions" id="actions"></a>

* **Save Button**: Click to save any changes made to the user's profile.
* **Reset Button**: Click to reset the form to its previous state.
* **Delete User Button**: Click to delete the user profile.

## Notes <a href="#notes" id="notes"></a>

* Fields marked with an asterisk (\*) are **required**.
* User role (e.g., **ADMIN**) is displayed below the profile avatar and cannot be modified from this page.
* **Member Since** and **Login Information** are non-editable fields that provide context for user account activity.


---

# 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.fusion.vectra.ai/settings/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.
