Preview · policy draft

Super Admin · Governance

Roles & permissions

Define the boundaries between platform operators, customer administrators and end users. This is the proposed policy blueprint, not enforced access control.

← Control Centre
Policy draft, not security enforcement. This matrix documents intended access. Hiding links in the interface does not secure data. The backend must enforce every permission and organisation boundary before production.
01
Least privilege

Give each role only the access needed for its work.

02
Scope matters

Permissions apply only within assigned platform, customer, site or department scope.

03
Audit sensitive changes

Record who changed access, what changed and when.

Proposed role access matrix

Use search and filters to explore the draft policy.

DESIGN DRAFT
CapabilitySuper AdminProvider AdminResellerOrganisation AdminSite AdminDepartment ManagerStandard User
Platform-wide configurationGlobal controlNo accessNo accessNo accessNo accessNo accessNo access
Feature flags & emergency controlsGlobal controlViewNo accessNo accessNo accessNo accessNo access
Tenant / organisation lifecycleFullManageScoped manageViewNo accessNo accessNo access
Users & groupsFullManageScoped manageManageScoped manageScoped manageOwn records
Printers & devicesFullManageScoped manageManageScoped manageViewView
Print activity & job detailFullManageViewManageScoped manageViewOwn records
Reports & cost analysisFullManageViewManageScoped manageViewOwn records
Billing & subscription plansGlobal controlManageScoped manageViewNo accessNo accessNo access
Organisation settingsFullScoped manageScoped manageManageViewNo accessNo access
Audit logs & security eventsFullViewNo accessViewNo accessNo accessNo access
Personal settings & own recordsFullOwn recordsOwn recordsOwn recordsOwn recordsOwn recordsOwn records
Showing all proposed capabilities.

Scope rules to enforce

  • Every customer-owned record must carry a tenant or organisation identifier.
  • Site and department roles must be limited to explicitly assigned sites or departments.
  • Standard users must not read another user's print jobs, usage or personal settings.
  • Super Admin actions must be authenticated, authorised and written to an audit trail.
  • Feature availability and role permission are separate checks; both must pass.

Decisions still to confirm

  • Can Provider Admins create or suspend reseller accounts?
  • Can Organisation Admins see detailed print-job content or only metadata?
  • Should department managers see costs, user names, or only totals?
  • Which roles can manage billing, quotas, print release and retention policies?

The matrix is a starting proposal. We will refine it before backend authorization is implemented.