> ## Documentation Index
> Fetch the complete documentation index at: https://forest-chore-open-api.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Invite your team
> Add users, create teams, and assign permissions
Your back-office is in production. This step is about giving your team access, with the right level of permissions for each person.
## Invite a user
1. Go to **Project Settings** → **Users**
2. Click **Invite user**
3. Enter their email address and select a **permission level**
The user will receive an invitation email and can access the back-office immediately after signing up.
## Permission levels
A user's **permission level** sets what they can do with the Forest platform itself, configuration, environments, administration. Forest has five built-in levels, each adding capabilities on top of the previous:
| Level | Adds the ability to |
| ------------- | --------------------------------------------------------------------- |
| **User** | Browse data, view/create/update/delete records, execute actions |
| **Manager** | Manage the inbox and notifications |
| **Editor** | Customize layouts, Smart Views, workspaces, dashboards, and workflows |
| **Developer** | Manage environments and deploy between them |
| **Admin** | Manage teams, users, roles, and project settings |
## Roles and teams
Permission levels are separate from **roles**. Where a permission level governs platform capabilities, a **role** governs *data access*, which collections a user can read or edit, which actions they can trigger, down to field level and conditional rules.
Roles are assigned through teams: group users into a team (e.g. Support, Finance), then attach a role that scopes exactly what that team can touch.
1. Go to **Project Settings** → **Teams**
2. Click **New team** and give it a name
3. Add users to the team
4. Attach a role defining which collections, actions, and fields the team can access
For the full breakdown of roles, collection and action permissions, conditional rules, and approval workflows, see [Roles & Permissions](/get-started/control/roles-permissions).
## What's next
Your team is in. If another developer needs to contribute to the project, the next step covers the developer onboarding workflow.
Set up a development environment for a new developer