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

# Profile

In the Profile Settings, users can manage and customize their personal information and preferences.

Below are the main features commonly available in this section:

* **Personal Information:** View and edit basic user details such as: Name, Email, Phone number, etc.
* **Reset Password:** Allows users to change their current password. Requires entering the old password and confirming the new password for security purposes.
* **MFA Configuration (Multi-Factor Authentication):** Enable or disable **Multi-Factor Authentication** to enhance account security.
* **Notification Settings:** Configure how you receive notifications: **Email** notifications, **In-app** notifications.
* **View Upload:** Review assets uploaded by the user on **HIVO**.
* **External Account (Third-Party Integrations):** Manage and configure linked third-party applications or tools (if applicable).
* **Dashboard Settings:** Options related to the interface: The **HIVO dashboard** provides a quick overview of key features and important information.
* **Logout on Other Devices:** A button to log out of the account on other devices to ensure safety when not in use.

If you have any questions, don't hesitate to ask, we're always here to help!


---

# 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://support.hivo.co/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.
