> 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/manage-members.md).
# Manage Members
Managing an Org's Members requires the **Admin** role. 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 **Manage Members**. You'll see three tabs: **Members**, **Invites**, and **Requests**.
## Members
The **Members** tab lists everyone on the roster, with each person's role and rank. Type in **Filter by name…** to find someone quickly.
Each Member shows three chips:
* **Role** (**Admin** or **Member**): Tap it for **Role actions**, like **Make admin**, **Remove admin role**, or **Remove from org**.
* **Rank** (for example **Captain** or **Engineer**): Tap it to **Set rank** (see [Ranks & App Access](/organizations/org-administration/ranks-and-app-access.md)).
* **Apps**: Tap it to choose which FireCal apps this Member can use (see [Ranks & App Access](/organizations/org-administration/ranks-and-app-access.md)).
When you tap **Remove from org**, CertLocker will ask **Remove member?** to be sure. Tap **Remove** to confirm. An Org always needs at least one Admin, so the last Admin can't be removed.
{% hint style="info" %}
**Where are Officers?** In CertLocker, Officers come from your rank ladder: everyone ranked above the **Officer Line** is an Officer. To make someone an Officer, give them an Officer rank (see [Ranks & App Access](/organizations/org-administration/ranks-and-app-access.md)).
{% endhint %}
## Invite Members
To invite someone to your Org, tap the **Invite Icon** (the red circle with a person and a **+**) at the bottom right of any tab. The **Invite to org** sheet opens with a search bar. Start typing a name, and when you see the right person, tap **Invite**.
Each person in the results shows whether they're **Eligible to invite**, have already been sent an invite (**Invite sent**), have **Requested to join**, or are **Already a member**.
## Manage Invites
Tap the **Invites** tab to see everyone you've invited who hasn't responded yet. Tap a pending invite's **Overflow Menu** (the three dots) to **Resend** it, or **Cancel invite** to take it back (confirm with **Cancel invite**, or tap **Keep** to leave it). When there's nothing pending, you'll see **No pending invites**.
## Manage Requests
People can ask to join a public Org. Tap the **Requests** tab to see who's waiting, then tap a request's **Overflow Menu** to **Approve** or **Deny** it. CertLocker asks **Deny request?** before turning someone away, so tap **Deny** to confirm, or **Keep** to decide later. When there's nothing waiting, you'll see **No pending requests to join.**
---
# 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/manage-members.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.
