Arize AI Community Icon

Home
Events

Arize AX Releases
Arize AX Support
Arize News
Arize Observe
Discussions
Introductions
Phoenix Support

Powered by Tightknit

Phoenix Support

Understanding Phoenix: Authentication vs Authorization Limits | Arize AI Community

Phoenix Support

Understanding Phoenix: Authentication vs Authorization Limits

·May 01, 2025 04:12 PM

Do I understand correctly that phoenix only supports authentication, but not authorization? I'm trying to find out if there is a way to control which users have permission to read from or write to which project?

3 comments

· Sorted by Oldest

RunLLM
APP
·
Phoenix supports both authentication and authorization through Role-Based Access Control (RBAC). According to the Phoenix documentation, RBAC allows for user roles such as admin and member, which control access to the system. Admins have full control, including managing users and system keys, while members can perform tasks like adding traces and experiments. However, Phoenix does not currently support fine-grained access control at the project level, meaning you cannot restrict read/write permissions to specific projects for different users.Would you like more detail on how RBAC is implemented in Phoenix?Sources: - Phoenix documentation
💡 Hint: Mention RunLLM in the thread for followups.
💡1
Zhuyi X.
·
so when multiple users are using the same pheonix instance (self-hosted), there is no way to track who created a project or added entities like dataset, experiements, etc. to it, right?
Zhuyi X.
·
e.g. when users are playing with prompts in the playground, the queries become traces, is there a way to track which user created a trace?