---
title: Database Access Manager Configurations
slug: singleconnect-reference-guide-3-3-0/database-access-manager-configurations
description: Learn how to effectively manage database access in multitenant environments with Single Connect's Database Access Manager. This comprehensive tool allows users with a license for Data Access Management and Multitenancy to utilize all the features of the S
docTags: 
createdAt: 2022-08-02T21:37:19.000Z
---

Single Connect offers a Database Access Manager for multitenant environments. All features of the SQL Proxy are enabled on a multitenant environment, if the user has a license for Data Access Management, along with Multitenancy. Logging, Policy Enforcement, and Masking can be provided.


For a user, device, and policy definition details, please refer to section [](https://app.archbee.com/docs/jsymInd0w_SXayMlKGOmR/5qFd2MJYKbHUD5U7k_n8T)[User/Device/Policy Definition](docId\:GIY4A3O_Acl_brhmGAySs). To add Oracle devices for new tenants, the following parameter should be set from the host admin System Config Manager screen for the port assigning option:

1. Navigate to the** Administration** >** System Config Man**.
2. Set the **sql.proxy.bind.port.range** parameter with the requested port range.

| **Parameter Name**                                          | **Parameter Value**                                                                                                                         |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| **sql.proxy.bind.port.range**                               | Port range (e.g. 6000-7000)                                                                                                                 |
| **sql.proxy.oracle.local.bind.port.tenant\_$tenant\_name$** | Port number for Oracle devices (e.g. 5000). It should be added separately for each newly created tenant, if the Oracle device will be used. |

For dynamic data masking, please refer to section [Dynamic Data Masking](docId:-IXHRD2oxM6ZY74K-0uqd) For further guidance, please refer to the **How to use Data Access Manager in Multitenancy** document.