> 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/kubernetes-overview/configs-and-secrets/managing-secret-access-for-read-only-users-aws-and-gcp.md).

# Managing Secrets and ConfigMaps access for readonly users (AWS and GCP)

Configure readonly user access to both Kubernetes Secrets and ConfigMaps using the **AllowReadonlyK8sSecrets** flag. This setting applies to all readonly users, whether they are Administrators, Tenants, or Users.

1. From the DuploCloud Portal, navigate to **Administrator** -> **Systems Settings**.
2. Select the **System Config** tab, and click **Add**. The **Add Config** pane displays.<br>

   <div align="left"><figure><img src="/files/dcpaB6e0IP4PHjTnxnxb" alt="" width="416"><figcaption><p>The <strong>Add Config</strong> pane</p></figcaption></figure></div>
3. In the **Config Type** list box, select **AppConfig**.
4. In the **Key** list box, select **Allow Readonly Users to view Kubernetes Secrets**.
5. In the **Value** field, enter **True** or **False**. A true value allows readonly users to view Kubernetes Secrets and ConfigMaps. A false value prohibits readonly users from viewing Kubernetes Secrets and ConfigMaps.
6. Click **Submit**. Readonly access to sensitive data in Kubernetes Secrets and ConfigMaps is configured.

<figure><img src="/files/tVxlnTvcYRVs0PvH0iBB" alt=""><figcaption><p>The <strong>System Config</strong> page with the <strong>AllowReadonlyK8sSecrets</strong> flag set to False</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.duplocloud.com/docs/automation-platform/kubernetes-overview/configs-and-secrets/managing-secret-access-for-read-only-users-aws-and-gcp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.