> ## 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 Structure Approvals for Holdings and Franchises
- URL: https://blog.jestor.com/structure-approvals-holdings-franchises/
- Published: 2026-09-15T20:20:31.000Z
- Updated: 2026-09-15T20:20:31.000Z
- Author: Bruno Bannach

Structuring approvals for holdings and franchises means deciding, deliberately, what stays centralized and what stays local — instead of every unit inventing its own version of the same process. In **Jestor**, this is a configuration choice: connected fields for franchises, option fields for smaller holdings, and alçadas set centrally or per entity.

The mistake most holdings make isn't choosing the wrong structure — it's not choosing one at all, and letting each unit's approval process drift independently over time.

## What goes wrong without a deliberate structure

- Each franchise or subsidiary building its own local approval process
- No consolidated view for the parent company across all units
- Inconsistent alçada rules between entities doing the same kind of work
- Difficulty onboarding a new unit because there's no template to follow

## How to structure it deliberately

- Use a **connected field** for franchises — many similar units, added dynamically over time
- Use an **option field** for a small, relatively fixed number of holding entities
- Decide which alçada rules are centralized (parent company policy) versus local (unit-specific)
- Build one process template that every new unit onboards onto, instead of starting from scratch

## Why Jestor fits this use case

- Multiple **Omie** accounts connect under one structure, priced by users, not by entity count
- The same approval template scales whether you have 3 units or 300
- Central visibility doesn't require removing local flexibility where it's genuinely needed
- New entities onboard onto an existing template instead of a blank slate

| Structure           | Recommended approach              |
| ------------------- | --------------------------------- |
| Franchise network   | Connected field, dynamic          |
| Small holding group | Option field, centralized alçadas |

## Frequently Asked Questions

**Can a new franchise unit reuse an existing template?** Yes, that's the recommended approach for consistency. More at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

**Does the parent company see all units' approvals?** Yes, through a consolidated view across connected entities.

**Can local units still have some independent rules?** Yes, alçadas can be centralized or set per entity as needed.

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 and see how to take your company's operations to a new level of efficiency and control.