Skip to main content

β›­ Nobl9 features

RBAC​

β›­ Project SLOs aren't visible for all users in an organization​

The default role for all new users in Nobl9 is Organization User (unless a different default role has been set for your organization). This means that if you create a new project as an Organization Admin, users who reside in your organization will not see the project in their project list (Catalog > Projects), or any SLOs related to this project.

Read more about Role-based access control.

β›­ Granting access to projects​

There are two methods to give users access to the project, and all the resources that are related to it:

  • On the organization level: change the organization roles of the users to Organization Viewer. This way, they will be able to see all projects (and their related resources) within your organization. Keep in mind that Organization Viewers can’t create new projects.
  • On the project level: when you create a project, add the project to the relevant users from the Settings panel (Settings > Users) and assign appropriate project roles to them.

β›­ Organization-level RoleBinding: user's name field configuration in sloctl​

The name is a string that must meet the following requirements:

  • Contain only lowercase alphanumeric characters: a-z, 0-9 and dashes -
  • Start and end with an alphanumeric character and include up to 63 characters
  • Be unique within an organization (for the Organization roles) or within a project (for the Project roles)

Additional considerations for the name field:

  • When you create a RoleBinding manually with sloctl, you can use any valid string for name
  • A RoleBinding created with sloctl can be edited in the Nobl9 UI.
    For example, you create project-owner-adam. Then, this object is available in Settings > Users.
  • When you configure a role in the UI first, it will generate a UUID for name. Then, get the RoleBinding through sloctl.

Read more about role binding and naming.

β›­ A default role for newly created users​

By default, new users are assigned the Organization User role.
Admin users can change the default organizational role in the Nobl9 UI.
For this, do the following:

  1. Go to Settings > Users.
  2. Click Configure Default Role. Select the required role: User or Viewer.

As a result, this setting is applied to every newly added user when they log in to the app for the first time. It doesn't impact user roles who logged in before you changed the default role.

β›­ Project-level default role​

It's not possible to set a default user role on the project level. The default roles can be managed only on the organization level.

Reports​

β›­ N/A values in a report​

N/A values in reports mean there is no data for the current time window.

Annotations​

β›­ Creating annotations through API or inbound webhook​

You can create annotations via an API call.
Read more about API endpoints for SLO annotations.

Data export​

β›­ Data export support during a POC or Nobl9 Free​

Data export is supported only for enterprise customers.