Docs

Permissions

Permission model

MyLink Portal uses a role-based access control (RBAC) model.

Permissions are granted through roles assigned to users within a specific service account.

Access is determined by the relationship between:

User
↓
Role
↓
Service Account

Roles define which actions a user can perform within that account.

Example:

This ensures secure and granular control of account resources.

Account-level permissions

Permissions are assigned per account.

This means a user can have different roles across accounts.

Example:

This allows organizations to provide granular access control across teams.

Default permissions

When the feature is first enabled:

  • All existing users keep Admin permissions

  • Permissions only change if an Admin modifies them manually

This ensures no disruption to existing workflows.

User roles

Each user can have different roles depending on the account they access.

Available roles:

PermissionCapabilities
ViewRead-only access
AdminFull access to configuration

Admins can:

  • Create and manage users

  • Assign roles

  • Manage product configurations

  • Modify credentials and settings

Viewers can:

  • View dashboards

  • Search message logs

  • View product configuration

But cannot:

  • Create users

  • Modify settings

  • manage credentials

These permissions are enforced through the platform authorization model.

Change permissions for an existing user

Admins can change permissions after a user has been created.

Steps:

  1. Go to Configuration → Users and Accounts

  2. Select the user

  3. Click Manage permissions

  4. Assign roles per account

Permissions can be edited:

  • Per account

  • For multiple users at once

Bulk editing allows admins to update permissions efficiently across several accounts.