Console Access Control
PhoenixAI access control
PhoenixAI employs role-based access control (RBAC) to manage privileges within a PhoenixAI cloud account. RBAC gives account administrators the ability to restrict privileges within the account on granular level with ease.
Enable Multi-Factor Authentication
You can enforce Multi-Factor Authentication (MFA) on access to the PhoenixAI Cloud console. MFA adds an extra layer of security by requiring two or more forms of verification when users sign in, thereby significantly decreasing the likelihood of unauthorized access.
End-to-End Private Link
For security reasons, you may want to secure all the traffic between your client and the PhoenixAI Cloud service and between your PhoenixAI cluster and PhoenixAI Cloud service, ensuring that sensitive data and queries are protected. We provide an End-to-End Private Link solution to meet this requirement by restricting all the traffic within the cloud provider's internal network.
Manage roles in an account
PhoenixAI employs Role-Based Access Control (RBAC) to manage privileges within a PhoenixAI cloud account.
Manage members in an account
After you create a PhoenixAI cloud account, you are delegated as the creator of the account. You can share your account with your team members by inviting them to your account. Your account serves as the billing entity, and all members within the account share the equivalent administrative role to manage clusters, billing, network configuration, and more.
PhoenixAI Studio Access Control
By default, PhoenixAI allows users to connect to PhoenixAI Studio from any IP address. You can set IP Access List for a PhoenixAI cluster to allow or deny access to the page based on its origin.
Use SAML SSO
PhoenixAI supports user authentication using Security Assertion Markup Language (SAML) single sign-on (SSO). SSO enables account administrators to authenticate PhoenixAI members via a specific identity provider (IdP). This allows members to sign in to their PhoenixAI Cloud account without further login credentials after they log in to the IdP.