Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Service-Based Roles in Cloud Services Platform (CSP) (79275)

Last Updated: 5/13/2022Categories: How toTotal Views: 4753Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Details

This resource focuses on the service-based roles that are available within the Cloud Services Platform (CSP).

For information on the main types of roles available within CSP (Organization Level Roles and Function-Based Roles), please refer to Roles available in Cloud Services Platform (CSP) (2151069).

For details on how to invite users to an Org in CSP, please view How to invite users to the Org in CSP (79240).

Solution

Each VMware Cloud Service account within the Cloud Services Platform (CSP) is contained within an Organization (Org). Orgs are used to provide controlled access to one or more services. A user must belong to an Org before they can access a particular cloud service.

There are multiple service-based roles for each service subscribed . Below are the list of the roles that are currently available:

VMC on AWS supports three types of user roles:

Administrator: This role has full cloud administrator rights to all service features in the VMware Cloud on AWS console.

Administrator (Delete Restricted): This role has full cloud administrator rights to all service features in the VMware Cloud on AWS console but cannot delete SDDCs or clusters.

NSX Cloud Auditor: When combined with an Administrator or Administrator (Delete Restricted) role, this role can view NSX service settings and events but cannot make any changes to the service.

NSX Cloud Admin: When combined with an Administrator or Administrator (Delete Restricted) role, this role can perform all tasks related to deployment and administration of the NSX service.

vRealize Network Insight Cloud supports three types of user roles for a user. Users can access vRealize Network Insight Cloud features based on the assigned roles.

Administrator: An administrator has complete access.

Member: A member user has limited access.

Auditor: An auditor has read-only access, and restricted from all create, add, edit, or delete actions. Users can only view the state.

vRealize Log Insight Cloud supports three types of user roles for a user. Users can access vRealize Log Insight Cloud features based on the assigned roles.

vRealize Log Insight Cloud Administrator: This role has all permissions present except organization owner permissions.

vRealize Log Insight Cloud User: Permissions associated with this role include creating and modifying private dashboards and read access for other information.

vRealize Custom Role: Custom roles can also be given in vRealize Log Insight. More details can be found here.

Users can access vRealize Log Insight Cloud features based on the assigned roles.

Skyline Advisor supports two types of user roles.

Skyline Administrator: Individuals with this role can:

Add a Skyline Collector to the Cloud Services Organization.

De-register an Inactive Skyline Collector from the Cloud Services Organization.

Receive email notification when the Skyline Collector root password is about to expire.

Opt-In or Opt-Out to sharing data relating to Dell Solutions (Dell EMC Support Assist for Enterprise).

Skyline User: A Skyline User cannot complete any of the actions listed within the Skyline Administrator service role.

Explicitly, a Skyline User cannot:

Add a Skyline Collector to the Cloud Services Organization.

Deregister an Inactive Skyline Collector from the Cloud Services Organization.

Receive email notification when the Skyline Collector root Password is about to expire.

Opt-In or Opt-Out to sharing data relating to Dell Solutions (Dell EMC Support Assist for Enterprise).

vRealize Operations Cloud provides two predefined roles- the General User role and the Administrator role. These two roles are assigned to the user by the organization owner from VMware Cloud Services portal.

Each predefined role includes a set of privileges for users to perform.

Administrator: This role includes privileges to manage the vRealize Operations Cloud instance and its objects. The Administrator can also customize the privileges associated with the General User role.

General User: These predefined template roles are initially defined as Read Only roles. vCenter Server administrators can configure these roles to create combinations of roles to give users multiple types of privileges. Roles are synchronized to vCenter Server once during registration.

Cloud Assembly service roles determine what you can see and do in Cloud Assembly. These service roles are defined in the console by an organization owner.

Cloud Assembly Administrator: This role must have read and write access to the entire user interface and API resources. This is the only user role that can see and do everything, including add cloud accounts, create new projects, and assign a project administrator.

Cloud Assembly User: A user who does not have the Cloud Assembly Administrator role. In a Cloud Assembly project, the administrator adds users to projects as project members. The administrator can also add a project administrator.

The permission for these two roles is defined below:

Project administrators leverage the infrastructure that is created by the service administrator to ensure that their project members have the resources they need for their development work.

Project members work within their projects to design and deploy blueprints.

Project viewers are restricted to read-only access, except in a few cases where they can do non-destructive things like download blueprints.

Cloud Assembly Viewer: A user who can see information but cannot create, update, or delete values. This is a read-only role. Users with the viewer role can see the blueprints and deployments for all projects regardless of project membership or whether the project deployments are shared.

Cloud Assembly service roles and project roles details can be found here

Code Stream roles

Depending on the individual role in Code Stream, users can perform certain actions and access certain areas. For example, one role might allow you to create, update, and run pipelines. Another role might only have permission to view pipelines.

Administrator role: As an administrator, users can create integration endpoints, triggers, new pipelines, and dashboards.

Projects allow pipelines to access infrastructure resources. Administrators create projects so that users can group pipelines, endpoints, and dashboards together. Users then select the project in their pipelines. Each project includes an administrator and users with assigned roles. With the Administrator role, users can mark endpoints and variables as restricted resources in a pipeline, and they can run pipelines that use restricted resources. A restricted endpoint or variable that a pipeline uses requires an approval to keep the pipeline running. Otherwise, the pipeline stops at the task where the restricted variable is used until approval is granted, at which point an administrator must resume the pipeline to run. When a pipeline task includes a restricted resource, the task in the pipeline displays an icon that indicates the resource is restricted. As an administrator, users can also request that pipelines be published in VMware Service Broker.

User role: Users can access Code Stream, but do not have any privileges as the other roles provide.

Viewer role: Users can see pipelines, endpoints, pipeline executions, and dashboards, but they cannot create, update, or delete them.

Service Broker roles

User Roles: User roles are defined for the organization in the vRealize Automation Cloud console. There are two types of roles, organization roles and service roles.

The organization roles are global and apply to all services in the organization. A user is assigned an Organization owner or Organization Member role. The Service Broker service roles, which are service-specific permissions, are also assigned at the organization level in the console.

Service Broker Service Roles: The Service Broker service roles determine what you can see and do in Service Broker. These service roles are defined in the console by an organization owner.

More details on the Service roles and project roles can be found here.

VMware Learning Platform roles

When a tenant admin creates an account, the account owner is assigned one or more roles in VMware Learning Platform. Each role has a different set of permissions for accessing user interfaces.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
[解決済み] AAPP-9610：Workspace ONE UEM の [デバイス リスト表示] または [詳細表示] から iOS デバイスを削除しても、企業情報ワイプ コマンドが生成されないことがある (78765)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workspace ONE

VMware Cloud Services Platform

VMware Cloud on AWS

Related Versions:

Take Our Survey

Support Assistant