> 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/batch-add-certs.md).
# Batch Add Certs
Just ran an academy, or a whole shift earned the same Cert? Add it to everyone's Locker in one pass. This requires the **Officer** or **Admin** role (see [Org Administration](/organizations/org-administration.md) to check yours).
## Tap + and Batch Add Cert
Tap **Orgs** in the navigation bar, tap your **Org Card**, then tap the **Manage Icon** in the top right corner of the Org's profile, then **Manage Member Certs**. Tap the **Floating Action Button (FAB)**, the red circle with a **+** at the bottom right, and choose **Batch Add Cert**.
## Select Members
On **Select Members**, tick each Member who earned the Cert. The count at the top keeps track. Tap **Next: Cert Details**.
## Enter the Cert Details
Fill in the details the Members share, like the **Cert name**, **Cert type**, and dates, exactly as you would when you [Add a Cert](/my-certs/add-a-cert.md). The **Recipients** list at the top shows who'll receive it. Tap **Create cert**.
## Check the Results
CertLocker tells you how many Lockers the Cert was added to. If it couldn't be added for some Members, it will name them, so you can try again for just those people instead of the whole group.
---
# 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/batch-add-certs.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.
