> 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/sign-in-and-access.md).

# Sign in and get access

## Sign in

Open RAIDParts and sign in with the team login. Your account is created the first time you sign in.

## Get a role

A new account has no role, so RAIDParts shows a message asking you to have an admin add you as a designer, a manufacturer, or both. The message lists the admins you can ask. Once an admin grants a role, the page updates on its own.

| Role         | Opens                        | What you do                                                               |
| ------------ | ---------------------------- | ------------------------------------------------------------------------- |
| Designer     | Design                       | Build the bill of materials, review parts, create parts for manufacturing |
| Manufacturer | Manufacturing                | Work MOs at the stations, report problems, run QA                         |
| Admin        | Design, Manufacturing, Admin | Everything, plus users, holds, seasons and the Library                    |

You can hold more than one role.

{% hint style="info" %}
**Designers who create parts also need the Manufacturer role.** Creating a part happens in the Manufacturing environment.
{% endhint %}

## Missing a tab?

You only see the environments your roles allow. If something is missing, ask an admin to check your roles in **Admin › Users**.


---

# 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/sign-in-and-access.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.