Skip to main content

Switching Organizations

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

As a part of this feature, Nobl9 offers the ability to toggle between organizations easily and securely.

For example, Nobl9 users can leverage this feature to switch between their production and sandbox organizations to experiment with the Nobl9 Platform and their SLOs in a safe environment that doesn’t disrupt their production environment and SLOs.

Create New Organization

You can request to create a new non-production organization:

Manage Your Organizations

You can easily identify the organization you’re currently in by checking the label in the top-right corner of your screen, next to your user’s icon:

org switcher prompt
Image 1: Organization label

You can switch between different organizations you’re assigned to in the UI or via sloctl.

Switch Organizations in the UI

To switch organizations in the UI:

  1. Click your user icon at the top-right corner of the screen.

  2. In the drop-down menu, click the organization's name with a caret icon next to it:

    org switcher caret
    Image 2: Organization switcher
  3. Choose the organization you’d like to switch to and click it.


You can also switch organizations using deep links.

Switch Organizations in sloctl

You can easily switch through organizations by using sloctl config commands. For more details, refer to sloctl user guide.


Use the sloctl config add-context command to add a new organization context to sloctl.

For example, to preview available organizations, use the sloctl config get-contexts -v command, which will produce the following output:

All available contexts: [production, sandbox]

Context: production
ClientID: # secret
ClientSecret: # secret
Project: default
Organization: production

Context: sandbox
ClientID: # secret
ClientSecret: # secret
Project: default
Organization: sandbox

Invite Users to an Organization

Organization Admins can invite users to an organization in two steps:

  1. Step 1:
    Switch to a specific organization to which you want to invite user(s).
  2. Step 2:
    Fill in the New User form in the Settings > Users panel:
new user form
Image 3: New User form

Invitation Emails

Invited users will receive the following email from Nobl9:

invitation email
Image 4: Invitation email from Nobl9

When a user clicks the button link visible in the email, they can either:

  • Manually switch to the new organization by clicking on their screen’s user icon in the top-right corner of the app:
org switcher
Image 5: Switching organization
  • Or accept a prompt from the Nobl9 Platform to change their current organization:
org switcher prompt
Image 6: Switch organizations prompt

After completing one of the above steps, users can leverage resources within the selected organization per the assigned role.

Switching Organizations - Rules at Glance

The ID of the current organization is stored in the URL that you can check in your browser’s address bar. The following link shows an example of a deep link to the main page of the Service Health Dashboard in the production organization:

Consequently, deep links can only be shared between users within the same organization. Thus, resources can be shared via deep links only within one organization.

If you share a deep link to a resource with another user outside of the organization this resource resides in, they won’t be able to access it.

Deep links also allow you to switch organizations:

For instance, using the link above, you can replace the production string ID with the sandbox string ID to switch to the sandbox organization:

Suppose (1) you type in the ID of an organization that doesn’t exist, for instance, foo-bar (, or (2) switch through this method to an existing organization to which you’re not assigned. In that case, you’ll be automatically redirected to a “Need permission” screen and a Switch organization modal:

need permission
Image 7: Need permission page

Restrictions for Switching Organizations

Remember that the following restrictions apply for switching organizations:

  • Organization Admins can’t set a default organization.

  • You can’t migrate SLOs between organizations and retain their historical data.