Managing User Roles and Permissions
  • 12 Oct 2023
  • 3 Minutes to read
  • Dark
    Light

Managing User Roles and Permissions

  • Dark
    Light

Article summary

Secure Edge Portal users can perform sets of operations based on the role assigned to them. 

By default, two roles are available: Admin and Read Only. Table 2 lists some of the operations that define default and custom roles for performing various functions in the Secure Edge Portal.

Table 2. Roles and Associated User Operations

ComponentAdminRead Only
NetworkAdd/delete network
View/edit network
Connect/disconnect network
View network
iNodeAdd/delete iNode
Edit iNode
Collect diagnostic data
View iNode details
OrgCreate child org
Create user and roles
View org details
RoleAdd/view rolesView roles
ServiceInstall services
Delete services
View service logs
View service
UserView/edit user
Add/delete user
View list of all users

Table 3 lists the default roles and their associated permission names.

Table 3. Default Roles and Associated Permissions

Default rolePermissions
Read OnlyNODE:READ, NETWORK:READ, SERVICE:READ, ORG:READ, USER:READ, ROLE:READ
AdminNODE:ADMIN, NODE:READ, NODE:REBOOT, NETWORK:READ, NETWORK:ADMIN, NETWORK:CONNECT_DISCONNECT, NETWORK:DIAGNOSTIC, SERVICE:ADMIN, SERVICE:READ, ORG:ADMIN, ORG:READ, USER:ADMIN, USER:READ, ROLE:ADMIN, ROLE:READ, PKI:ADMIN, EVENT:DOWNLOAD, EVENT:VIEW, ACTIVITY:DOWNLOAD, ACTIVITY:VIEW

Table 4 lists and describes all the available permissions. On the Roles page, in the Permissions field,
you can hover over a permission name to display a description of its access level(s).

Table 4. Available Permissions

PermissionDescription
NODE:READAllows read access to all clusters, nodes, networks, services, service template, profiles (config template), techdump, ssh public keys, PKI, iNode and service statistics view, iNode upgrade history and container image under the respective namespace, node cli, monitoring, and duplicate address detection (DAD).
NODE:ADMINAllows administrator access to all nodes, networks, services, service template, profiles (config template), techdump, iNode upgrade history and container image, and iNode and service statistics view.
Also allows read access to PKI under the respective namespace, cluster management, node cli, monitoring, DAD, and representation network automation.
NODE:REBOOTAllows reboot and iNode service statistics view access to all nodes under the respective namespace.
NETWORK:READAllows read access to all networks and vinet under the respective namespace.
NETWORK:ADMINAllows administrator access to all networks and vinet under the respective namespace.
NETWORK:CONNECT_DISCONNECTAllows connect and disconnect access to all networks under the respective namespace.
NETWORK:DIAGNOSTICAllows read access to all nodes’ techdump under the respective namespace.
SERVICE:READAllows read access to all services and secrets under the respective namespace.
SERVICE:ADMINAllows administrator access to all services and secrets under the respective namespace.
ORG:READAllows read access to organization, user, role, ssh public keys, and permission(s).
ORG:ADMINAllows access to the following functions: create a new organization, user, and role; create/update organization policy, reset twofactor authentication (2FA), initiate verify email, assign certificates to organization under the respective namespace, manage public keys, manage ssh access on iNodes and administrator access to apikey, access events at organization and node level, and access notification channels.
USER:READAllows read access to users’ roles under the respective namespace.
USER:ADMINAllows administrator access to users and roles, initiate verify user email, and create/get apikey under the respective namespace.
ROLE:READAllows read access to roles under the respective namespace.
ROLE:ADMINAllows administrator access to roles under the respective namespace.
PKI:ADMINAllows administrator access to PKI (public key
infrastructure).
EVENT:DOWNLOADAllows access to download event logs.
EVENT:VIEWAllows access to view organization and node
level events.
ACTIVITY:DOWNLOADAllows access to download activity logs.
ACTIVITY:VIEWAllows access to view activity logs

Creating User-defined Roles

To create user-defined roles, follow these steps:

  1. Login to Secure Edge Portal with an Admin user role.
  2. From the left menu, select Users > All Roles.
  3. In the top right, select the plus sign icon (+) to add a new role.
  4. Enter the Role name, a Description, and select the Permissions from the list.
    Add Role window that has fields for Role Name, Description, and Permissions
  5. Click + Add Role.

Assigning a User-defined Role

To assign a user-defined role, you create a user account for the user and map a role to that user. Follow these steps:

  1. To add a user, at the top of the Orchestrator left menu select the plus sign icon (+) > Add User.
  2. Enter the user details and select the role to assign this user.
    Window for a new user with fields for: Full Name, Email Address, Password and Confirm Password, Role, and Time Zone
  3. Click Add User.
  4. To confirm the role has the permissions you intended, log in as the user and confirm the appropriate operations are available.

Viewing/Editing Roles

The administrator can view the list of roles and view/edit the permissions applied to a role. Default roles cannot be edited.

  1. On the Orchestrator left menu, select Users > All Roles to view the current roles and their set permissions.
  2. On the Roles page, in the left column, click the + to expand the current permissions for a specific role. Or click the role name to view its description and permissions.
    Example role line item for PKIADMIN role that shows its associated permissions
  3. To view or edit the role, click the View/Edit icons on the menu (vertical dots) to the far right.
  4. Modify the desired fields. You can hover over a permission to display a short description.
    Edit Role window showing how you can modify the permissions (items) for the example PKIADMIN role
  5. Click Update.

Was this article helpful?

What's Next