> 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/access-control/user-access-and-permissions/tenant-access/read-only-access-to-a-tenant.md). # Read-Only Access to a Tenant Limit a user's access to a Tenant to read-only ## Setting a User's Tenant Access to Read-Only Temporarily or permanently restrict a user from making changes to an existing tenant in the DuploCloud Portal. 1. In the DuploCloud Portal, navigate to **Administrator** -> **Tenants**. 2. From the **NAME** column, select the tenant you want to limit access to. 3. Select the **User Access** tab. 4. Click **Add**. The **Add User Access** pane displays.

Add User Access pane

5. From the **User** list box, select the user for whom you want to limit access. 6. Select **Readonly Access**. 7. Click **Add**. The **User Access** tab displays **Yes** in the **READ ONLY** column. The user has read-only access to the Tenant.

User Access tab showing a user with read-only access to the Tenant

--- # 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/access-control/user-access-and-permissions/tenant-access/read-only-access-to-a-tenant.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.