Skip to content
SkyRosterBook a discovery call

Trust · Access control

Match access to operational responsibility.

Set what each role can view and change across sixteen permission areas. Scope access to an individual, unit or organisation, and set dates for temporary responsibilities.

Permission areas

Build permissions around each role’s work.

Build each role from the areas it needs to use. Set the scope of access separately for each one:

Organisation settingsRoster managementBaseline requestsBaseline managementLeave requestsLeave managementResource managementTactical planningAttendance managementCompetency managementCompetency matrixShift managementSector managementLocked intervalsReportsDashboard information

A seventeenth marker, none, exists alongside them: setting a role's permission for an area to none switches that area off for anyone holding only that role, rather than defaulting to some minimal read access. Splitting requests from management, and the competency matrix from competency management, is deliberate: it lets an organisation grant someone the authority to approve a leave request without also granting them the authority to redefine the leave policy, or to see the whole organisation's qualification matrix without being able to edit a single qualification in it.

Within several of these areas the model goes one level finer still: leave requests, for example, separates create, delete, send-reminder and cancel into independent actions, and baseline (work, off, swap) requests separates approve and decline from the act of creating one. An organisation can grant a team manager the authority to approve a swap without granting them the authority to delete a leave request.

Try it

Explore how read and write scopes interact.

Adjust the scopes and watch the access change. For each role and area, write scope stays within read scope.

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

The membership scope ladder

Choose how far access reaches.

Both the read scope and the write scope of a permission are set to one of the same seven levels, from no access up to the whole organisation:

LevelReaches
NoneNo access at all.
IndividualOnly the user's own record.
Selfless primary unitEveryone in the user's primary unit, excluding the user's own record.
Primary unitThe user's own primary organisational unit, including themself.
Selfless membershipEvery unit the user is a member of, excluding the user's own record.
MembershipEvery unit the user is a member of, including themself.
GlobalThe entire organisation.

The two “selfless” scopes exclude the user’s own record. For example, a manager can receive leave-approval access for colleagues in their primary unit without receiving access to approve their own request through that grant. Review the combined effect of all roles assigned to the user.

Read and write, independently

Grant visibility without the same editing rights.

A role can see across the organisation while editing only its own unit. Read and write are separate settings, so visibility does not have to bring editing rights with it.

For the same role and area, the system limits write scope to the configured read scope. Administrators can grant broad visibility with narrower editing access.

Temporary roles

Set temporary access for cover and secondments.

Give someone temporary access for leave cover, a secondment or a project. Set the start and end dates. The temporary role stops applying the day after its end date.

When several roles apply, the effective permission uses the widest read and write scopes and grants visibility if any role allows it. Temporary roles combine with standing roles, so review the resulting access across all assignments.

Role configuration

Adapt built-in roles to your organisation.

Start with one of five built-in roles. Adapt the permissions to the way your team works:

User

Access personal information and qualification status, and submit leave and duty requests.

Membership user

View the team roster and use shift swaps where permitted by the organisation.

Team manager

Manage team schedules, coverage and leave or duty requests.

Head of unit

Oversee roster preparation, qualification validity and exceptional approvals.

Organisation admin

Manage staff records and organisational data, and prepare reports for payroll.

These five are a starting point, not a ceiling. An administrator can create an unlimited number of custom roles, each independently configuring read and write access across all sixteen areas, and assign any user one or more roles, permanent or temporary, in whatever combination their organisation's actual authority structure requires.

Configurable

Where this is enforced

Test combined roles and record access.

Review how permissions are applied to API operations and individual records on the security page.

Read next

Related security and deployment information

Bring your roles into the evaluation.

Describe your roles and approval responsibilities in a 20-minute discovery call. We’ll use them to shape the access-control part of a tailored demo or evaluation.