> For the complete documentation index, see [llms.txt](https://docs.visdom.virtuslab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visdom.virtuslab.com/visdom-control-plane/user-guide/users-and-permissions.md). # Users and permissions Who can sign in to which product, and what they can do there. ## Users People appear under **Users** the first time they sign in through Keycloak; there is nothing to invite. The list is paginated and sortable and readable by anyone with the Control Plane Viewer role. An admin can disable a user through the API. A disabled user is refused by the Control Plane and receives no permissions in any product. Disabling yourself is not allowed. ## How access is decided Access is deny by default and has two layers: 1. **Sign-in access** to a product. Without it the person does not get into that product at all. 2. **Roles** inside the product, each at a fixed scope – the whole workspace or one project. A role without sign-in access does nothing. Admins hold everything. | Product | Workspace roles | Project roles | | -------------- | ------------------------------------------------------- | ---------------- | | Orchestrator | Building blocks viewer, Building blocks operator, Admin | Viewer, Operator | | Context Fabric | Administrator | Viewer, Operator | | AI Tracing | Admin | Viewer, Operator | | Control Plane | Viewer, Admin | Operator | What each role allows inside a product is defined by that product: Viewer reads, Operator configures and runs, Admin manages the product for the whole workspace. In the Control Plane itself: * **Viewer** reads users, grants, projects, secret metadata and repositories. * **Operator** configures one project: its name and description, repositories, repository token and project secrets. * **Admin** creates and archives projects, grants and revokes roles, disables users, writes workspace secrets and sets the workspace timezone. ## Granting a role Open **Permissions**, find the person, turn on **Sign-in access** for the product, then add roles. A project-scoped role asks for the projects it applies to; selecting several projects creates one grant per project. Each grant records who gave it and when. Revoking sign-in access to a product also removes the person's other roles in that product, so access never lingers behind a switched-off door. ## Admins The `control-plane-admin` realm role in Keycloak makes a person an admin. The granted Control Plane **Admin** role has the same authority and is managed here rather than in Keycloak. Admins of other products (`orchestrator-admin`, `context-admin`, `ai-tracing-admin`) see every project in the Control Plane but get no Control Plane rights from that alone. --- # 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.visdom.virtuslab.com/visdom-control-plane/user-guide/users-and-permissions.md?ask=&goal= ``` `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.