Currently, the open-source (community) version of Phoenix does not support restricting user access to specific projects within a single instance. All users with access to the instance can see all projects, traces, datasets, and experiments; project-level isolation is not available. For stricter isolation, the recommended approach is to deploy a separate Phoenix instance per project, each with its own database and authentication configuration. Fine-grained, per-project RBAC and multi-tenancy are planned for future releases, but are not available yet in the open-source version鈥攖hese features are present in the enterprise Arize AX platform instead.
For more details, see the official documentation on <https://arize.com/docs/phoenix/self-hosting/architecture|tenancy and scaling>, <https://arize.com/docs/phoenix/settings/access-control-rbac|RBAC>, and related <https://github.com/Arize-ai/phoenix/issues/4980|GitHub discussions>. Would you like more detail on how to set up multiple instances or on the current RBAC capabilities?
Sources:
- <https://arize.com/docs/phoenix/self-hosting/architecture|Phoenix Architecture: Tenancy & Scaling>
- <https://github.com/Arize-ai/phoenix/issues/4980|GitHub Issue: User/project isolation>
- <https://arize.com/docs/phoenix/settings/access-control-rbac|RBAC>
