<< Click to Display Table of Contents >> Navigation:  Manage platform users and authentication > Manage users for Enterprise subscriptions > Cloud services users and roles

Overview

In the Customer Portal, you can manage users of all the Bizagi cloud platform services. Therefore, there are different roles to manage users across the wrkspaces of each service. This article describes the type of roles available in the Customer Portal.

 

One company can purchase a subscription of each service offered in our cloud-based platform. For example, one company can have a subscription of Automation Service, and one subscription of Studio Cloud Services.  Each service has a type of workspace. The following table shows the subscriptions and workspace available:

 

 

Bizagi's Customer Portal controls access to workspace based on a Role Access model. Roles are distributed hierarchically among the different levels. A company has three levels:

 

•Company: Company who has access to the purchased services.

•Subscription: Services offered by Bizagi like Automation,Studio Cloud Services, Modeler

•Workspace: Each service, has a resource type where users can work on. For example, in Automation you have projects and in Modeler you have models.

 

All the users registered through the Customer Portal, are registered in a private Identity Provider, that grants access to the portals or applications of each service. See Accessing services' portals and applications.

 

Within each level, the Customer Portal offers roles as follows:

 

 

•Company Administrator: this user can create users to the company user's pool, and manage users in all the company subscriptions.

•Service subscription owner: For each service, there is an owner in the company, for example, an Automation service owner, a Studio Cloud Services owner, and a Modeler service owner. Each subscription owner can manage users under the service where is entitled as owner.

•Service subscription viewer: A user with this role can read (consult) the projects created under a subscription. They can also create new projects.

•Workspace owner: Each service has different types of workspace. For example, in Modeler services, you have models, in other services you have projects. a workspace owner is the creator of the workspace and can manage users for a specific model or project, to invite users to be part of the workspace, and define its role. For example a Project Owner in Automation Service, or a Model Owner in Modeler Services.

•Workspace contributor or editor: This is a user accessing, editing, or viewing a workspace of a subscription, for example, contributors, or project editors.

•Developer or Power user: The can access the authoring environment (Studio) to work on the automation of processes.

 

 

Based on the level, each role has a set of permissions to manage the level scope. For example, the permission a user has in the subscription level, like reading or making changes. The following section describes the set of permissions the roles have in each level:

 

Permissions at the Company Level

At the company level, the only role who can manage users at this level is the Company Administrator.

 

Permissions at the Subscription level

At the subscription level, the Subscription Owner is the only role that can manage the subscription users. The Subscription Viewer, on the other hand, can see the subscription as read-only.

 

 

The Company Administrator inherits all the permissions that the subscription owner has, at the subscription level.

 

Permissions at the Project level

Once you have a project created, roles have the following permissions:

 

Permissions are inherited for upper roles in the hierarchy. For example, the subscription owner inherits the project owner's permission, therefore, a user with the subscription owner role can share, delete, edit, read, and create projects.

 

Last Updated 7/6/2023 9:23:50 AM