> 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/update-cert-details.md).

# Update Cert Details

Keep your Cert data current.

## Tap to Edit

When looking at your Locker, **Tap a Cert** to open it. On the **Certification** screen, you can change the Cert's name and dates right where you see them: tap the name to edit it, or tap the **Calendar Icon** beside **Issued** or **Expires** to pick a new date. Your changes save as you go.

## Open Cert Details

For everything else, tap the **Info Icon** (the circled **i**) in the top right corner of the Certification screen to open the **Cert details** pane.

<figure><picture><source srcset="https://946479658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbOWuzIpL5k2toZeIBVvC%2Fuploads%2Fgit-blob-469fb7c10d129e5ae45c591db47d80de5710973e%2Fcertlocker-cert-details-pane-dark.png?alt=media" media="(prefers-color-scheme: dark)"><img src="https://946479658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbOWuzIpL5k2toZeIBVvC%2Fuploads%2Fgit-blob-b79ab943977c55f409da9c380e879910fbce1467%2Fcertlocker-cert-details-pane.png?alt=media" alt="The Cert details pane with Details (Cert ID, Instructor, Issuing locality), Notes, and Privacy" width="375"></picture><figcaption></figcaption></figure>

Under **Details**, tap to add or change the **Cert ID** (the ID issued by the certifying agency, the one you'd give an employer or a licensing office), the **Instructor**, and the **Issuing locality**. At the bottom of the Details card is the Cert's **ID**, CertLocker's own reference for this record. You won't need it day to day, but if you ever contact us for help with a Cert, tap the **Copy Icon** beside it and include it in your message.

**Notes** is yours to fill with anything worth remembering about this Cert. If you imported the Cert with AI, CertBot's notes are kept separately from yours. People you share the Cert with can read your notes too, so keep that in mind.

Further down, you'll find **Privacy** (see [Keep a Cert Private](/my-certs/keep-a-cert-private.md)), **Sharing** (see [Invite to View](/sharing-certs/invite-to-view.md)), and **Expiration reminder**, where you can change when we remind you about this Cert's expiration. Tap **Done** when you're finished.

## Change the Cert Type

If you picked the wrong Cert Type, tap the type shown under the Cert's name. CertLocker will ask **Change cert type?** and explain what happens: your name, dates, attachment, credential number, instructor, locality, and notes all stay, but your **renewal progress, CE credit, and applied training are reset**, because a different type tracks different requirements. Tap **Choose new type** to pick the right one, or **Cancel** to leave it as is.

<figure><picture><source srcset="https://946479658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbOWuzIpL5k2toZeIBVvC%2Fuploads%2Fgit-blob-82d1fa2da468fc1af05d31d825a0ac21ff7a8202%2Fcertlocker-change-type-dialog-dark.png?alt=media" media="(prefers-color-scheme: dark)"><img src="https://946479658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbOWuzIpL5k2toZeIBVvC%2Fuploads%2Fgit-blob-8aadceab45b7171b2062f57240c6254b7d1bf046%2Fcertlocker-change-type-dialog.png?alt=media" alt="The Change cert type? dialog with Cancel and Choose new type" width="375"></picture><figcaption></figcaption></figure>

{% hint style="info" %}
**If a change doesn't save**, CertLocker will tell you. Reopen the Cert and check what was saved before trying again.
{% 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/my-certs/update-cert-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.
