Roles and Permissions - Zylon

Upcoming release — Zylon 1.58These docs are published ahead of release so you can prepare your API integrations. The release image is not yet available. For installations running 1.57, use the 1.57 documentation.

Overview

Backoffice access is role-based. What a user can see and do depends on:

The account role assigned in Backoffice.
The gateway role assigned inside each gateway.

A single account can have more than one role.

Account roles

Account roles define platform-level access.

Account role	What this role does	Backoffice access
Super Admin	Initial administrative account for platform setup and governance	Same platform access as Operator
Operator	Manages accounts, roles, gateways, and platform operations	Full Platform Backoffice access
Developer	Works with gateways and API tokens for development	Access to Developer Console
Workspace	Uses Workspace for projects and collaboration	No Platform Backoffice access

Gateway roles

Gateway roles define what a user can do inside a specific gateway.

Gateway role	What this role does
Owner	Manages gateway users and roles, creates and manages tokens
Admin	Manages gateway users, creates and manages tokens
Member	Creates and manages own tokens

How access works in practice

Account role controls which Backoffice sections are available.
Gateway role controls actions inside each gateway.
An Operator who enters gateway workflows uses the same gateway-role permissions as any other gateway user.
Permissions are always scoped to the current role and context.