Arcade-Level RBAC
What is Arcade-level RBAC?
Arcade-level RBAC (role-based access control) lets you control who can view or edit a specific Arcade, without changing access across your entire workspace.
This allows teams to collaborate on individual Arcades while keeping workspace-level permissions unchanged.
How is Arcade-level access different from workspace access?
Workspace-level access determines who can create, manage, and own Arcades across the workspace.
Arcade-level access determines who can view or edit a single Arcade.
Workspace-level permissions remain the same. Arcade-level permissions apply only to the Arcade where they are set.
When do Arcade-level permissions apply?
Arcade-level permissions apply based on the visibility of the Arcade.
If an Arcade is set to public, anyone with the link can view it.
Viewer permissions do not apply to public Arcades
No invitation is required to view
Editor permissions can still be granted to control who can edit the Arcade
Public Arcades are designed for broad sharing and do not require viewer-level access controls.
Private Arcades
If an Arcade is set to private, access is restricted to invited users.
Viewer permissions apply only to private Arcades
Users must be explicitly invited to view or edit
Editors and viewers are managed through Arcade-level permissions
Private Arcades are designed for controlled access and collaboration.
Can I use editor permissions on public Arcades?
Yes.
Editor permissions can be used on both public and private Arcades.
Public Arcades: anyone can view, only invited editors can edit
Private Arcades: only invited users can view or edit
This allows teams to share content publicly while maintaining strict control over who can make changes.
How do I change an Arcade’s visibility?
Select one of the following:
Anyone with the link can view
When “Only invited users” is selected, you can manage individual permissions.
Who can I invite to an Arcade?
You can invite:
Members of your workspace
External collaborators outside your workspace
Invited users do not need to belong to your workspace to access a specific Arcade.
What permission levels are available?
Each invited user can be assigned one of two roles:
Can be changed back to Viewer or removed at any time
Can external collaborators edit an Arcade?
Yes. External collaborators can be invited as Editors for a specific Arcade.
Their access is limited to that Arcade only and does not grant workspace access.
How does Arcade distinguish workspace users from external users?
Arcade determines how access and feature availability apply based on whether an invited user is part of your workspace and whether they have a paid Arcade seat.
Workspace users (same domain)
Users whose email domain matches your workspace are considered workspace users.
Their access may extend beyond a single Arcade
Editor access may require a paid seat, depending on your plan
Workspace-level permissions continue to apply
External users (different domain)
Users whose email domain does not match your workspace are considered external users.
Their access is limited to the specific Arcade they are invited to
They do not receive workspace-level access
Their permissions apply only to that Arcade
What access do users without a paid seat have?
Users who do not have a paid Arcade seat can still be invited to collaborate on a specific Arcade, but their access is intentionally limited.
When added through Arcade-level permissions:
They can edit only the Arcade they are invited to
Their access to paid features is limited
Their usage is scoped to collaboration, not full workspace creation or management
This ensures teams can collaborate without granting unrestricted access to paid capabilities.
How does Arcade-level RBAC affect billing?
Billing behavior depends on your plan and whether the editor is a member of your workspace.
How does RBAC billing work on the Growth plan?
On the Growth plan:
Viewers never affect billing.
Editors who are members (and/or have the same domain) of your workspace require a paid seat.
When a workspace member (same domain) is added as an editor, billing is applied immediately.
Growth plans are designed for smaller teams with direct seat-based billing.
How does RBAC billing work on the Enterprise plan?
On the Enterprise plan:
Viewers never affect billing.
Editors who are members of your workspace are tracked and reconciled according to your Enterprise billing agreement.
Editor access is typically reviewed during scheduled billing true-ups rather than charged immediately.
Enterprise plans are designed for flexible collaboration across larger teams and external partners.
Does adding viewers affect billing?
No. Viewers do not affect billing on any plan.
Can viewers request edit access?
Yes. Viewers can request edit access, which can be approved or denied by an Arcade owner or editor.
Can I change or remove someone’s access later?
Yes. At any time, you can:
Change an editor to a viewer
Remove a user’s access entirely
Changes take effect immediately.
Does Arcade-level RBAC override workspace permissions?
No. Arcade-level RBAC works alongside workspace-level permissions.
Workspace admins retain full control over workspace-level settings.
When should I use Arcade-level RBAC vs workspace-level RBAC?
Use Arcade-level RBAC when you want to control access to a specific Arcade without changing permissions across your entire workspace.
Common use cases:
Sharing a single Arcade with an external partner or client
Collaborating on one Arcade with someone who doesn’t need full workspace access
Granting edit access to a specific Arcade while keeping the rest of your workspace restricted
Making an Arcade public for viewing while limiting who can edit it
Use workspace-level RBAC when you want to control access across all Arcades in your workspace.
Common use cases:
Adding or removing full team members (from the workspace)
Controlling who can create, edit, or manage Arcades by default
Applying consistent permissions across multiple projects
Managing long-term access for internal teams
How they work together
Arcade-level RBAC and workspace-level RBAC are designed to work together:
Workspace-level RBAC defines baseline access
Arcade-level RBAC allows fine-grained control for individual Arcades
This combination lets teams collaborate flexibly while maintaining clear boundaries and predictable billing.
