Manage organizations, users, and roles on CloudBolt Documentation

Manage organizations

Mon, 01 Jan 0001 00:00:00 +0000

The CloudBolt Platform organizes access into a hierarchy of organizations, each with its own users, roles, and data access boundaries. Use sub-organizations to reflect your internal structure or, for managed service providers and resellers, the individual customers you manage.

When you sign up, CloudBolt automatically creates an organization for your company, and you’re granted the Admin role as the first user so you can add teammates and assign roles.

Prerequisites

Viewing and managing organizations requires access to a CloudBolt Platform user account with the Admin role.

Organization context

The CloudBolt Platform allows you to navigate between organizations of which you are a member. Each organization represents a separate working environment, or context, with its own data and users.

Manage users

Mon, 01 Jan 0001 00:00:00 +0000

To view the user list, change a user’s role, or remove a user, see User Management.

Prerequisites

Adding a user requires access to a CloudBolt Platform user account with the Owner permission.
Accepting an invitation requires access to the user’s email account.

Select an organization

To select a CloudBolt Platform organization:

Log in to the CloudBolt Platform as a user with the Owner permission. The address depends on where your organization’s tenant is hosted; see Sign in.
In the sidebar, select Switch Organization.
Choose the organization to make active.

For details, see Switch Organization.

Manage roles

Mon, 01 Jan 0001 00:00:00 +0000

The CloudBolt Platform provides a role-based access control (RBAC) model to manage user privileges within each organization. Roles determine available components and actions, enabling fine-grained control across cloud cost, operations, and user management workflows. Users can have different roles in different organizations, but only one role per organization.

Permissions

Roles in the CloudBolt Platform consist of permissions that define the allowed actions. Permissions are granted at three hierarchical levels:

Level	Description
Owner	Full access: create, read, update, and delete resources.
Editor	Read and update access: cannot create or delete resources.
Viewer	Read-only access to resources.

Permissions are not assigned directly to users. Users receive permissions through assigned roles.

Roles and permissions

Mon, 01 Jan 0001 00:00:00 +0000

Every user has one of four roles: Admin, Operations, Practitioner, or Stakeholder. Roles are assigned when a user is invited and can be changed later from User Management. For a description of what each role means, see Manage roles.

Most pages in the platform are open to any authenticated member of your organization, regardless of role. A smaller set of administrative pages require a specific permission level on top of your role.