Skip to main content

Organizational structure

The Structure screen organizes the account in three levels: workspaces, companies and branches. This hierarchy is what separates portfolios, scopes reports and defines on whose behalf communications go out.

Structure

The hierarchy​

Organization (your account)
└── Workspace            ← work environment (e.g. "Retail Group")
    └── Company          ← legal entity, with CNPJ (the "headquarters")
        └── Branch       ← business unit within the company
  • Workspace: only needs a name. The account's first workspace is the main one ("main" badge).
  • Company: name and CNPJ (optional). The first company is the headquarters ("headquarters" badge).
  • Branch (business unit): name and CNPJ (optional), created inside a company.

Simple accounts can live their whole life with one workspace and one company: nothing forces you to create levels you do not use. See also Concepts.

Creating and editing​

On the screen: New workspace, New company (inside the workspace) and New branch (inside the company); names require at least 2 characters. Renaming and editing the CNPJ is unrestricted; the change is reflected in the context selector and in communications. Creating, editing and deleting require the workspaces.manage permission, and everything goes into the audit trail.

The context selector​

When the account has more than one workspace or at least one branch, the header gains a context selector (Workspace · Unit). The Headquarters option represents the workspace's main company, with no branch filter.

Selecting a context:

  • Filters the lists and the dashboard by the chosen unit (tasks, charges, metrics).
  • Scopes record creation: what you create is born in the selected unit.
  • Is stored for 1 year in the browser — you do not re-select on every login.

Email layouts per level​

Each company and branch can point to its own email layout; resolution cascades (branch → company → organization default), which allows different brands per unit.

Deletion protections​

Deletion is always reversible in the database (soft delete), but the system refuses removals that would break the operation:

SituationWhat happens
Deleting the main workspaceRefused (DEFAULT_IMMUTABLE)
Deleting a workspace with companiesRefused (WORKSPACE_IN_USE): remove the companies first
Deleting the headquarters companyRefused (DEFAULT_IMMUTABLE)
Deleting a company with branchesRefused (HAS_BRANCHES): remove the branches first
Deleting a company with customers or chargesRefused (COMPANY_IN_USE): reassign before deleting

In the interface, the delete button does not even appear for the main workspace or the headquarters company — the protection exists at both layers, screen and API.