Skip to Content
HeadGym
User GuideMars AdminAccess Control
Tags:#access-control#users#roles#permissions#rbac

Access Control

The Access Control module manages users, roles, and permissions within the MAR platform.

Overview

The Access Control page provides three tabs for managing access:

  1. Users - Manage user accounts and their status
  2. Roles - Define roles and their permissions
  3. Role Bindings - Assign roles to users for specific scopes

Users Tab

User Properties

PropertyDescription
NameUser’s display name
EmailUser’s email address (also used for login)
RoleAssigned role
StatusAccount status (active, inactive, pending)
Last ActiveTime since last login
ProjectsProjects the user has access to

User Statuses

  • Active - User can log in and access resources
  • Inactive - User account is disabled
  • Pending - User has been invited but hasn’t accepted

Inviting Users

  1. Click the Invite User button
  2. Enter the user’s name (optional) and email
  3. Select a role for the user
  4. Click “Send Invite”

Managing Users

  • View - See user details
  • Edit - Modify user properties
  • Delete - Remove user from the system

Roles Tab

Role Properties

PropertyDescription
NameRole identifier
DescriptionBrief description of the role
ScopeLevel of access (org or project)
PermissionsList of permissions granted
UsersNumber of users with this role

Role Scope

  • Organization (org) - Role applies to the entire organization
  • Project - Role applies to specific projects only

Available Permissions

Permissions are organized by resource type:

CategoryPermissions
Clustersclusters:read, clusters:create, clusters:update, clusters:delete
Instancesinstances:read, instances:create, instances:update, instances:delete, instances:start, instances:stop, instances:restart
Config Profilesconfig-profiles:read, config-profiles:create, config-profiles:update, config-profiles:delete
Monitoringmonitoring:read, monitoring:write
Alertsalerts:read, alerts:create, alerts:update, alerts:delete
Webhookswebhooks:read, webhooks:create, webhooks:update, webhooks:delete
Access Controlaccess:read, access:manage

Creating Roles

  1. Click the New Role button
  2. Enter role name and description
  3. Select scope (org or project)
  4. Choose permissions for the role
  5. Click “Create Role”

Built-in Roles

The platform includes several default roles:

  • Platform Admin - Full access to all resources and settings (org scope)
  • Operator - Manage clusters, instances, and configurations (project scope)
  • Developer - View resources and manage deployments (project scope)
  • Viewer - Read-only access to resources (project scope)

Role Bindings Tab

Role bindings connect users to roles at specific scopes.

Binding Properties

PropertyDescription
UserThe user assigned the role
RoleThe role being assigned
ScopeThe scope (org:organization or project:project)
Granted AtWhen the binding was created
Granted ByWho created the binding

Managing Bindings

  • View which roles are assigned to which users
  • Delete bindings to remove role assignments
  • Track who granted access and when
Last updated on