> For the complete documentation index, see [llms.txt](https://bikecheck.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bikecheck.gitbook.io/guide/shop-owners/build-your-team.md).

# Build your team

Your staff use their own personal BikeCheck accounts. You invite them with a code; they join from their Settings.

## Roles

| Role             | What they can do                                                                                          |
| ---------------- | --------------------------------------------------------------------------------------------------------- |
| **Mechanic**     | Works tasks on the Kanban board                                                                           |
| **Receptionist** | Runs the front desk: answers bookings, checks bikes in and out, walk-ins, the team roster                 |
| **Fleet rider**  | Gets one of your fleet bikes assigned to them: its log, service requests and stolen report — nothing else |

Mechanics don't handle bookings; the owner and receptionists do.

## Invite someone

1. On your **Dashboard**, in the **Team** section, choose **Add team member**.
2. Pick the **role**.
3. Choose **Generate code** and copy it.
4. Send the code to the new team member. The code doesn't expire: it stays valid until it is redeemed or revoked.

![Add team member: pick the role, then Generate code](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-437d990b7a8c8dd3b4170ac3e9b2c1f76ae63c22%2Fteam-add.jpg?alt=media)

5. The new member enters it in **Settings → Join a business** (see [Join a shop](/guide/shop-staff/join-a-shop.md)).

{% hint style="info" %}
A team member must have a verified identity to join. Each person — and each unused code — takes a **staff seat**. If you have no free seat, add one under [Billing](/guide/shop-owners/billing.md).
{% endhint %}

Codes never expire on their own. Revoke an unused code from the roster when you no longer need it.

## Manage the roster

Click the arrow next to a team member to see their details: name, email and phone. From there you can:

* change their **Role** — mechanic, receptionist or fleet rider;
* **View log** — their activity: tasks and ratings;
* **Fire** — remove them from the shop. Their open tasks go back to the board unassigned.

![Jonas Weber's details in the team roster](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-d1a45370ebe73ff44ff969a5cb3451e0adaf7878%2Fteam-roster.jpg?alt=media)

Changing a role and removing someone ask for your password.


---

# 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://bikecheck.gitbook.io/guide/shop-owners/build-your-team.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.