You must grant your team access rights to the default tenant before they can begin configuring vRealize Automation.

The default tenant is automatically created when you configure single sign-on in the installation wizard. You cannot edit the tenant details, such as the name or URL token, but you can create new local users and appoint additional tenant or IaaS administrators at any time.


  1. Log in to vRealize Automation as the administrator of the default tenant.
    1. Navigate to the vRealize Automation product interface.
      https:// vrealize-automation-FQDN/vcac
    2. Log in with the user name administrator and the password you defined for this user when you configured SSO.
  2. Select Administration > Tenants.
  3. Click the name of the default tenant, vsphere.local.
  4. Click the Local users tab.
  5. Create local user accounts for the vRealize Automation default tenant.
    Local users are tenant-specific and can only access the tenant in which you created them.
    1. Click the Add (+) icon.
    2. Enter details for the user responsible for administering your infrastructure.
    3. Click Add.
    4. Repeat this step to add one or more additional users who are responsible for configuring the default tenant.
  6. Click the Administrators tab.
  7. Assign your local users to the tenant administrator and IaaS administrator roles.
    1. Enter a username in the Tenant administrators search box and press Enter.
    2. Enter a username in the IaaS administrators search box and press Enter.
      The IaaS administrator is responsible for creating and managing your infrastructure endpoints in vRealize Automation. Only the system administrator can grant this role.
  8. Click Update.

What to do next

Provide your team with the access URL and log in information for the user accounts you created so they can begin configuring vRealize Automation.

  • Your tenant administrators configure settings such as user authentication, including configuring Directories Management for high availability. See Configuring Tenant Settings.
  • Your IaaS administrators prepare external resources for provisioning. See External Preparations for Provisioning.
  • If you configured Initial Content Creation during the installation, your configuration administrator can request the Initial Content catalog item to quickly populate a proof of concept.