> 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/getting-started/welcome-back.md). # Welcome Back Your Locker came with you. If you had a CertLocker account before, your account came with you into the new CertLocker. There's no need to register again or re-upload your Certs. ## Sign In with Your Existing Email Sign in with the same email address you've always used for CertLocker (see [Sign In & Reset Password](/getting-started/sign-in.md)). If you don't remember your password, tap **Forgot password?** and we'll send you a link to set a new one. ## Read Your Welcome Message The first time you sign in, you'll see a welcome message telling you what came with you, for example how many Certs you have and which Orgs you belong to. On a phone the message fills the screen, and on a tablet or computer it appears in a card in the middle of the page. Tap **Take a look** (or the **X** to close it), and you'll land on your [Daily Briefing](/getting-started/daily-briefing.md). The message only appears once, so if you move on, it won't show up again. ## Check Your Locker Take a few minutes to open **My Certs** and look over a few of your Certs, checking their dates, Cert IDs, and attachments against your own records (see [Your Locker](/my-certs/your-locker.md)). {% hint style="info" %} **If something seems to be missing**, first check that you signed in with the email address you used before (you can see it at the top of the **More** screen). Please don't upload the same documents again until you've confirmed what's already in your Locker. If you still can't find something, email us at with the names of the Certs that are missing, and we'll help. {% 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/getting-started/welcome-back.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.