RBAC
Organization roles that decide who can see, change and manage what in your workspace.
What is RBAC?
Role-based access control (RBAC) gives people permissions through roles, such as admin or viewer, instead of setting access one user at a time. On Spro, organization admins create roles with a set of permissions and assign them to members. Access to workspaces, keys and settings then follows the role.
As AI usage spreads through a company, people need different access. Some should change routing and keys, and others should only read usage. RBAC keeps that consistent by tying permissions to roles instead of to individuals.
Spro's organization pages let admins create roles, update the permissions in each role and assign roles to members. Changing a member's role changes what they can do.
Key features
What this feature does for your requests.
- Create roles with a chosen set of permissions
- Assign one or more roles to each member
- Manage members from the organization members page
- Update a role's permissions in one place
How it works
4 steps, from setup to the first request.
- 01
Create a role
Name the role for the job it covers.
- 02
Choose its permissions
Pick what the role can view and change.
- 03
Assign it to members
Add the role to each person who needs it.
- 04
Review regularly
Update roles as teams and responsibilities change.
Is it the right fit?
Specific situations where this feature helps, and where it does not.
Good fit if
- Several teams need different access to keys, routing and billing
- More than a few people administer the account
- Access must be removed quickly when someone leaves
Not a good fit if
- A single person runs everything
- You need permissions inside your own app. RBAC covers dashboard access
- You need roles synced automatically from an identity provider. That is not part of RBAC today
RBAC FAQs
Common questions about RBAC.
Route every AI request through SPRO.
One OpenAI-compatible API for 350+ models, with intelligent routing, 29 built-in guardrails, observability, and automatic failover.
