Pular para o conteúdo
AvraAvra
Esc
↑↓navegar↵abrir⌘Jpré-visualizar
Nesta página

Roles & permissions

The roles in your organization, what each one can do in the dashboard and the API, and how to change a member's role.

Avra uses role-based access control scoped to your organization. Each member has one role, and it applies across every workspace in the organization, in the dashboard and through the API. Creators choose a member’s role when they invite them, and can change it at any time under Settings → Organization → Members.

Ana’s role is set once, for the organization. She’s a Developer in every workspace, including workspaces created after she joined, so there’s no workspace where she has more or less access than anywhere else.

Roles

Role Description
Creator Full administrative access, including workspaces, billing, and members
Developer Technical access for integration: models, predictions, batches, API keys, and webhooks
Analyst Read-only access to models and batches, for reporting and analysis
Billing Manager Access to invoices
Auditor Read-only access to the audit and usage logs
Member Basic read access to workspace resources

Permissions

Capability Creator Developer Analyst Billing Auditor Member
Workspaces
Create and update workspaces ✓
Archive and unarchive workspaces ✓
Models
View models and versions ✓ ✓ ✓ ✓ ✓
Manage aliases ✓ ✓
Run predictions ✓ ✓
Batches
View batches ✓ ✓ ✓ ✓
Create batches ✓ ✓
Download results ✓
File Transfer: Sent to Avra and Received from Avra
Download files ✓
Upload files ✓
Delete uploaded files ✓
API keys and webhooks
Manage API keys ✓ ✓
Manage webhooks ✓ ✓
Billing and logs
View invoices ✓ ✓
View the usage log ✓ ✓
View the audit log ✓ ✓
Team
Manage members ✓
View members ✓ ✓ ✓ ✓ ✓ ✓

Your organization’s notification settings are permission-controlled too. Ask a Creator if you need to change them.

Where each role works

The permissions in the matrix map to these places in the dashboard.

Role Where they work
Creator Everywhere: workspace settings, API keys, Members, Billing, the logs under Observability, and File Transfer
Developer Models, to manage aliases and run predictions; Batches, to create them; Settings → Workspace → API keys; and Alerts → Webhooks
Analyst Models and Batches, read-only
Billing Manager Settings → Organization → Billing, for invoices
Auditor Observability → Audit and Observability → Usage, and Models, read-only
Member Models and Batches, read-only

Every role can view the member list under Settings → Organization → Members, and every member sets their own notifications under Alerts → Notifications.

Without a permission

The dashboard adapts to each role. The sidebar leaves out entries a role can’t use at all, such as Alerts → Webhooks for roles that can’t manage webhooks, and File Transfer for roles that can’t download files. On the Notifications page, the Organization tab appears only for members allowed to see the organization’s settings.

Other pages still open. Some show a notice instead of their content, such as You do not have permission to view invoices under Billing. Others turn off the controls a role can’t use: without permission to manage API keys, Create Key is turned off, with a tooltip saying why.

Hiding a control isn’t what protects it: a member’s role applies through the API too.

Choose a role

Follow least privilege: give each member the narrowest role their work needs.

Engineers who integrate the API, manage keys, and run batches need Developer. People who follow models and batches for reporting need Analyst. Finance needs Billing Manager to reach invoices, and compliance or security reviewers need Auditor to read the logs. Keep Creator for the few people who manage members, workspaces, and billing.

Change a role

Only Creators change roles.

Open the member list

Go to Settings → Organization → Members.

Select the current role

Find the member, and select their current role.

Choose the new role

Choose the new role. The change takes effect immediately, in every workspace.

Role changes are recorded in the audit log, under Observability → Audit. See Audit and usage logs.

Key behaviors

Removing a member removes their access to the organization. API keys belong to the workspace, not to the member who created them, so rotate any key that should stop working. See Team management.

Where to go next

Esta página foi útil?