Role-Based Access Control (RBAC) for SingleStore Aura
On this page
Note
This is a Preview feature.
SingleStore Aura supports Role-Based Access Control (RBAC), which allows administrators to assign granular permissions at multiple levels.
Refer to Role-Based Access Control (RBAC) for SingleStore Helios for more information on RBAC in SingleStore Helios.
Benefits of RBAC in SingleStore Aura
-
Operational Efficiency: You can onboard or offboard users efficiently and modify their access based on role changes.
-
Secure Collaboration: RBAC ensures that users access only the resources they need.
For example, data scientists can build applications, while analysts can view them without making changes. -
Compliance-Ready: Role-to-resource mappings and access logs simplify audit processes and help meet regulatory requirements.
-
Orphaned Resource Prevention: When users leave, RBAC helps prevent lost or unmanaged assets by enabling easy transfer of ownership.
Predefined Roles for Aura App Resource
Role |
Description |
Permission |
---|---|---|
Owner |
Owners are granted full access including the ability to manage access, operate, delete, monitor and use the Aura App. |
|
User |
Users are granted access to only use Aura App and create Aura API keys. |
|
How to Use RBAC in SingleStore Aura
Aura App users can enforce RBAC in SingleStore Aura using both the Cloud Portal and Management API.
Using Cloud Portal
To use RBAC in the Cloud Portal, perform the following steps:
-
Under the Develop section, navigate to an Aura App.
-
Select the three dots under the Actions column next to your Aura App instance, and then select Share.
-
From the list, select User or Team to share the Aura App with.
-
In the Access list, select the desired role next to the selected user or team.
-
To remove access for a user or team, select Remove Access in the Access list.
Using Management API
Use the Users
(/v1/users
endpoint) and Teams
path (/v1/teams
endpoint) in the Management API to use RBAC in SingleStore Aura.
Last modified: August 18, 2025