> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidparts/getting-started/finding-your-way.md).

# Find your way around

Switch environments in the header. Each one has its own tabs.

![The Manufacturing Parts tab, with Manufacturing, Design and Admin in the header](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-5c980da9274ba03c19050b3472067c9c2b560b87%2Fmfg-parts-tab.jpg?alt=media)

## Design

| Tab                | What's there                                                                                                 |
| ------------------ | ------------------------------------------------------------------------------------------------------------ |
| Bill of materials  | Subsystems, subassemblies and design parts, with review and comment threads. COTS parts and purchase orders. |
| Assembly readiness | Which subassemblies are ready to build, and what's blocking the rest.                                        |

## Manufacturing

| Tab         | What's there                                                                                                                                 |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Parts       | Every manufacturing part, plus design parts approved for manufacturing and waiting to be created. Drop STEP files here to bulk-create parts. |
| Workstation | One station's queue of MOs, and each MO's work card.                                                                                         |
| Production  | The floor at a glance: work pending and in process, problems, holds, completed MOs and station load.                                         |
| Assembly    | The same readiness view as in Design.                                                                                                        |

## Admin

Open **Sections** to move between them.

![The Admin sections list](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-d00fcda60607b94be185d8a00285335e95df7ea1%2Fadmin-sections.jpg?alt=media)

| Group      | Sections                                                |
| ---------- | ------------------------------------------------------- |
| Operations | Holds, Labels to print, MO History, Seasons, Subsystems |
| Library    | Colors, Base materials, Materials, Thicknesses          |
| Team       | Users                                                   |

## Good to know

* **Everything is live.** When someone starts a step or approves a part, every screen updates right away.
* **Links keep your place.** The address bar holds the open part, MO or station, so you can share a link or reload without losing your spot.
* **QR labels** on parts open that MO's work card when scanned.
* **Tablets:** a Workstation tablet can be pinned to one station. See [Your station](/raidparts/manufacturing-guide/your-station.md).


---

# 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.raidrobotics.org/raidparts/getting-started/finding-your-way.md?ask=<question>&goal=<user_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.