> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/account-and-administration/users-and-roles/how-to-invite-a-team-member.md).

# How to invite a team member

This guide shows you how to invite a person to your organization, with the right type and roles for their job.

{% hint style="info" %}
**Before you start**

* You have the **Admin** or **Super admin** role, or a role with access to invite users.
* Only a **Super admin** can give the **Super admin** role.
  {% endhint %}

## Fill in the invite

{% stepper %}
{% step %}

### Open the users

Go to **Settings** → **Organization** → **Users** and click **Invite**.
{% endstep %}

{% step %}

### Enter the email address

Enter the **Email** of the person.
{% endstep %}

{% step %}

### Choose the type

Under **Type**, choose **Platform user** for a person who works in the Guestway platform, or **Cleaner** for a person who only uses the cleaning app.

You cannot change the type later. If you choose the wrong one, cancel the invite and send a new one.
{% endstep %}

{% step %}

### Choose the roles

Select one or more **Roles**. **Roles** offers only the roles for the type you chose.

{% hint style="success" %}
Give each person exactly the access they need, and keep integrations, API access and billing with a few trusted people. See [About roles](/account-and-administration/users-and-roles/about-roles.md).
{% endhint %}
{% endstep %}
{% endstepper %}

## Send the invite

{% stepper %}
{% step %}

### Send it

Click **Invite**. You see *Invitation sent!* The person gets an email and shows on the **Pending invites** tab until they accept.

If the person is already a user of another organization of your holding, they are added at once, without an invite to accept. You see the email address and *is now a member.* The person gets an email that you added them.
{% endstep %}
{% endstepper %}

## Follow up on the invite

{% stepper %}
{% step %}

### Send the invite again

On the **Pending invites** tab, click **Resend Invite** on the row, then **Confirm**.
{% endstep %}

{% step %}

### Withdraw the invite

If the person must not join, click **Cancel Invite** on the row, then **Confirm**.
{% endstep %}
{% endstepper %}

## Troubleshooting

<details>

<summary>What does "Some of these roles are not for a cleaner" mean?</summary>

A role is either for platform users or for cleaners. Remove the roles of the other type, or change the **Type**.

</details>

## Related

* [Users and roles](/account-and-administration/users-and-roles.md): every role and what it can do
* [About roles](/account-and-administration/users-and-roles/about-roles.md)
* [How to change a user's roles](/account-and-administration/users-and-roles/how-to-change-a-users-roles.md)


---

# 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.guestway.io/account-and-administration/users-and-roles/how-to-invite-a-team-member.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.