> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/adalo-account/account.md). # Account View your team name and update your Email or Password ## Team Name Your team name is displayed at the top of the Profile section. If you are a team admin, you can edit it by clicking on the name and entering a new one. This is also the name reflected on your Adalo Invoices. *** ## Profile The Profile section is where you manage your personal account details and security settings. #### Your Info * **Email Address:** The email address associated with your Adalo account. Click **Edit** to update it. * **Your Name:** Your display name. Click **Edit** to update it. *** ## Developer Mode Developer Mode gives you access to tools for building custom component libraries for the Adalo Marketplace. Toggle this on or off from your Profile. For more information, visit [developers.adalo.com](https://developers.adalo.com). *** ## Two-Factor Authentication (2FA) Two-factor authentication adds an extra layer of security to your account by requiring a verification code in addition to your password at login. --- # 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.adalo.com/adalo-account/account.md?ask=&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.