# Configuring Access with Clouds, Groups, and Roles

As you get started, it’s vital to understand constructs such as Clouds and Groups as they are implemented in HPE Morpheus Enterprise. Deploying an effective strategy for dividing organizational resources and people groups under these constructs will ensure all parties have convenient access to the resources they need. Map currently-existing strategies for splitting resources and controlling costs into HPE Morpheus Enterprise and your teams will have access only to resources allocated to their department.

This guide discusses the constructs of Clouds, Groups, Roles, Users, and Policies while also presenting an example use case for allocating resources and distributing access under these umbrellas. We’ll end up with a permissions structure represented by the diagram below and step through each part of the implementation process.

![../../_images/0permsDiagram.png](https://support.hpe.com/hpesc/public/api/document/sd00008014en_us/GUID-DAC903C8-75F8-45F5-8C24-8217DDD1758F-high.png)

## Clouds

Clouds have broad meaning in HPE Morpheus Enterprise and can be integrations into public clouds, private clouds, or bare metal servers. You can read more about Clouds in HPE Morpheus Enterprise Docs [here](https://docs.morpheusdata.com/en/latest/infrastructure/clouds/clouds.html).

In our example case, the organization has an Azure account and three separate departmental projects consolidated under separate resource groups. The HPE Morpheus Enterprise integration with Azure public cloud allows users to scope the Cloud to one specific resource group, if desired. We will do so in this case because it will allow us to restrict our users to the appropriate Azure resource groups in a later step. In the screenshot below, note how I am scoping the HPE Morpheus Enterprise Azure Cloud to a specific resource group when adding or editing the Cloud. This process will be repeated two additional times to create the three HPE Morpheus Enterprise Clouds we need. Complete details on integrating HPE Morpheus Enterprise with Azure public cloud are [here](https://docs.morpheusdata.com/en/latest/integration_guides/Clouds/azure/azure.html) in HPE Morpheus Enterprise Docs.

![../../_images/1configCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00008014en_us/GUID-04D720D8-D7A9-44B8-8585-DBDEDD802C3D-high.png)

## Groups

[Groups](https://docs.morpheusdata.com/en/latest/infrastructure/groups/groups.html) in HPE Morpheus Enterprise allow administrators to determine which Clouds their users have access to. Part of defining a Role, which we’ll see in the next section, is selecting which Groups are associated with the Role. One or multiple Clouds are added to each Group and passed to users through their assigned Roles.

When creating a Cloud, it must be added to a Group. Additionally, Clouds can be added to a Group at any time from the Clouds tab on the Group detail page (Infrastructure > Groups > Specific Group). In the example case diagrammed above, one Cloud (Azure cloud account scoped to a specific resource group) is associated with each Group but often Groups will contain many Clouds. In the screenshot below, I am adding an Azure Cloud to a Group that is currently empty.

![../../_images/2addCloudToGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00008014en_us/GUID-0AB9B625-EF46-4CA2-B797-B86D533F52B4-high.png)

## Roles

HPE Morpheus Enterprise Roles determine user access to many things, including application features, Groups, configured Instance Types, configured Blueprints, Personas, and Catalog Item configurations for the Service Catalog Persona. It’s important to note that a user can have multiple Roles and will take the most permissive rights across all of these Roles. In many cases, this greatly simplifies Role configuration for administrators as it prevents the need to create highly-specific individual Roles that can suit every case. To illustrate this for our example case, I will create a set of Roles to handle Group access for my users and another set of Roles to give access to the correct feature permissions.

For this example case, I’ll start by creating one Role for each of the three Groups we created in the previous step. By default, a new Role will have all feature permissions set to “None” as shown below meaning we can skip directly to the Group Access tab.

![../../_images/3roleFeatureAccess.png](https://support.hpe.com/hpesc/public/api/document/sd00008014en_us/GUID-E0F14807-7823-4651-8193-7E2F04ADC12E-high.png)

On the Group Access tab, I will toggle the Global Access setting to Custom and give access only to one Group as shown in the next image. By doing this for each of our Groups created in the last section, we can easily control Group access for each user by applying one or more of our Group Roles to their user which we will do in the next section.

![../../_images/4roleGroupAccess.png](https://support.hpe.com/hpesc/public/api/document/sd00008014en_us/GUID-1F85B206-FDB4-478F-BCEC-96E7184EF31F-high.png)

In addition to Roles for handling Group access, we need additional Role sets which will control our feature access. For example, we might have highly permissive feature access for administrators and more restrictive ones for developers or other users who have specific responsibilities requiring access to just a few specific areas of the UI. These additional Roles are created in the same way as the Group Roles we just created but all Group access will be set to “None” and the appropriate feature access will be configured on the “Feature Access” tab.

## Users

With the groundwork laid in the previous steps, we can easily configure permissions for any user accounts we might add to HPE Morpheus Enterprise. In the screenshot below, I’m adding a user account for a developer at my organization. I’ve applied one Role to handle correct Group access for this user and I’ve applied the “Developer” role to give only the feature access needed for this user to carry out his or her responsibilities.

![../../_images/5newUser.png](https://support.hpe.com/hpesc/public/api/document/sd00008014en_us/GUID-295DFC03-0A0D-4350-B2DB-30692FE51851-high.png)

## Policies

One final consideration for this example case is policy application. HPE Morpheus Enterprise enables administrators to place fine-grained governance scoped to specific users, Roles, Groups, Clouds, Tenants, or globally. You can read more about policies in HPE Morpheus Enterprise docs [here](https://docs.morpheusdata.com/en/latest/administration/policies/policies.html) but we will also create some that apply to the example case discussed in this guide.

Policies are created from the Administration menu in the Policies section. In the screenshot below, I’ve created a new policy and chosen to scope it to a Group. In this case, I’m creating a maximum VMs policy but there are many other types which are listed in our documentation linked above.

![../../_images/6policies.png](https://support.hpe.com/hpesc/public/api/document/sd00008014en_us/GUID-21C24B9B-7C14-48A8-AB21-9D31F5DF44DC-high.png)

## Conclusion

At this point, we’ve completed implementation of the access structure. As new users are added, we can easily give them the Group and feature access they need. We can also easily add or edit the policies that are in place or add new Clouds and distribute access to existing users. The key is understanding the relationship between the HPE Morpheus Enterprise constructs discussed in this guide. Armed with that understanding, the example case presented here can be expanded to suit the needs of large-scale enterprise.
