Platform structure

Understanding this structure is essential to configuring schedules, calendars and control policies correctly. A well-considered configuration removes the need to enter data over and over and guarantees that every employee always operates under the right rules.

The three hierarchical levels

Level 1: Organisation

The organisation represents the company as a whole. It is the highest level of the hierarchy and the container for everything else.

The configuration at organisation level establishes the default values that will apply to every branch and employee, unless one of the lower levels explicitly overrides them.

What is configured at organisation level:

• Tax and corporate details: trading name, legal name, tax ID and address.
• Primary language and visual identity.
• Default time zone, derived from the organisation's address.
• Global work calendar: base weekly schedule and public holidays that affect the whole organisation.
• Billing and subscription.

Level 2: Branch or project

The branch is the operational unit. It can represent a store, an office, a site, a department or any other functional grouping of employees.

The branch inherits the organisation's entire configuration, but can override those elements that differ from the global set-up. This lets a company with sites in different regions have different local public holiday calendars without needing to create separate accounts.

What can be configured at branch level:

• Name, address and GPS coordinates.
• Check zone and its radius in metres.
• Its own time zone, if it differs from the organisation's.
• Weekly schedule and breaks, which may differ from the organisation's.
• Workday and break mode: strict or flexible.
• Local public holiday calendar.

Level 3: Employee

The employee is the smallest unit in the hierarchy. They are assigned to one or several branches with a given role and receive the effective calendar that results from combining the organisation's configuration with their branch's.

In specific cases —remote employees, workers with irregular schedules, staff on secondment— individual exceptions can be defined that override the branch's values.

What can be configured at employee level:

• Their own time zone (for remote employees in another region).
• Schedule exceptions (one-off or recurring changes).
• Hourly cost (for cost analysis).
• Associated documents (contracts, payslips, certificates).

Cascading inheritance

An employee's effective calendar on a given day is resolved following a clear order of priority:

Employee configuration      (highest priority)
         |
         v
Branch configuration
         |
         v
Organisation configuration  (base priority)

In practice, this means that if the organisation defines the base schedule as 09:00-17:00, but the "South Warehouse" branch has a 07:00-15:00 schedule, and the employee Juan García has an individual schedule exception for the afternoon shift (15:00-23:00), the system will apply Juan García's schedule and use that as the reference for calculating late arrivals, absences and overtime.

This inheritance logic removes the need to configure every employee from scratch and guarantees that changes at organisation or branch level propagate automatically to all the employees affected.

Back office roles

The managers who administer the platform from the web back office operate under one of these three roles:

Mobile app role

The Worker role corresponds to the employee who uses the CheckBiz360 app to clock in. This role has no access to the web back office.

From the app, the Worker can:

• Record entry and exit.
• Consult their own attendance records.
• See their assigned schedule.
• Receive notifications from the platform.
• Access their employment documents (if the document module is active).
• Consult and manage their assigned tasks (if the tasks module is active).

Modules available by role