Business management · Branches and Multiunit

Headquarters and branches under one command, with isolated operations and a consolidated view

Each branch can have its own CNPJ, administrator, users, permissions, and operational data, working as a subsidiary company isolated from headquarters. Leadership follows every location on a consolidated dashboard and can securely step into each branch's context to manage operations without mixing records, classes, or finances.

The problem and the fix

The problems Branches and Multiunit solves every day

If any of these situations sounds familiar, it is because they happen in almost every graduation company, until the right system comes in.

The problem

The company expands to other cities but keeps treating everything as a single operation.

With Partiu Formatura

Each new location can be provisioned as a subsidiary company with its own corporate identity, administrator, and operational database, while keeping its management link to headquarters.

The problem

Users at one branch can see classes, graduates, or financial figures from another location.

With Partiu Formatura

The branch context limits the administrator's scope, and in the separate-company model the whole location is isolated: the session switches to the branch's company and every module operates inside it.

The problem

Leadership has to add up spreadsheets from every city to know the size and delinquency of the group.

With Partiu Formatura

The headquarters dashboard consolidates graduates, classes, amounts collected, amounts receivable, delinquent graduates, and collection rate, while keeping an individual card for each location.

The problem

Managing a branch requires another browser, another URL, and shared credentials.

With Partiu Formatura

Headquarters enters the branch context right from its own panel, with ownership validation and a new session carrying the effective permissions of that location's administrator; when finished, it returns to headquarters.

The problem

Location details and branding are scattered across documents and old artwork.

With Partiu Formatura

The branch record brings together legal name, trade name, CNPJ, tax registrations, address, contacts, hours, social media, colors, logo, welcome message, and person in charge.

The problem

There is no clarity on who manages headquarters and who should operate a single location only.

With Partiu Formatura

Administrators can be linked to headquarters or to a branch. The headquarters administrator manages them all; a linked administrator only gets the scope of their own location.

In practice

Real examples of Branches and Multiunit working for you

Everyday situations at graduation companies, from the problem to the result, using the modules on this page.

01

New location provisioned without a parallel rollout

The scenario

A graduation company opened an operation in another city, with its own CNPJ and administrative team.

With the system

Headquarters registered the branch and entered the initial administrator, and the system created the subsidiary company, a unique code and subdomain, an admin role, and the hierarchical link to the parent company.

The result

The new location started with its own login and isolated database, while headquarters kept the ability to enter the branch context and follow consolidated KPIs.

02

Leadership follows the group without mixing operations

The scenario

Three branches reported different numbers for classes, collections, and delinquency at month-end close.

With the system

The consolidated dashboard began pulling KPIs directly from each subsidiary company and showing the group total alongside the detail per location.

The result

Meetings started working from a single source, without opening one branch's operational data to another branch's team.

03

Headquarters support inside the branch

The scenario

A location needed help reviewing permissions and settings but could not share the administrator's password.

With the system

A headquarters administrator opened the branch with the manage button. The system confirmed the location belonged to headquarters, switched the session, and loaded the subsidiary's effective permissions.

The result

The change was made in the right context, and on the way back the original headquarters session was restored without keeping any branch data in cache.

How it works

How information flows through Branches and Multiunit

Every step is a real module, and what comes out of one goes into the next without anyone typing it again.

  1. 1Headquarters registersThe company enters the corporate details, address, branding, and initial administrator for the new location.
  2. 2System provisionsA subsidiary company, code, subdomain, user, and admin role are created and linked to headquarters.
  3. 3Branch runs in isolationThe location works with its own users, permissions, classes, finances, and other modules within its own company.
  4. 4Headquarters monitorsThe dashboard consolidates the key numbers and keeps the detail for each branch.
  5. 5Headquarters managesWhen needed, an authorized administrator enters the location's real context without sharing a password.
  6. 6Context is restoredWhen done, the headquarters token, company, and session come back, with the identity cache refreshed.

Module by module

Everything included in Branches and Multiunit

8 modules and 69 features on this page, all running on the same class, graduate and event records.

Branch Company Record

The location registered as a real company, not just a label on reports.

  • Name, internal code, legal name, trade name, and CNPJ
  • State and municipal tax registrations per location
  • Person in charge, phone, WhatsApp, and general, tax, and support emails
  • Full address with ZIP code, street, number, unit, neighborhood, city, and state
  • Its own website, Instagram, Facebook, and business hours
  • Logo, identification color, and primary and secondary colors
  • Welcome message and operational notes
  • Public CNPJ lookup to help fill in the form, with review before saving
  • Activation and deactivation without erasing the location's history

Provisioning as a Subsidiary Company

A branch can start life as an isolated company, hierarchically linked to headquarters.

  • Subsidiary company created with an internal hierarchical link pointing to headquarters
  • Unique code and subdomain generated automatically
  • CNPJ, identity, address, and theme copied from the initial record
  • Initial branch administrator created
  • Password set by headquarters or a securely generated temporary password
  • Admin role seeded with the system's active permissions
  • Persistent link between the branch record and the subsidiary company
  • Compatibility with legacy branches that only use filial_id inside the parent company
  • A branch that is already a subsidiary cannot create another layer of sub-branches

Administrators and Access Scope

Everyone sees the part of the operation they actually manage.

  • Administrator without a linked branch treated as a headquarters administrator
  • Administrator linked to a branch limited to the corresponding filial_id
  • Headquarters screen to assign or remove administrator links
  • Branch management restricted to the headquarters administrator
  • My Details screen so administrators maintain only their own location
  • Entity Framework queries, SQL, and in-memory lists applying the same context
  • Headquarters with no focus sees the full set of permitted locations
  • Headquarters with a selected focus works only with the chosen branch until switching back to All

Secure Headquarters → Branch Navigation

Headquarters manages the location in its real context, without sharing credentials.

  • Validation that the subsidiary belongs to headquarters and is active
  • Entry through the Manage branch button on the headquarters panel
  • Selection of an active administrator at the location to build the context
  • Loading of the effective permissions of the branch administrator's role
  • Access token issued specifically for the subsidiary company
  • Original headquarters session stacked before the context switch
  • Identity cache cleared on entry and on return
  • Return to headquarters restoring the original token, user, company, and session
  • Switching protected against access to a branch that does not belong to headquarters

Consolidated Group Dashboard

An executive view of the whole and operational detail for each subsidiary.

  • Total branches with their own company
  • Total and active graduates per location
  • Number of classes per branch
  • Amount collected and amount receivable per subsidiary
  • Number of delinquent graduates per location
  • Collection rate calculated per branch
  • Consolidated KPIs adding up the subsidiaries
  • Individual cards with city, state, status, and KPIs
  • Direct access from the consolidated card to branch management

Branch Operations Across Modules

The location dimension follows the key operational and management records.

  • Classes, graduates, and installments that can be linked to a branch
  • Accounts payable, accounts receivable, and financial entries per location
  • Employees and payroll parameters filterable by branch
  • CRM leads, customers, opportunities, activities, and campaigns with filial_id
  • Studio services, bookings, photographers, sales reps, galleries, and productions per location
  • Purchase orders, contracts, budget, and financial planning with a branch dimension
  • Journal entries, periods, trial balance, DRE, and accounting calculations filterable by branch
  • Legal cases, collections, and legal KPIs scoped by location
  • Business events, notifications, and workflows preserving filial_id

Branding and Communication per Location

Each branch shows its own details wherever it meets customers and staff.

  • Custom colors and logo stored in the location record
  • Separate customer service, support, and invoicing channels
  • Welcome message configurable by the branch
  • Address and contact details available for documents and communication
  • Badge color used to spot the location quickly in selectors
  • Optional request for a white-label mobile app per branch
  • Branch administrator allowed to update their own details without editing another location

Multi-Location Compatibility and Governance

Expansion without breaking companies that were already operating before the branches feature.

  • Legacy model inside the parent company preserved for records with filial_id
  • Hierarchical subsidiary model added with no mandatory retroactive migration
  • Records with a null filial_id still belong to headquarters in the legacy model
  • Existing branches can continue without their own company
  • Indexes and foreign keys protect branch links
  • Branch existence and context cache invalidated after changes
  • Deactivation blocks new selections without erasing historical data
  • The consolidated view only includes branches linked to subsidiary companies
  • Company-level isolation remains the main boundary in the hierarchical model

Find the right plan for Branches and Multiunit

Compare the modules and choose the setup that fits your operation.