> ## Documentation Index
> Fetch the complete documentation index at: https://docs.recepai.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Team members

> Who from your hotel can sign in, and what each of them can reach.

**Team members** is where you give your colleagues access, and decide how much of it each one gets.

***

## What is on the screen

Everyone from your hotel with access, and what each of them can reach.

Access is not one switch. A person is given the areas they need — guests, requests, reviews, reservations, marketing — and, within those, whether they can act or only look.

***

## What you do here

<Steps>
  <Step title="Add the person">
    **Add Team Member**, then enter their name, their work email and a password. You are creating the account directly — there is no invitation email, so tell them their password yourself and ask them to change it.
  </Step>

  <Step title="Give them what their job needs">
    A receptionist who works the request board does not need your billing screens. Smaller access is not distrust — it is a cleaner screen for them and less to explain on their first day.
  </Step>

  <Step title="Archive people who leave">
    **Archive Team Member** closes their access without erasing what they did. The history of who handled which request stays intact.
  </Step>
</Steps>

<Warning>
  **Archive, do not share logins.** A shared account means the activity trail says nothing about who did what — and when that person leaves, the only way to close the door is to change a password everyone was using.
</Warning>

***

## What happens next

A new member can sign in straight away with the email and password you set. Access changes take effect the next time they load the panel.

There is no password-change screen here. If someone needs a new password, they use **Forgot password?** on the sign-in screen and set it themselves.