> 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/ranks-and-app-access.md).
# Ranks & App Access
Your Org's rank ladder lists the ranks in your department, from the top down, and draws the line between Officers and everyone else. Setting it up takes a minute, and it makes everything else in CertLocker know who's who. This requires the **Admin** role (see [Org Administration](/organizations/org-administration.md) to check yours).
## Open the Rank Ladder
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, tap **Manage Members**, then tap the **Rank Ladder Icon** in the top right corner of the Manage Members screen.
## Build Your Ladder
Tap **Add rank** to add a rank, and give it a name. Drag ranks by their handles to put them in order, with the highest rank at the top, and drag the line labeled **Officer Line: Everyone above is an officer** so it sits just below your lowest Officer rank. Tap the **Trash Icon** beside a rank to remove it. Tap **Done** when you're finished.
## Set a Member's Rank
Back on the **Members** tab, tap a Member's **Rank Chip** (or **No rank**) and choose their rank. A Member ranked above the Officer Line becomes an Officer right away.
## Choose a Member's Apps
If your department uses other FireCal apps, tap a Member's **Apps** chip to open **App access**. Every Member has all of your department's apps by default. Untick an app to take it away from this Member, then tap **Save**. Officers and Admins always keep every app.
---
# 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/ranks-and-app-access.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.
