# AD Group Mapping

Before you can map Active Directory (AD) groups to roles in WorkSpaces Manager, you first need to create and validate the AD groups. You can do this by following the instructions on the [Active Directory Groups](https://admin.nuvens.cloud/security-section/active-directory-groups) Page.

Now the Groups have been validated we can now map to Roles to create WSM Role. Go to **Security** > **Roles** and click **Create Role**, enter a Name and click **Create.**

<figure><img src="https://2854239078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxEJOGCAr5O8d9q95spJy%2Fuploads%2FpDVywFyyt4bckcZxCK68%2Fimage.png?alt=media&#x26;token=2824af9a-0c53-4e3c-acc6-5644e3d57959" alt=""><figcaption></figcaption></figure>

Once the role has been created, click on it to open the configuration page. In the top-left corner, you'll see the **"AD Group Mapping"** dropdown. From there, select the **Active Directory Group** you want to associate with this role.

Next, define the permissions for the role. For example, in this case, we're assigning the WSMTest AD Group and granting users access only to the Admin and WorkSpaces tabs. This ensures users in that group have restricted, role-specific access when using WorkSpaces Manager.

<figure><img src="https://2854239078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxEJOGCAr5O8d9q95spJy%2Fuploads%2FUHIWpmB3pVXAbuj59NGy%2FScreenshot%202025-11-11%20151311.png?alt=media&#x26;token=35b3a81d-92bd-42fa-9986-aa6a76c20fa1" alt=""><figcaption></figcaption></figure>

Users who belong to the mapped Active Directory group will automatically have the assigned role applied to them in Portal Users within WorkSpaces Manager.

<figure><img src="https://2854239078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxEJOGCAr5O8d9q95spJy%2Fuploads%2FlsSNI3F7fcQNjbeUoh2L%2Fimage.png?alt=media&#x26;token=b5796469-f499-4e08-8d34-781286d1f244" alt=""><figcaption></figcaption></figure>

When users log in to the portal, they will authenticate using their Active Directory credentials (e.g., `Domain\username`). Once logged in they will only see the sections and functionality that correspond to the permissions assigned to their mapped role.

Refer to the example below to see how these role-based permissions are reflected in the user interface.

<figure><img src="https://2854239078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxEJOGCAr5O8d9q95spJy%2Fuploads%2FQwonJRh9KnvyJgJkc2t1%2Fimage.png?alt=media&#x26;token=0c4f740f-0e24-40ae-8ff1-ab8b9b16a5aa" alt=""><figcaption></figcaption></figure>
