> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Run Operations Across Multiple Units
- URL: https://blog.jestor.com/operations-across-multiple-units/
- Published: 2026-09-17T22:31:27.000Z
- Updated: 2026-09-17T22:31:27.000Z
- Author: Bruno Bannach

To manage **operations across multiple units**, you need one standardized process and strict separation of data. Franchises and multi-site groups fail on whichever of the two they neglect.

## The two opposite failure modes

Groups tend to over-correct in one direction or the other.

- Every unit building its own process, so nothing is comparable
- One shared system where units see each other's data
- Reporting assembled by asking each unit for numbers
- Standards defined centrally and ignored locally

## What the structure needs

| Requirement                | How it is met                                                       |
| -------------------------- | ------------------------------------------------------------------- |
| **One process**            | A template duplicated per unit, or a shared table with a unit field |
| **Data separation**        | Permissions scoped so each unit sees only its own records           |
| **Consolidated reporting** | A central dashboard reading across all units                        |
| **Local autonomy**         | Units interact with the process without being able to change it     |

## How to set it up in Jestor

1. Build the standard process once in **Jestor**, or install a template.
2. Add a unit or company field, or duplicate the table per unit — duplication copies structure and automations without records.
3. Scope permissions so each unit sees only its own records.
4. Give unit staff interaction access rather than full control, so the process stays standard.
5. Build a central dashboard reading across every unit.

## Why choose Jestor for multi-unit operations?

**Jestor** applies permissions by role, field, and action, which is what allows one build to serve every unit while keeping their data apart — the alternative is maintaining separate systems that drift.

For groups with several registered companies, multiple **Omie** accounts can be connected to a single panel, with products attributed to the correct entity by CNPJ verification.

## Frequently Asked Questions

### Can units see each other's data?

Only if you allow it — permissions can scope each to its own. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### How do I stop units changing the process?

Give interaction access rather than full control.

### Can I report across all units?

Yes, from a central dashboard.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.