Roles, permissions & company boundaries
Give people the access they need, within the right company and team scope.
What each role is for
A person can hold several roles. Roles and organisational-unit scopes are checked by the API; a visible link alone never grants permission. An administrator is not automatically entitled to every manager operation.
- Learner: take available courses and see your own learning records.
- Author: create and publish learning content where authorised.
- Manager: assign learning and inspect permitted team progress and reports.
- Administrator: maintain company profile settings and inspect administration information.
- Owner: manage other members’ role scopes and prepare company SSO.
Manage existing members
Owners cannot use this screen to change their own access or remove the last active owner. Suspension is a restrictive action; reactivation needs a platform recovery procedure, not a simple toggle. New-member invitations and self-service provisioning are not available in this screen yet.
- Open Company settings → People & access.
- Find the member and inspect the exact role and team scope.
- As an owner, add or remove the required scope and confirm the result.
- Ask the member to sign in again if their previous access was restricted.
Keep company data separate
The active company comes from the verified session. Adding a company identifier to a request cannot switch its authority. Reports, course access and downloads are checked against the requesting user’s current permissions.
Team labels in the directory help people navigate. They are not a replacement for the role scopes enforced by the backend.