Skip to main content

Multi-site and Teams

Brikly is built for hospitality businesses that operate across multiple locations. Whether you run two sites or twenty, the workspace model keeps everything organised, secure, and easy to manage.

The workspace concept​

A workspace is the top-level container in Brikly. It represents your business or organisation. Within a workspace, you can manage:

  • Multiple sites (individual kitchens, restaurants, or venues).
  • Team members with different roles and access levels.
  • Shared resources like suppliers, ingredients, and recipes.

Every user belongs to a workspace and can be given access to one or more sites within it.

Workspace (your business)
├── Site A (e.g. City Centre Restaurant)
│   ├── Recipes
│   ├── Invoices
│   └── Costings
├── Site B (e.g. Waterfront Bistro)
│   ├── Recipes
│   ├── Invoices
│   └── Costings
└── Shared
    ├── Suppliers
    ├── Ingredients
    └── Team Members

Managing multiple sites​

Adding a site​

  1. Go to Settings > Sites.
  2. Click Add Site.
  3. Enter the site name and any relevant details (address, contact information).
  4. Save.

The new site is immediately available. You can start adding site-specific recipes, processing invoices, and tracking costings for it.

Switching between sites​

Use the site selector in the top navigation bar to switch your active site. The data you see - invoices, recipes, costings - updates to reflect the selected site.

tip

If you manage multiple sites, make a habit of checking the site selector before uploading invoices or creating recipes. This ensures data lands in the correct site.

Data isolation​

Brikly enforces strict data isolation between sites where it matters:

Site-specific data​

The following data is kept separate for each site:

  • Invoices - an invoice is always linked to the site that received the delivery.
  • Recipe costings - cost calculations are site-specific because ingredient prices may differ between locations.
  • Menus and dish assignments - which dishes are served at which site.

Shared data​

Some data is shared across all sites within a workspace to avoid duplication:

  • Suppliers - your supplier list is workspace-wide. If two sites order from the same supplier, there is one supplier record.
  • Ingredients - the master ingredient list is shared, though prices can vary by site.
  • Recipes - recipe definitions (ingredients and quantities) are shared, but costings are calculated per site based on local prices.
  • Team members - users are managed at the workspace level, with per-site access controls.
info

Sharing suppliers and ingredients across sites means you only need to set them up once. When a supplier sends a new invoice to any site, the system's learned matching patterns apply across the board.

Practical examples​

Scenario: Two restaurants, same menu, different suppliers. Both sites share the same recipes. Site A buys chicken from Supplier X at one price; Site B buys from Supplier Y at a different price. Each site's dish costings reflect its own ingredient prices.

Scenario: A restaurant group with a central kitchen. The central kitchen site handles bulk purchasing. Satellite sites receive prepared components. Each site tracks its own invoices and costings independently.

Scenario: Seasonal pop-up alongside a permanent restaurant. Add the pop-up as a temporary site. It shares the workspace's ingredient and supplier data but has its own invoices and costings. When the season ends, the site can be archived.