Skip to content
SkyRosterBook a discovery call

Platform · Configuration

Your operation. Your settings.

Configure shift patterns, working-time rules, approvals and access for your units. Administrators manage supported settings in the platform; additional capabilities can be scoped separately.

Workflow settings

Define shifts and request workflows.

Shifts and patterns

Define shift types, times, rest requirements, display settings and repeating patterns. Reuse demand profiles from one roster period to the next.

Request approvals

Set approval chains for leave, duty, work requests, off requests, shift extensions and swaps. Leave and duty can use separate operational and non-operational chains; other chains are configured by unit.

Approval steps identify eligible roles and membership scopes. Off requests share the work-request approval configuration. An empty chain allows automatic approval, so each request type needs a deliberate policy decision. See leave and duty requests.

Configure rule thresholds and priorities.

Switch supported rules on, set thresholds and periods, and adjust their weights. Some can be hard requirements or soft preferences. Others are fixed product rules.

Hard violations take priority over coverage and soft preferences in scoring. A rule’s setting must reflect its operational and regulatory status. See the rule catalogue and scoring explanation.

Vacation Score

Set scoring periods and dated overrides. Use the resulting Vacation Score when reviewing competing leave requests.

Tactical shortfalls

Configure how day and night staffing shortfalls are evaluated. These settings do not authorise a reduction in required operational staffing.

Organisation settings

Apply unit settings and individual terms.

Time and calendars

Set the working day, night window and week. Add each unit’s holiday calendar. The same settings inform scheduling, attendance and payroll.

Inherited terms

Let unit terms flow to sub-units and staff. Protect a unit’s contract or set individual terms where they need to differ.

Access permissions

The right access for each role.

Read and write access can be configured separately across platform areas, from an employee’s own records to organisation-wide access. Write access cannot exceed read access. Use built-in roles, custom roles and date-limited role assignments.

Explore access permissions

Set read and write access for each of 16platform areas. A role can view a wider set of records than it can edit. Try the controls below to explore how each scope changes access.

  • Permission areas

    16

  • Scope tiers

    6

  • Read / write axes

    Independent

  • Write may exceed read

    Never

The permission matrix

Every area gets its own Read row and Write row. Pick a column on either row to set that area's scope for that axis, the two rows are completely independent, which is how a role can see broadly but edit narrowly, never the reverse.

16permission areas, each with an independent read scope and write scope from the6-tier membership ladder.
Securable areaNoneIndividualSelfless PUPrimary unitSelfless mem.MembershipGlobal
Organization settings
Read
Write
Dashboard management info
Read
Write
Competency management
Read
Write
Competency matrix
Read
Write
Shift management
Read
Write
Roster management
Read
Write
Sector management
Read
Write
Tactical planning
Read
Write
Reports
Read
Write
Resource management
Read
Write
Leave requests
Read
Write
Leave management
Read
Write
Baseline requests
Read
Write
Baseline management
Read
Write
Locked intervals
Read
Write
Attendance management
Read
Write

No access
No access at all.
Individual
Only the user's own record.
Selfless primary unit
Primary-unit scope, excluding the user's own record.
Primary unit
The user's own primary organisational unit.
Selfless membership
All units the user is a member of, excluding their own record.
Membership
All units the user is a member of.
Global
The entire organisation.

Exclude a manager’s own record

Illustrative example

Two tiers on the ladder, Selfless primary unit andSelfless membership · are identical to their plain counterparts except for one subtraction: the user's own record. They exist for approval workflows, so a manager can act on their team's requests without that same permission letting them act on their own.

Team Manager's write scope on Leave Requests approval
  • M. Ionescu Team Manager✓ Eligible to approve · including their own request
  • A. Radu Controller✓ Eligible to approve
  • B. Enache Controller✓ Eligible to approve
  • C. Tudor Controller✓ Eligible to approve
  • M. Ionescu Team Manager✕ Not eligible, it is their own request
  • A. Radu Controller✓ Eligible to approve
  • B. Enache Controller✓ Eligible to approve
  • C. Tudor Controller✓ Eligible to approve

Scope

Plan for additional requirements.

The interface is available in English and Portuguese, including notifications and rule-violation messages. Additional languages require translation and configuration work.

Standard configuration remains within the supported product. New rules, connectors or bespoke functionality are assessed separately, including release support and any dedicated-hosting requirement. See pricing and deployment options.

Discuss the settings your operation needs.

Start with a 20-minute discovery call about your unit structure, scheduling rules and approval process. We’ll then arrange a demonstration tailored to your priorities.