> For the complete documentation index, see [llms.txt](https://docs.firecal.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.firecal.app/more/change-email-and-password.md).
# Change Email & Password
## Change Your Password
Tap **More** in the navigation bar, then tap **Change Password**. Enter your **Current password**, then your **New password**, and type it again in **Confirm new password**. The same password rules apply as when you registered (an uppercase letter, a lowercase letter, a number, a symbol, and at least 12 characters). Tap **Save**, and you'll see **Password changed**.
Forgot your current password? Sign out, then use **Forgot password?** on the sign in screen (see [Sign In & Reset Password](/getting-started/sign-in.md)).
## Change Your Sign In Email
Tap **More** in the navigation bar, tap **Edit Profile**, then tap **Change email**. Enter your **Current password**, then your **New email**, and type it again in **Confirm new email**. Tap **Save**.
We'll send a verification link to your new address. Open it to finish the change, then sign in with your new email from then on. If CertLocker can't make the change (for example, if that email is already in use, or your password doesn't match), it will tell you why.
{% hint style="info" %}
**Your sign in email works in every FireCal app**, so changing it here changes it everywhere.
{% endhint %}
---
# 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.firecal.app/more/change-email-and-password.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.
