Application Services and vRealize Automation share tenants and business groups. A tenant is an organizational unit in a vRealize Automation deployment. A business group belongs to a tenant and associates a set of services and resources with a set of users.

An Application Services appliance is registered to a vRealize Automation deployment, also called an instance, and to a tenant in that instance. An Application Services system administrator can register the appliance to different tenants, but only one at a time.

A tenant has multiple business groups. Each business group within a tenant has members and objects such as applications, services, and external services. Users can be members of multiple business groups and multiple tenants. Every object is owned by a business group. Only users who belong to the business group can edit the objects in that group.

Applications, services, and other objects in Application Services are private or shared. Only users who are members of a particular business group can view or edit private objects in that group. All users in all business groups within a tenant can view shared objects.

As part of their function, user roles determine which objects users can create. For example, a user assigned the application architect role can create an application, among other objects. When creating the application, the user assigns the business group and specifies whether the application is private or shared. Thereafter, only members of the owning business group can edit the application. If the application is private, only members of the owning business group can view it. If the application is shared, all members of all business groups in the tenant can view the application. Regardless of whether the application is private or shared, only members of the owning business group can edit the application.

The different levels of sharing determine what you can do with the components within the blueprint, and with the application itself. As the logged-in user who constructs the application blueprint, you must belong to the owning business group of the application to edit the blueprint. Logical templates, services, external services, tasks, artifacts, and artifact repositories all belong to business groups and can be private or shared. If you select shared blueprint components that belong to a different business group, you can view those components but you cannot alter them. Only when you belong to the owning business group of a component can you change the component. When you share an application, all of the components in the application blueprint such as logical templates, services, and external services must be explicitly shared.