> 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/known-limitations.md). # Known limitations What the Control Plane does not do yet, so none of it is a surprise. This page reflects release **v0.3.32**, read on **14 September 2026**, and will drift. ## Not built yet * **Teams.** There is no team object; roles are granted person by person. The Teams page is hidden until it exists. * **Service accounts and API keys in the UI.** Machine identities are Keycloak clients, managed in Keycloak. * **Audit trail.** Grants and records carry who created them and when, but there is no event log of administrative changes. * **External secret manager and key rotation.** Secrets are stored in the Control Plane's database under a single master key. * **Repository-level permissions.** Roles apply to the workspace or to a project, not to a single repository. * **Organisation hierarchy, budgets, policies.** None of these live in the Control Plane yet; see [Roadmap](/visdom-control-plane/roadmap.md). ## Operational * **Single replica.** There is no coordination between instances; deploy one replica with a *Recreate* upgrade strategy. * **No Helm chart** in the repository. Deployments today use Kustomize through GitOps. * **`/readyz` does not check the database.** Use it as a liveness signal only. * **Keycloak federation is configuration, not a feature.** The shipped realm has one external identity provider (Google); Entra ID, LDAP or SAML are added in Keycloak by the installer. ## Rough edges * Disabling a user is available in the API but has no button in the UI. * The Settings gear in another product opens the Control Plane UI, which requires Control Plane sign-in access; a person with access only to that other product sees *Access not granted* there. * The workspace timezone editor is enabled in the UI only for the Keycloak admin role, although the API also accepts the granted Admin role. --- # 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/known-limitations.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.