7.4
Table Of Contents
- Foundations and Concepts
- Contents
- Foundations and Concepts
- Foundations and Concepts
- Using Scenarios
- Using the Goal Navigator
- Introducing vRealize Automation
- Tenancy and User Roles
- Service Catalog
- Infrastructure as a Service
- XaaS Blueprints and Resource Actions
- Common Components
- Life Cycle Extensibility
- vRealize Automation Extensibility Options
- Leveraging Existing and Future Infrastructure
- Configuring Business-Relevant Services
- Extending vRealize Automation with Event-Based Workflows
- Integrating with Third-Party Management Systems
- Adding New IT Services and Creating New Actions
- Calling vRealize Automation Services from External Applications
- Distributed Execution
- Foundations and Concepts
Table 4. Tenant Role Overview
Role Description
Tenant Administrator Typically a line-of-business administrator, business manager, or
IT administrator who is responsible for a tenant. Tenant
administrators configure vRealize Automation for the needs of
their organizations. They are responsible for user and group
management, tenant branding and notifications, and business
policies such as approvals and entitlements. They also track
resource usage by all users within the tenant and initiate
reclamation requests for virtual machines.
Fabric Administrator Manages physical machines and compute resources assigned
to their fabric groups and creates and manages the reservations
and policies associated with those resources within the scope of
their tenant. They also manage property groups, machine
prefixes, and the property dictionary that are used across all
tenants and business groups.
Note If you add the fabric administrator role to a system-wide
role such as IaaS administrator or system administrator, the
fabric administrator can create reservations for any tenant, not
just their own.
Blueprint Architects Umbrella term for the individuals who are responsible for
creating blueprint components and assembling the blueprints
that define catalog items for consumers to request from the
service catalog. These roles are typically assigned to individuals
in the IT department, such as architects or analysts.
Catalog Administrator Creates and manages catalog services and manages the
placement of catalog items into services.
Approval Administrator Defines approval policies. These policies can be applied to
catalog requests through entitlements that a tenant administrator
or business group manager manage.
Approver Any user of vRealize Automation, for example, a line manager,
finance manager, or project manager, can be designated as an
approver as part of an approval policy.
Business Group Manager Manages one or more business groups. Typically a line
manager or project manager. Business group managers
entitlements for their groups in the service catalog. They can
request and manage items on behalf of users in their groups.
Support User A role in a business group. Support users can request and
manage catalog items on behalf of other members of their
groups.
Business User Any user in the system can be a consumer of IT services. Users
can request catalog items from the service catalog and manage
their provisioned resources.
Health Consumer Any user of vRealize Automation, for example, a line manager,
finance manager, or project manager, can be designated as a
Health Consumer with read-only privileges for Health Service
reports.
Foundations and Concepts
VMware, Inc. 20