Studio · 4 minutes
Understand Studio roles and controls
Know what owners, administrators, and members can manage before assigning access.
Use this guide with Aura
Open the existing Studio dashboard, then keep this guide beside it while you follow the steps. Aura does not receive the page text, your account, your project, or anything you typed.
If the Studio page does not open, sign in to the Aura dashboard and choose Studio.
Before you start
- A Studio workspace exists.
Plan and model funding
Roles control access to workspace management. They do not silently change the funding source selected for a model request.
Say this in ordinary language
No prompt is required.
Steps
-
1
Open Dashboard, Studio, and review the member list.
What you should see: Every member shows a role and active status.
-
2
Use Owner for the person responsible for the workspace and billing relationship.
What you should see: The owner retains the highest workspace authority.
-
3
Use Admin only for people who should manage members and organization provider keys.
What you should see: Administrators receive management controls allowed by workspace policy.
-
4
Use Member for developers who need the shared workspace and allowed funding without administrative access.
What you should see: Members see provider availability and model choices but never raw keys or billing controls.
What Aura may change
Changing a role changes workspace permissions; it does not duplicate the person's account or copy provider secrets to their computer.
How to verify it worked
Test each role with its own signed-in account and confirm forbidden controls are absent and the server rejects forbidden actions.
Undo or recover
An authorized owner can change roles or remove a member. Removing a member releases the assigned seat.
Common problems
- A hidden button is not enough by itself; Aura's server must also reject an action that role is not allowed to perform.
- An invitation marked Admin reserves the seat but grants nothing until the invited account accepts.