Short answer: you can’t. In Prefect 1.x, the “Teams” features (members, roles/RBAC, org API tokens) are Cloud-only. When you deploy the open-source Prefect Server via Helm, those parts of the shared UI are intentionally disabled/greyed out because there’s no auth/multi-user in OSS Server. Your options: - Use Prefect Cloud for those features - In Prefect 1, Teams/RBAC/API tokens live in Cloud. If you must stay on 1.x, you’d need to run against Cloud instead of self-hosted Server to enable them. - Cloud signup: Prefect Cloud - Or upgrade to the current Prefect (3.x) and, if you need RBAC/API keys/SSO, use Prefect Cloud 3. OSS remains single-tenant without user management. - Prefect docs: Prefect 3 docs - If you must remain self-hosted and OSS-only, there’s no switch to flip. Typical workaround is putting Server behind your own reverse proxy/SSO for gatekeeping, but Prefect itself won’t have roles/users/tokens. References (helpful starting points): - Prefect 1 docs (Server vs Cloud overview): Prefect 1 docs - Helm charts: prefect-helm repo If you share your constraints (must self-host? need RBAC? timeline?), I can suggest a concrete path—either a minimal move to Cloud or an upgrade plan to 3.x with the right pieces on Kubernetes.