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

# Managing your team

{% hint style="info" %}
📦 Available on **FoodCore Core**. [Upgrade your plan](https://docs.foodcore.io/getting-started/essentials-vs-core.md) to access this feature.
{% endhint %}

FoodCore's Team & Users feature lets you bring your whole kitchen team into the system — chefs, managers, dietitians, and viewers — each with the right level of access for their role. No passwords are ever sent in an email: every team member sets their own via a secure invite link, so only they ever know it.

{% embed url="<https://youtu.be/-6WhZmx20Ws>" %}

![Team & Users overview](https://2634348187-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG8od1eHZMN9iqk1QqWM2%2Fuploads%2Fgit-blob-0e5e54d7c544d1359a8eb1e0bc3543c6193b4dab%2Fusers.png?alt=media)

## Why it matters

Running a kitchen is a team effort, and your recipe management, food safety records, and labelling should reflect that. When everyone works in the same system with their own account, you get a clear audit trail of who made what change and when — useful for compliance, accountability, and just understanding how your records evolve over time.

FoodCore's role system is designed around the natural structure of a food business. A chef doesn't need to see billing. A manager doesn't need to manage users. A viewer should be able to check allergen information without accidentally editing a recipe. Each role is scoped to give people exactly what they need — nothing more, nothing less.

## What you can do

* **Invite team members** by email. They receive a secure link to set their own password and are in within minutes.
* **Assign roles** at the point of invitation, or change them later. Roles control what each person can see and do in FoodCore.
* **Customise per feature** — override an individual user's access area by area (None, View, or Edit) on top of their role's defaults, for the cases where a role is a good starting point but not quite right. See [User roles & permissions](https://docs.foodcore.io/team-and-users-core/roles.md#customise-per-feature).
* **Restrict site access** — if you run multiple locations, you can limit a user to a single site so they only ever see the data relevant to them.
* **Deactivate leavers** quickly. When someone leaves the team, deactivate their account in seconds. They lose access immediately and can't log in again.
* **Resend invites** for team members who haven't accepted yet. Useful if the invite landed in spam or someone joined later than expected.

## Who can manage users?

Only **Admin** users can invite, edit, and deactivate team members. If you're the account owner, you're an Admin by default. If you need to delegate user management, promote a trusted colleague to Admin.

## Getting started

The fastest way to get your team set up is to invite them in order of seniority — Admins and Managers first, so they can assist with onboarding the rest of the team if needed. See [Invite a team member](https://docs.foodcore.io/team-and-users-core/invite.md) for the full steps.

Once your team is in, review their roles to make sure everyone has the right level of access. See [User roles & permissions](https://docs.foodcore.io/team-and-users-core/roles.md) for a breakdown of what each role can and can't do.

## Essentials accounts

Essentials accounts are single-user — the account owner only. If you need to bring in additional team members, you'll need to upgrade to Core, which includes unlimited users.

## What's next

* [Invite a team member](https://docs.foodcore.io/team-and-users-core/invite.md)
* [User roles & permissions](https://docs.foodcore.io/team-and-users-core/roles.md)
* [Essentials vs Core — plan comparison](https://docs.foodcore.io/getting-started/essentials-vs-core.md)
