> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/systems/roles.md).

# Roles

Roles and loadouts system. How to set them up.

***For design documentation on this system, use the link below.***

{% content-ref url="/spaces/hffJRpQgXgXOOhvtML3c/pages/JaHf0GF547z77lUDBS8N" %}
[Broken mention](broken://spaces/hffJRpQgXgXOOhvtML3c/pages/JaHf0GF547z77lUDBS8N)
{% endcontent-ref %}

Roles are the jobs players get at the start of a round, they decide what the player will spawn with and what permissions they will have in their ID Cards.

### Features

**Permission Checking**\
ID Cards have a set of permissions that allow you to have access to restricted areas or open locked containers.

**Loadouts**\
Loadouts set what each role spawns with, things like outfits and starting items, like a baton for a security officer.

**Role Selection**\
The system chooses players's roles the moment they join the lobby, currently a single player is chosen as Security and every other player gets the Assistant role.


---

# 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://ss3d.gitbook.io/systems/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.