> 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/certificate-seal-and-signature.md).
# Certificate Seal & Signature
When your Org issues completion certificates, they carry your department's seal, an authorized signature, and your CE provider numbers. Set them up once, and every certificate your Org issues will look official. This requires the **Admin** role.
## Open Certificate Seal & Signature
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 tap **Certificate Seal & Signature**.
## Organization Seal
Tap **Upload seal** and choose a square PNG or JPEG of your seal, ideally with a transparent or white background.
## Authorized Signature
Tap **Draw** to sign right on your screen, or **Upload** to use an image of a signature.
## Authorized Signer
Enter the **Signer name** and **Signer title**, which print under the signature line, for example "Chief A. Smith, Training Officer."
## CE Provider IDs
If your Org is an approved CE provider, tap **Add provider ID**, enter the **Provider ID**, and choose the **Approving body**: **CAPCE**, a **State EMS bureau** (then choose the **State**), or **Other**. You can also add **Attestation text (optional)** to print with it. Tap **Remove** to delete one.
Each change saves on its own as you go. Certificates your Org issues from then on carry your new seal, signature, and provider IDs.
---
# 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/certificate-seal-and-signature.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.
