> 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/roles.md).

# User roles & permissions

{% 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 uses a role-based access system. Every team member is assigned a role that controls what they can see and do in the app. Roles are designed around the natural structure of a food business, so most teams can assign them without much deliberation.

## The roles

### Admin

Full access to everything in FoodCore — including billing, subscription management, and user management. Admins can invite new users, change roles, deactivate accounts, and view or export all data across all features and sites.

Use this role sparingly. Your account owner is always an Admin. You might promote one other trusted person — an operations manager or business partner — but most teams only need one or two Admins.

### Manager

Access to all FoodCore features — recipes, ingredients, food safety, stock, production, menus, labels, business insights, and more — but without the ability to manage billing or invite and deactivate users. A Manager can do everything a chef or dietitian needs, plus reporting and business insights, without touching account-level settings.

This is the right role for a head chef or kitchen manager who needs full operational access but doesn't need to be involved in billing decisions.

### Chef

Access to the day-to-day operational features: ingredients, recipes, food safety, stock management, and production planning. Chefs can create and edit records in all of these areas, run food safety checks, and log monitoring data.

Chefs cannot access business insights, cost reports, billing, or user management. This keeps the role focused on kitchen work without exposing commercially sensitive data unnecessarily.

### Dietitian

Access to recipes, allergens, and nutrition features, with full read and edit permissions across those areas. A Dietitian can review and update allergen declarations, nutritional data, and dietary claims — but doesn't have access to stock, production, food safety records, or financial data.

This role is designed for a nutritionist or registered dietitian working with your recipe team, either in-house or as a consultant.

### Viewer

Read-only access to all features. A Viewer can look at any recipe, ingredient, allergen matrix, food safety record, or report — but cannot create, edit, or delete anything. They also cannot manage users or access billing.

Useful for auditors, compliance consultants, or stakeholders who need visibility into your records without the ability to make changes.

## Customise per feature

A role sets sensible defaults, but it doesn't have to be the last word. **On any user, you can override individual areas of the app** rather than accepting the role's defaults wholesale — useful when someone is *almost* a Chef but shouldn't touch food safety, or a Viewer who should be able to edit one specific area.

**To customise a user's permissions:**

**1. Go to Settings → Team & Users → click the user**

**2. Open Customise per feature**

**3. For each area, choose None, View, or Edit**

* **None** — the user can't see this area at all; it's hidden from their navigation.
* **View** — the user can browse the area and its records, but every control that changes something is unavailable to them.
* **Edit** — full access to create, change, and delete within that area, same as a role that grants it by default.

**4. Save**

The starting point for each area is whatever the user's role already grants — customising a feature only overrides that one area, it doesn't change the rest of the role.

{% hint style="warning" %}
A permission change — whether it's a role change or a per-feature customisation — **takes effect the next time that user signs in**, not immediately. If they're already logged in when you make the change, their current session keeps its existing access until they sign out and back in (or their session naturally expires).
{% endhint %}

## What read-only access actually looks like

A user with **View** access to an area isn't shown an error page or blocked at the door — they see the same page everyone else does, with the parts that change data quietly taken away:

* Buttons that create, edit, delete, or bulk-act are **removed**, not just disabled.
* Editable forms — like a recipe or ingredient's detail view — open as a **greyed-out, read-only view**: every field is still legible, just not editable.
* They can still **browse everything a View permission covers**, including things like an ingredient or recipe's [version history](https://docs.foodcore.io/recipes/version-history.md) — read-only doesn't mean read-nothing, it means look-but-don't-touch.

This is deliberate: a read-only teammate — an auditor, a consultant, a junior team member you're easing in — should be able to find what they need with confidence, not hit dead ends or error messages while trying to do their job.

## Permissions at a glance

| Feature               | Admin  | Manager | Chef   | Dietitian | Viewer  |
| --------------------- | ------ | ------- | ------ | --------- | ------- |
| Ingredients           | ✅ Edit | ✅ Edit  | ✅ Edit | 👁 View   | 👁 View |
| Recipes               | ✅ Edit | ✅ Edit  | ✅ Edit | ✅ Edit    | 👁 View |
| Allergens & nutrition | ✅ Edit | ✅ Edit  | ✅ Edit | ✅ Edit    | 👁 View |
| Labels                | ✅ Edit | ✅ Edit  | ✅ Edit | 👁 View   | 👁 View |
| Food Safety           | ✅ Edit | ✅ Edit  | ✅ Edit | 👁 View   | 👁 View |
| Stock & production    | ✅ Edit | ✅ Edit  | ✅ Edit | ❌         | 👁 View |
| Business Insights     | ✅      | ✅       | ❌      | ❌         | 👁 View |
| Settings              | ✅      | Limited | ❌      | ❌         | ❌       |
| User management       | ✅      | ❌       | ❌      | ❌         | ❌       |
| Billing               | ✅      | ❌       | ❌      | ❌         | ❌       |

## Changing a role

You can assign a role when you [invite a team member](https://docs.foodcore.io/team-and-users-core/invite.md), or change it at any time afterwards.

**To change a role after invitation:**

**1. Go to Settings → Team & Users**

**2. Click the team member's name**

**3. Select Change Role**

**4. Choose the new role and confirm**

The change is saved immediately, but as with per-feature customisation above, it **takes effect at the user's next sign-in** — not for their current session if they're already logged in.

## Multi-site access

If your account has multiple sites, you can restrict any user (regardless of role) to one or more specific locations. A user restricted to a single site only sees records, stock data, and food safety information for that location — they have no visibility of other sites, even as a Viewer.

To update a user's site access, go to **Settings → Team & Users → click the user → Edit Sites**.

Multi-site restrictions layer on top of role permissions: a Chef restricted to Site A has Chef-level access to Site A only.

## What's next

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