> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/cerby-web-app/accounts/managing-your-accounts/edit-the-account-details.md).

# Edit the account details

{% hint style="info" %}
**Who can use this feature?**

* Workspace **Owners**, **Super Admins**, **Admins**, and **Users**
* **Account Owners**
* Supported using the Cerby web app and mobile app.
  {% endhint %}

As an account **Owner**, you can edit the account details to ensure they match your app and help Cerby automation run successfully.

To edit the account details, you must complete the following steps:

1. Log in to your[ Cerby](https://app.cerby.com/) workspace.
2. Click the corresponding account card. The account details page is displayed with the **General** tab activated.
3. Hover the mouse over the field you want to edit:
   * **Account label in Cerby:** It is the name assigned to your account in Cerby.
   * Login URL: It is the login URL entered manually for self-managed accounts. For managed accounts, this field is not displayed.
   * **Username:** It is the username you use to log in to your account.
   * **Current password:** It is the password you use to log in to your account.
   * **Email linked to account:** It is the email address associated with your account. You can use a Cerby-managed email by following the instructions in the article [Set up and associate a Cerby-managed email address for your account](/cerby-web-app/accounts/managing-your-accounts/set-up-and-associate-a-cerby-managed-email-address-for-your-account.md).
   * **Phone number linked to account:** It is the phone number associated with your account. You can use a Cerby-managed phone number by following the instructions in the article [Set up and associate a Cerby-managed phone number for your account](/cerby-web-app/accounts/managing-your-accounts/set-up-and-associate-a-cerby-managed-phone-number-for-your-account.md).
   * **Custom fields:** They are customized information fields added manually. For more information, read the article [Add and manage custom fields for your accounts](/cerby-web-app/accounts/managing-your-accounts/add-and-manage-custom-fields-for-your-accounts.md).
   * **Notes:** They provide additional information about your account. For more information, read the article [Save and manage account notes](/cerby-web-app/accounts/managing-your-accounts/save-and-manage-account-notes.md).
4. Click the **Edit** icon of the corresponding field to make it editable.
5. Enter the new value in the field.
6. Click the **Done** icon to save the changes. A success message box is displayed.
7. Repeat steps 3 to 6 as necessary.

Now you are done.


---

# 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.cerby.com/cerby-web-app/accounts/managing-your-accounts/edit-the-account-details.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.