Skip to main content

User management FAQ

Reading time: 0 minute(s) (0 words)
How do I grant access to my project?

Depending on the required access level:

  • Users with the Organization viewer role can view all projects in the organization.
    This role is assigned by the Organization admin
  • For granular access control, assign roles at your project level. The roles include:
  • Project owner (the only role capable of managing other accesses)
  • Project editor
  • Project integrations user
  • Project responder
  • Project viewer

Access granted at the project level is inherited by all resources this project contains. To manage project access, open your project details, open the Users tab, and click Assign users.

What are the name field requirements for role binding?

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 on the Nobl9 Web.
    For example, you create project-owner-adam. Then, this object is available in Settings > Users.
  • When you configure a role in the Nobl9 web application first, it will generate a UUID for name. Then, get the RoleBinding through sloctl.
How can I perform a bulk user import using SSO?

SSO provides access to the platform but does not support detailed user management. To assist clients, users can be created in bulk by submitting a spreadsheet or CSV file to the support team.

Can I view Nobl9 dashboards without the Nobl9 account?

No, it's not possible to view Nobl9 dashboards without an account in Nobl9.

Does Nobl9 support SCIM automation for removing user accounts when they are removed from AD groups?

Active Directory (AD) translates the "removing from group" action to user account deactivation in Nobl9, not deletion. For complete user deletion in Nobl9, a hard delete operation must occur on the identity provider side. In AD, this requires both user deletion and removal from the recycle bin.

Technical details:

  • SCIM standard does not support automatic user account deletion when a deletion event doesn't occur in the source system
  • AD controls which operations are reflected in specific calls to our API
  • For additional automation options, please consult your Azure AD documentation

Note: If your organization requires custom user lifecycle management beyond standard SCIM capabilities, contact Nobl9 Support to discuss possible solutions.

Last updated on