Balerion LogoBalerion
Get started
← ManualTeam

Team and roles

Six roles sit above a finely structured permission vocabulary. What someone can see is determined by the permission, not by the role alone.

Creating and inviting employees

Only a name is required for an employee. 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. You can select Scheduler or Quality Management. The invitation link opens the password setup, is valid for 7 days and can be used only once.

Balerion Security, Team and roles: Creating and inviting employees
All security employees at a glance.

Roles and permissions

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

The principle is "denied by default": anyone without an explicit permission is denied. Reading and writing 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. Each employee has a profile with five tabs: General, Contract and Personnel, Billing, Documents and Site blocks.

Only the owner can see the "Billing" tab. The "Contract & Personnel" tab is also visible to users with a payroll or personnel permission. Without payroll administration, it is read-only. For everyone else, fields relating to tax, bank details, identification and contract are blocked. They are neither displayed nor accepted.

The deployment list in the record appears only with permission to read the schedule.

Limit: An emergency contact is not currently supported.

Personnel status and Standby

Each employee has a personnel status: Active, Standby, Inactive, Former, 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 employees 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 deployment.

Work already performed remains paid. If a row for an employee on Standby appears in the payroll preview, a notice points this out so that no one mistakes it for an error.

Two indicators that are easy to confuse: The Standby tile in the team list counts the personnel status. The Reserve tile on the overview instead counts employees who are ready for deployment but have no shift today. They deliberately measure different things.

Balerion Security, Team and roles: Personnel status and Standby
Standby reflects the staffing status, not today's shift.

Deactivating and deleting

Deactivation is the standard procedure and preserves all evidence. Only the owner can permanently delete an employee. Deletion is blocked as soon as worked or billable deployments, Wachbuch entries, patrol scans or equipment that has not been returned 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