> 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/organizations/org-administration/custom-cert-types.md).
# Custom Cert Types
Every department has qualifications of its own, like an internal driver certification, a specialty team, or a local credential that isn't in our catalog. **Custom Cert Types** let you define them, with your own renewal requirements, so they can be tracked just like any other Cert. Officers and Admins can create them.
## Open Custom Cert Types
Tap **Orgs** in the navigation bar, tap your **Org Card**, tap the **Manage Icon** in the top right corner, then tap **Custom Cert Types**. You'll see your department's types, with how often each one renews.
## Tap + to Create
Tap the **Floating Action Button (FAB)**, the red circle with a **+** at the bottom right (or choose **Create Custom Cert Type** from the **+** on Manage Member Certs), and the **New Cert Type** screen opens.
## Name It
Under **Identity**, enter the type's **Name \*** (the only required field), and if it helps, a **Level**, an **Abbreviation**, a **Display name override**, and a **Description**.
## Classify It
Under **Classification & discipline**, choose what kind of credential it is and its discipline, such as **EMS** or **Fire**. Under **Validity**, set how long the Cert is good for with **Valid for** and **Units** (for example, 2 years), and under **Standards**, add the **Standard** it meets and its **Edition / section**. **Issuing authority** shows your Org, since internal types are issued by your organization.
## Set Its Renewal Requirements
Under **Renewal requirements**, tap **Add Component** for each part of the renewal (like Airway or Operations), and give it a **Component name \*** and a **Quantity \*** with its **Units**. To break a Component down further, tap **Add Requirement** inside it. Add **Topics** to each Component and Requirement, and training with matching topics will credit itself automatically. A type with no Components renews by re-issue only.
If your department uses TaskBook, **Earned via qualification book** can link the type to a qualification book, so completing that book issues this Cert automatically.
## Publish It
Your work saves as a draft as you go, but Members won't see the type until you publish it. Tap **Publish** at the bottom, then confirm on **Publish This Version?** by tapping **Publish**.
To change a published type later, open it, make your changes, and tap **Publish New Version**. You can look back at every version you've published under **Version history**.
If you try to leave with unpublished changes, CertLocker asks what you'd like to do: **Save for later**, **Publish**, **Delete draft** (or **Discard draft, keep published** if the type was published before), or **Stay on page**.
## Retire or Delete a Type
To stop using a type without deleting it, open it, tap the **Overflow Menu** (the three dots) in the top right corner, and choose **Deprecate type**, then confirm with **Deprecate**. You can bring it back any time with **Restore type**.
To delete a type, tap the **Trash Icon** beside it on the list, then confirm with **Delete**. Certs already issued with that type keep their recorded details.
## Issue the Type to Members
Once published, your type appears at the top of the Cert Type list when anyone in your Org adds a Cert. To add it to your Members' Lockers yourself, use [Manage Member Certs](/organizations/org-administration/manage-member-certs.md) or [Batch Add Certs](/organizations/org-administration/batch-add-certs.md).
---
# 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/organizations/org-administration/custom-cert-types.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.
