Balerion LogoBalerion
Get started
← ManualVerwaltung

Organizational Units

For companies with several branches: who can see which sites, orders, and security officers.

Requirements

  • Permission to manage organizational units, which the standard dispatcher does not have
  • For assigning users: owner

Creating units

Under Settings, Organizational units, you model the company as a tree, for example with branches and departments beneath them. The tree can be up to five levels deep.

A unit is not a separate tenant. Separation between companies remains unaffected. Units only narrow access within your company.

A unit can only be deleted if it is truly empty. Subunits, sites, security officers, orders, assigned users, and loans are checked.

While no unit exists, the entire module is hidden. The "Unit" field only appears for a site, order, or security officer when there is something to select.

Balerion Security, Organizational Units: Creating units
The company can be divided into units.

Assigning access

Under User management, every office employee receives access to their units. No selection means access to the entire company, as before. If a unit is selected, the person sees that unit and all units beneath it.

No one can change their own assignment, including an owner. This prevents someone from accidentally locking themselves out.

Security officers themselves have no unit access. They have a home unit to which their personnel file and payroll belong.

Balerion Security, Organizational Units: Assigning access
The security employee record shows which unit they belong to.

How to tell that something is filtered

This is the most important point because it can easily look like an error:

  • Lists are shortened silently. There is no "filtered" notice and no count.
  • A record outside your unit cannot be found by you. If a colleague can see an order that you cannot find, the unit assignment is almost always the reason.
  • Records without a unit remain visible to everyone. Existing data therefore does not disappear when units are introduced.

An additional rule applies to orders: if an order has a site, it inherits the site's unit and the field is locked.

Balerion Security, Organizational Units: How to tell that something is filtered
The entire board can be switched to a single unit.

Lending security officers

If a security officer is temporarily helping at another branch, lend them to that branch for a limited period from the Loan tab in the employee profile. An end date is optional. Without one, the loan continues indefinitely.

The loan only extends where the security officer can be scheduled. The personnel file and payroll remain with the home unit. At the end of the period, nothing is moved. The security officer simply disappears from the target unit's candidate list again.

A security officer can be loaned to several units at the same time. Overlapping loans are not prevented.

Visible does not mean assignable

For loaned security officers, two different reference dates apply, which regularly prompts questions:

  • A security officer is visible in the palette before their loan begins so that the target unit can plan ahead.
  • They are only assignable when the shift start falls within the loan period.

You can therefore correctly drag a visible security officer onto a shift and still have the assignment rejected because the shift is before the loan begins or after it ends. The palette is a planning preview, not a promise that an assignment will be accepted.

Loaned security officers carry the label "Loaned from another unit" or "Loaned until" with a date in the palette and shift schedule. Anyone whose unit access is unrestricted never sees this label because all units are already available to them.

Related

Updated on: 03.09.2026