> 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/admin-guide/users-and-roles.md).

# Users and roles

## Add a person

1. Ask them to sign in to RAIDParts once. That creates their account.
2. Open **Admin › Users** and find them.
3. Click **Add Designer**, **Add Manufacturing** and/or **Add Admin**, in any combination. The matching **Remove** buttons take a role away.

Their screen updates on its own once they have a role. **Rename** sets the name shown in RAIDParts; **Delete** removes the account.

![Admin › Users, with Add and Remove role buttons (emails blurred)](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-e8cf980fad0ce68f8bc215a32a28e7530529e94a%2Fadmin-users.jpg?alt=media)

{% hint style="info" %}
Designers who create parts also need **Add Manufacturing**, since creating a part happens in the Manufacturing environment.
{% endhint %}

## Safety rules

* The last admin can't be removed or deleted.
* You can't delete your own account.

## First install

On a brand-new install with no admins, the first person to sign in can make themselves admin. This stops working as soon as any admin exists.

![Onboarding and season setup](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-d79188093280ab3c277fec789bfee2541647a687%2F10-onboarding.png?alt=media)


---

# 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/admin-guide/users-and-roles.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.