7.2

About the Default Tenant
When the system administrator congures an Active Directory link using Directories management during
the installation of vRealize Automation, a default tenant is created with the built-in system administrator
account to log in to the vRealize Automation console. The system administrator can then congure the
default tenant and create additional tenants.
The default tenant supports all of the functions described in Tenant Conguration. In the default tenant, the
system administrator can also manage system-wide conguration, including global system defaults for
branding and notications, and monitor system logs.
User and Group Management
All user authentication is handled by Active Directory links that are congured through Directories
Management. Each tenant has one or more Active Directory links that provide authentication on a user or
group level.
The system administrator performs the initial conguration of single sign-on and basic tenant setup,
including designating at least one Active Directory link and a tenant administrator for each tenant.
Thereafter, a tenant administrator can congure additional Active Directory links and assign roles to users
or groups as needed.
Tenant administrators can also create custom groups within their own tenants and add users and groups to
those groups. Custom groups can be assigned roles or designated as the approvers in an approval policy.
Tenant administrators can also create business groups within their tenants. A business group is a set of
users, often corresponding to a line of business, department or other organizational unit, that can be
associated with a set of catalog services and infrastructure resources. Users and custom groups can be added
to business groups.
Comparison of Single-Tenant and Multitenant Deployments
vRealize Automation supports deployments with either a single tenant or multiple tenants. The
conguration can vary depending on how many tenants are in your deployment.
System-wide conguration is always performed in the default tenant and can apply to one or more tenants.
For example, system-wide conguration might specify defaults for branding and notication providers.
Infrastructure conguration, including the infrastructure sources that are available for provisioning, can be
congured in any tenant and is shared among all tenants. You divide your infrastructure resources, such as
cloud or virtual compute resources, into fabric groups and assign an administrator to manage those
resources as the fabric administrator. Fabric administrators can allocate resources in their fabric group to
business groups by creating reservations.
Single-Tenant Deployment
In a single-tenant deployment, all conguration can occur in the default tenant. Tenant administrators can
manage users and groups, congure tenant-specic branding, notications, business policies, and catalog
oerings.
All users log in to the vRealize Automation console at the same URL, but the features available to them are
determined by their roles.
Foundations and Concepts
VMware, Inc. 13