---
title: Multitenancy
slug: singleconnect-reference-guide-3-1-0/multitenancy
description: Learn how to enable and configure the Single Connect Multitenancy function, allowing for multiple independent applications and customization for each customer. This document includes instructions on adding tenant connectors through OpenVPN or a built-in V
docTags: 
createdAt: 2022-07-24T14:43:32.000Z
---

The Single Connect Multitenancy function can provide multiple and independent applications and functions. Single Connect Multitenancy enables an architecture in which a single instance serves multiple customers. Each customer is called a tenant. Tenants may be given the ability to customize some parts of the application. Tenants are logically isolated from each other. Tenant admins can only manage devices and users that they are allowed to access and can only see the logs related to the permitted devices and users.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/F_QpdQ0S6Z8sfLWbaPzIk_image.png" size="74" width="623" height="520" caption="Multitenancy for Single Connect" position="center" showCaption="true"}

To enable multitenancy:

1. Navigate to **Administration **> **System Config. Man.**
2. Set **multitenancy.enabled** as **true**.
3. **Save** configuration.
4. Navigate to **Portal Function** >** Function Group Definition**.
5. Give the function group a name and select the **single.connect.tenant.admin** function
6. **Save **configuration.
7. Open the **Function Realm Definition** tab.
8. Give the realm a name, select a tenant admin user group and select the function group that you created on step 6 and **Save**.
9. Restart the Netright-Tomcat service
   a.	Establish an SSH connection to the Single Connect IP address as the **pamuser** user.
   b.	Run the **systemctl restart pam-gui** command to restart the service

## Tenant Connector

The Tenant Connector provides secure remote data center connections to different tenants who want to use Single Connect’s features, such as preventing password theft and eliminating unsupervised access and need a secure connection between their remote data centers and the central Single Connect server. This section describes how the tenant connector is added and matched with devices.

To create an OpenVPN Connector:

### Adding an OpenVPN Connector

Tenants who already have an OpenVPN server in the remote data center or want to use OpenVPN in their remote data center connections can use this feature.

1. Navigate to **Tenant Connector**.
2. Open the **Connector Sites** tab.
3. Click the **Add** button, enter the remote site name and description, and click **Save**
4. Open the **Connector Nodes **tab.
5. Click the **Add** button and select the **OpenVPN** option.
6. Select the connector site, enter the OpenVPN credentials, copy the OpenVPN configuration, and click **Save**.

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/bXvVsrECEpHC43AK7z9___image.png "OpenVPN Connector Configuration Screen")

### Adding a Built-in VPN Connector

Tenants who do not have an OpenVPN license and want to use Single Connect’s secure connection can use its Built-in VPN option. In order to set this connection, the connector package must first be installed on a Linux server at the remote data center.

To install the connector node to the remote datacenter:

1. Download the connector installation package **connector\_install.tar.gz **from the Single Connect repository.
2. Extract the files to a Centos / RHEL server at the remote datacenter.
3. Execute the **install.sh **script. This script installs all the required packages and configures the connector node
4. Log in to the restricted CLI and execute the **create ssh key** command. Copy the generated SSH RSA Key.

To create a Built-In VPN Connection:

1. Navigate to **Tenant Connector**.
2. Open the **Connector Sites** tab.
3. Click the **Add **button, enter the remote site name and description, and click **Save**.
4. Open the **Connector Node** tab.
5. Click the **Add** button and select the Built-In VPN option.
6. Select the remote site name, enter the node name, tunnel port, connection port, connector node external IP, the SSH RSA Key created during the connector node installation, and click **Save**.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/OY4-8Du8aqHtzaQ7tGPd6_image.png" size="74" width="938" height="433" caption="Built-In VPN Configuration Screen" position="center" showCaption="true"}

### Connector Monitoring

Connectors send heartbeat messages to Single Connect servers at regular
intervals. This information can be used to monitor whether the connectors are
working properly.

To check the heartbeat messages:

1. Navigate to** Tenant Connector**.
2. Open the **Connector Nodes** tab.
3. Click the **List view** button, select the connector node, and click the **Heartbeat** button.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/3L_jtJgyPYVKgEFJH1XES_image.png" size="74" width="783" height="355" caption="Connector Heartbeat Chart" position="center" showCaption="true"}

### Adding a Device to a Connector Site

In order to access the devices located at remote data centers through the
connector, these devices must be associated with the connector sites. 

To associate a device with a connector site:

1. Navigate to **Device Management** >** Device Inventory**.
2. Click the** New Device Discovery** button.
3. Fill out the relevant device information, select the connector site, and save by clicking **Discover** and **Add**.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/hJGBoKW7M5xuUymTflIMJ_image.png" size="74" width="687" height="413" caption="Adding Device to a Connector Site" position="center" showCaption="true"}