> 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/my-certs/add-a-cert.md).
# Add a Cert
Know the details? Type them right in.
If you'd rather enter a Cert yourself, or you don't have a copy handy to photograph, you can add it by hand.
## Tap + to Create
Tap **My Certs** in the navigation bar, tap the **Floating Action Button (FAB)**, the red circle with a **+** at the bottom right, then choose **Create a Cert**. You'll be taken to the **Add Cert** screen. (You can also get here from **Add a cert** on your [Daily Briefing](/getting-started/daily-briefing.md).)
## Name Your Cert & Pick Its Type
Give your Cert a **Cert name \***, which is how it will appear in your Locker.
Next, choose its **Cert type**, which should reflect the issuing agency and level of certification, for example **NREMT: EMT-B** for a National Registry EMT Basic. Tap the **Catalog Icon** at the end of the **Cert type** field to open **Pick a cert type**, then search for your Cert. Types created by your department are listed first, under the department's name, followed by the full catalog.
We're adding to our catalog of Cert Types all the time, but if yours isn't listed yet, type its name in the search and tap **Use "your text" as your own cert type**, or tap **Other (type your own)**. The field will read **Cert type (Other)**, ready for you to edit.
{% hint style="info" %}
**Pick the right type when you can.** Catalog types come with their renewal requirements built in, so CertLocker can track your progress requirement by requirement and suggest your expiration date. A Cert can't be created without a type.
{% endhint %}
## Add the Details
Fill in the **Cert ID** (the number issued by the certifying agency), along with the **Instructor** and **Issuing locality** if they apply.
## Set the Dates
Pick the **Certification date** when you earned this Cert, then the **Expiration date**. For many catalog types, CertLocker will suggest the expiration date as soon as you pick the certification date, so double check it against your card. If this Cert never expires, leave the **Expiration date** set to **Never**.
## Attach Your Cert
To attach a copy of your Cert, tap **Upload attachment**. On a phone or tablet, choose **Take Photo** to photograph your paper Cert, **Choose from Photos**, or **Choose from Files**. On the web, you'll pick a file from your computer. PDFs, PNGs, JPGs, and HEIC photos all work, and images are converted to PDF so all your Certs share and print the same way.
## Track Renewal & Reminders
If your Cert Type doesn't come with its own renewal requirements, you'll see a **Renewal progress** section where you can enter the **CE units required** to renew and any **CE units earned (manual)** so far. Below that, **Expiration reminder** sets when we'll remind you about this Cert, and **Notes** is yours for anything else worth remembering.
## Tap Create Cert
When you're finished, tap **Create cert** at the bottom (or **Save** at the top). If anything required is missing, CertLocker will point you to it. Otherwise, your Cert is created and opens on the **Certification** screen. Tap **My Certs** to return to your Locker, where you'll find it waiting.
Next, see [Track Renewal Progress](/my-certs/track-renewal-progress.md) to start crediting training toward your renewal.
---
# 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/my-certs/add-a-cert.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.
