> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/security-and-compliance/access-control-2/database-access-for-users.md). # Database Access for Users Grant access to specific databases for DuploCloud users Administrators have full access to all databases created in all DuploCloud Tenants. A non-administrator user can view and use database engine types created by an administrator if the administrator grants them view rights. ## Granting Users View Access to Database Engines 1. In the DuploCloud Portal, navigate to **Administrator** -> **System Settings**. 2. Click **System Config**. 3. Click **Add**. The **Add Config** pane displays.

Add Config pane

4. From the **Config Type** list box, select **AppConfig**. 5. From the **Key** list box, select **RDS approved list for non admin users**. 6. Select the **Value** list box, and select the types of databases you want non-administrator users to access. In this example, the user is granted access to any **Aurora-MySql** and **Aurora-PostgreSql** database engines the Administrator creates. 7. Click **Submit**. The **AppConfig** configuration setting is displayed on the **System Settings** page.

System Settings page with AppConfig configuration setting

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.duplocloud.com/docs/automation-platform/security-and-compliance/access-control-2/database-access-for-users.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.