For the complete documentation index, see llms.txt. This page is also available as Markdown.

Multiple sites & sharing

📦 Available on the Core plan.

If you run more than one location, Settings → Sites is where you add and manage them, and where you decide what's shared across every site and what's kept separate per site.

Adding a site

Go to Settings → Sites and add each location you run. Once you have more than one site, a site switcher appears so you can move between them, and you can restrict individual users to a single site — see User roles & permissions.

Sharing

Below your site list, the Sharing panel controls whether three areas are shared across all sites or kept per site:

Area
Default
What "per site" means

Recipes

Shared

Each site can see and use every recipe

Menus

Per site

Each site has its own set of menus

Food safety config

Per site

Each site has its own templates, storage units, and settings

These defaults were chosen to match how FoodCore already behaved before multi-site existed, so switching on a second site never changes anything about your first site unless you deliberately go into Sharing and change a toggle.

To change how an area is shared:

1. Go to Settings → Sites → Sharing

2. Toggle the area — Recipes, Menus, or Food Safety — to Shared or Per Site

3. If you're switching to Shared, confirm the prompt

Switching a toggle to Shared offers to apply it retroactively — to bring everything that already exists into the shared pool, rather than only affecting things you create from that point on. Confirm the prompt and FoodCore does this for you; decline and only new records go into the shared pool.

What's always shared, no matter what

Ingredients, label templates, and stock have no site dimension at all — they're shared across every site regardless of what the Sharing toggles say, and there's no setting to change that. A shared ingredient library and label set is what keeps your allergen data and label designs consistent everywhere you trade.

Records already written never move

Sharing only affects the recipes, menus, and configuration you set up — it never touches records that already happened. Daily Due Diligence checks, cleaning logs, and monitoring records always stay stamped with the site that made them, permanently, no matter how you set Sharing afterwards. This is what keeps your food safety history honest: a temperature check always shows which fridge, at which site, it was actually taken at.

Per-item control for recipes and menus

Sharing sets the default for a whole area, but you don't have to go all-or-nothing. On the Recipes and Menus pages, you can control visibility item by item:

1. Tick the cards for the recipes or menus you want to change

2. Use the bulk bar that appears at the bottom of the page

3. Choose which sites should see the selected items

This is the tool to reach for when almost everything should be shared but a handful of recipes or menus are specific to one location — a shared core menu with a couple of site-only specials, for example — without switching the whole area to Per Site.

What's next

Last updated