---
title: "Multi-Tenancy"
description: ""
url: "https://docs.itrsgroup.com/docs/opsview/6.11.7/configuration/users-and-roles/multi-tenancy/index.html"
---
As described in [Overview of the Security Model](https://docs.itrsgroup.com/docs/opsview/6.11.7/configuration/users-and-roles/users-and-roles/index.html#overview-of-the-security-model), Multi-Tenancy is a great way to give a control of Opsview Monitor to your end users. It does so by allowing them to create new Hosts and further Roles and Users all within their own secure, private environment.

To use Multi-Tenancy, you must first ensure that your User's Role has the `CONFIGURETENANCIES` option checked. This option is located within the **Configuration** tab, as shown below:

![Edit Administrator section](https://docscdn.itrsgroup.com/opsview/images/config-multi-edit-admin.png)

By default, this option is disabled. Once the option is enabled, you should be able to see **Multi-Tenancy** under the **Configuration** menu.

## Adding a tenancy

To add a new tenancy, navigate to **Multi-Tenancy** within the Configuration menu and then click **Add New**.

Click on the **Add New** button which will display a window:

![New Multi-Tenancy fields](https://docscdn.itrsgroup.com/opsview/images/config-multi-new-fields.png)

In the above example, we are creating a new Tenancy based on an example **Opsview Servers** Role. This Role has access to view and modify only the hosts within the **Monitoring Servers** Host Group, and can only view Service Checks on those Hosts that are within the service group **Application - Opsview**.

Primary roles are not allowed to have any of the following accesses:

- `ADMINACCESS`
- `AUTODISCOVERY`
- `AUTOMONITOR`
- `CONFIGURETENANCIES`
- `CONFIGUREVIEW`
- `CONFIGUREKEYWORDS`
- `VIEWALL`
- `ACTIONALL`
- `TESTALL`
- `NETFLOW`
- `CONFIGURENETFLOW`
- `REPORTADMIN`
- `BSM`
- `CONFIGUREBSM`
- `CONFIGUREBSMCOMPONENT`

After clicking **Submit**, the new tenancy is added:

![Added new Tenancy](https://docscdn.itrsgroup.com/opsview/images/config-multi-submit.png)

Once the primary role and the multi-tenancy definition have been associated (**Configuration > Multi-Tenancy**), the primary role cannot be changed, although an administrator can edit the permissions for that role. Opsview will automatically ensure that all other roles in that tenancy will not have more permissions than the primary role. So when a User with the **Opsview Servers** role logs in, they can add Hosts and create Roles if the Role **Opsview Servers** allows, which are all based on the Hosts and Service Checks that the primary Role is configured to allow Users to view and edit.

## Deleting a tenancy


**Warning**


When deleting a tenancy, all associated roles and users will also be removed. Ensure you check the roles and users within the tenancy before confirming deletion.



To delete a tenancy, click the contextual menu icon and select **Delete**.

![Delete a tenancy](https://docscdn.itrsgroup.com/opsview/images/config-multi-delete.png)

To confirm deletion, select **OK**.

![Confirm deletion of a tenancy](https://docscdn.itrsgroup.com/opsview/images/config-multi-delete-confirm.png)


