> 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/find-and-join-an-org.md).
# Find & Join an Org
Find your crew.
## Tap + and Find an Organization
Tap **Orgs** in the navigation bar, tap the **Floating Action Button (FAB)**, the red circle with a **+** at the bottom right, then tap **Find an organization**.
## Search by Name
Start typing the Org's name, and the results will update as you type. When you see your Org, tap it to open its profile.
## Request to Join
On the Org's profile, tap **Request to Join**. Your request is sent to the Org's Admins for review, and the Org will appear in **My Orgs** as **Request Pending**. Once an Admin approves, you're a **Member**, and you'll get a notice in your [Inbox](/more/inbox.md). Changed your mind? Tap **Withdraw** on the Org Card (or **Withdraw Request** on the profile).
{% hint style="info" %}
**Can't find your Org?** Some Orgs are private, which means they don't accept join requests and only welcome new Members by invitation. Ask your department's Admin to invite you (see [Org Invites](/organizations/org-invites.md)). If your department isn't in CertLocker yet, you can [create it](/organizations/create-an-org.md).
{% endhint %}
---
# 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/find-and-join-an-org.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.
