> 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/managed-service-accounts-rbac.md). # Managed Service Accounts (RBAC) For Kubernetes Power Users: Information about the service accounts created by DuploCloud When a DuploCloud Tenant is created with Kubernetes access, DuploCloud creates three service accounts that are mapped to the Tenant's unique namespace. ## Account types * `default -` The `default` account serves as a template for creating other accounts. This account cannot be altered by the end user. There are no role bindings for the `default` service account. * `duploservices--readonly-user` - This service account is assigned to the `duploservices--readonly-role` role binding. It provides read-only access to resources in the Tenant * `duploservices--edit-user` - This service account is assigned to the `duploservices--edit-role` role binding. It provides edit access to resources in the Tenant. This is the service account that is assigned to a new Pod, unless you explicitly override it Service accounts can be applied to Pods using the DuploCloud Service's **Other Pod Configuration** field when you Add a [Service](/docs/automation-platform/container-orchestrators/concepts.md). --- # 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/kubernetes-overview/managed-service-accounts-rbac.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.