Balerion LogoBalerion
Get started
← ManualTeam

Team and Roles

Six roles, with a finely structured set of permissions above them. What someone sees is determined by the permission, not the role alone.

Create and invite employees

Only a name is required for a security officer. Phone, email, qualifications, Bewacherregister ID, vehicle and place of residence are optional. The account and profile are created in one step without a password. Sign-in uses an SMS code. There is no app access without a phone number.

Office staff are invited by email, with Dispatcher and Quality Management available as roles. The invitation link leads to password setup, remains valid for 7 days and can only be used once.

Balerion Security, Team and Roles: Create and invite employees
All security employees at a glance.

Roles and permissions

There are six roles: Employee, Dispatcher, Customer, Administrator, Owner and Quality Management. Above them is a finely structured set of permissions and three predefined presets: Executive Management with all permissions, Dispatcher and Quality Management. You can create custom roles.

The principle is "denied by default": anyone without an explicitly assigned permission receives a rejection. Read and write are separate permissions. Permissions are checked again for every action. A revoked permission therefore takes effect immediately, even if the person is currently signed in.

No one can assign someone a higher level than their own.

Balerion Security, Team and Roles: Roles and permissions
Roles determine who can see what.

The employee profile

The team list shows metrics and can be filtered by qualifications. Behind it, each security officer has a profile with five tabs: General, Contract and personnel, Payroll, Documents and Site blocks.

The Contract and Payroll tabs are visible to the owner only. Fields relating to tax, bank details, identity documents and contracts are blocked for dispatchers. They are neither displayed nor accepted.

Limit: An emergency contact is not currently provided.

Employment status and standby

Every security officer has an employment status: Active, Standby, Inactive, Former employee, Applicant or Anonymized. It is set in the employee profile and is available as a filter and tile in the team list.

Standby is intended for officers who remain part of the workforce but should not currently be scheduled, for example during parental leave or an extended break. They are no longer included in staffing suggestions and do not count as ready for assignment.

Work already performed remains paid. If a row in the payroll preview relates to an officer on standby, a notice identifies this so that no one mistakes it for an error.

Two displays that are easy to confuse: The Standby tile in the team list counts the employment status. The Reserve tile in the overview instead counts officers who are ready for assignment but have no duty today. They deliberately measure different things.

Balerion Security, Team and Roles: Employment status and standby
Standby reflects the staffing status, not today's shift.

Deactivating and deleting

Deactivation is the normal case, and all evidence is retained. Only the owner may permanently delete someone. Deletion is blocked as soon as worked or billable assignments, security logbook entries, patrol scans or unreturned equipment exist.

This is intentional: evidence that could be removed by deleting an employee would be worthless as evidence.

If information is missing from the profile, you can add it as a custom field.

Related

Updated on: 03.09.2026