> 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.md). # Org Administration Many hands make light work. If you're an Officer or Admin, CertLocker gives you the tools to keep your whole department compliant: see every Member's Certs at a glance, run training sessions, build compliance reports, and manage who's on the roster. ## Check Your Role Tap **Orgs** in the navigation bar and look at the status on the **Org Card**. If it reads **Officer** or **Admin**, you'll find a **Manage Icon** in the top right corner of the Org's profile. Tap it to open **Manage Org**.

Manage Org, with CertLocker Content, CertLocker Reporting, and Organization sections

## What's on Manage Org Manage Org is organized into three sections. Officers see the tools they can use, and Admins see everything. Tap the **Info Icon** beside any row for a quick description. **CertLocker Content** * **Custom Cert Types**: Create your department's own Cert Types (see [Custom Cert Types](/organizations/org-administration/custom-cert-types.md)). * **Training Sessions**: Schedule training, track attendance, and credit your Members (see [Training Sessions](/organizations/org-administration/training-sessions.md)). **CertLocker Reporting** * **Compliance**: Your department's standing at a glance (see [Compliance Reports](/organizations/org-administration/compliance-reports.md)). * **Manage Member Certs**: Every Member's Certs, by type or by Member (see [Manage Member Certs](/organizations/org-administration/manage-member-certs.md)). * **Report Preferences**: How far ahead your reports look for expiring Certs (Admins only, see [Compliance Reports](/organizations/org-administration/compliance-reports.md)). **Organization** * **Manage Members**: Invitations, join requests, roles, and ranks (see [Manage Members](/organizations/org-administration/manage-members.md)). * **Departed Member Records**: Records kept from Members who have left (see [Departed Member Records](/organizations/org-administration/departed-member-records.md)). * **Edit Profile**: Your Org's name, logo, contact details, and visibility (see [Edit Org Profile](/organizations/org-administration/edit-org-profile.md)). * **Certificate Seal & Signature**: What appears on the certificates your Org issues (see [Certificate Seal & Signature](/organizations/org-administration/certificate-seal-and-signature.md)). You'll also see **Shift Positions**, **Stations**, **Apparatus**, **Equipment**, and **Hydrants**. These describe your department for the other FireCal apps your department uses, such as Shifts and TruckCheck, and are covered in those apps' guides. ## Leave or Delete At the bottom of Manage Org, **Leave Organization** removes you from the Org (see [Leave an Org](/organizations/leave-an-org.md)), and for Admins, **Delete Organization** starts the process of deleting the Org (see [Delete an Org](/organizations/org-administration/delete-an-org.md)).

The bottom of Manage Org with Leave Organization and Delete Organization

--- # 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.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.