Access control in Nobl9

Reading time: 0 minute(s) (0 words)

Nobl9 supports role-based access control (RBAC) to ensure granular user and system permissions and access to resources in the Nobl9 platform.

Nobl9 RBAC features two levels of permissions: organization and project.
Role management is available in Nobl9 Web and with sloctl using Role Binding.

Although the majority of operations a Nobl9 user can perform depends on their role, all users can do the following:

• Reset their passwords
  Once a user clicks Forgot password, their status sets to Recovery and goes back to Active after the user submits their new password.
• Generate user access keys to sign programmatic requests in sloctl and to Nobl9 API.

Organization admins can create and manage API keys to implement system access control without involving a user identity.

Project management

Resource visibility and available options

This section describes options available for the full permission set. Your available options depend on your Organization-level and Project-level role.

You can manage projects from the Catalog page. To get there, click Catalog in the main navigation. The Projects tab lists all projects within your organization.

Hover the cursor over the required project to edit or delete the project.

Non-empty projects

You cannot delete a project that holds at least one resource.

Deleting or editing a project

Click the required project row to open its details. The following options are available:

• Edit and delete the resource—click

  Impact on SLOs

  Deleting a service or data sources also deletes all associated SLOs.

• View details of the included resources and open their pages

• Remove labels from included resources

• Update the agent version under the Data sources tab

• View the history of project changes

• View and manage access to your project under the Users and API keys tabs

To assign a user or API key to the project, click Assign users or **Assign API keys. Select the required actors and their role in your project, then click Assign users / Assign API keys to confirm.

Assigning a user to a project

Role change overwrites the previous role's permissions

When changing a role for a user or API key, the new role permissions overwrite the previous role.

For example, when you change the role from Project editor to Project viewer, the user loses the Project Editor permissions.

To revoke an actor's access to the project, hover over the required user or API key row. Click X next to their role in the Project role column and confirm your action.

Revoking user access to a project

Self-removal

Any user, including organization admins, can remove themselves from a project. Doing so will immediately revoke your access to the project and its resources. To regain access, contact a project owner or an organization admin.

Useful links

Check out these related guides and references:

API keysAccess managementUser access keysAccess managementRole bindingAccess managementAccess tokenNobl9 APIssloctl user guideSLOs as codeOrganization rolesAccess managementProject rolesAccess management