Roles and Permissions

Understand the RBAC model in PlayableLabs with five organization roles and a detailed permission matrix

Overview

PlayableLabs uses role-based access control (RBAC) to manage what each team member can do within an organization. The system has two tiers:

System Roles -- Platform-wide roles (User, Supervisor, System Admin)
Organization Roles -- Per-organization roles that control access to games, assets, and settings

This page focuses on the five organization roles that you interact with daily.

The Five Roles

Owner

Full control over the organization, including deletion
Can transfer ownership to another member
Cannot be removed (only transferred)
One Owner per organization

Typical users: Founders, agency owners, studio heads

Admin

Manage all games, assets, and team members
Configure organization settings
Create and manage teams
Cannot delete the organization

Typical users: CTOs, account managers, technical directors

Manager

Create, edit, and delete games, versions, and variants
Export playable ads
Cannot manage team members or organization settings

Typical users: Product managers, creative directors, campaign managers

Member

Create and edit games (may require approval)
Upload and manage assets
Create and edit variants
Export playable ads
Limited to assigned content visibility

Typical users: Developers, designers, content creators

Viewer

Read-only access to assigned games and assets
Can view and download exports
Cannot make any changes

Typical users: Clients, stakeholders, investors, executives

Permission Matrix

Action	Owner	Admin	Manager	Member	Viewer
Organization
Delete organization	Yes	No	No	No	No
Edit organization settings	Yes	Yes	No	No	No
View organization	Yes	Yes	Yes	Yes	Yes
Team Members
Invite members	Yes	Yes	No	No	No
Remove members	Yes	Yes	No	No	No
Change roles	Yes	Yes	No	No	No
Teams
Create/manage teams	Yes	Yes	No	No	No
Join teams	Yes	Yes	Yes	Yes	Yes
Games
Create games	Yes	Yes	Yes	Yes*	No
Edit all games	Yes	Yes	Yes	No	No
Edit assigned games	Yes	Yes	Yes	Yes	No
Delete games	Yes	Yes	Yes	No	No
View all games	Yes	Yes	Yes	No	No
View assigned games	Yes	Yes	Yes	Yes	Yes
Variants
Create variants	Yes	Yes	Yes	Yes	No
Edit variants	Yes	Yes	Yes	Yes	No
Delete variants	Yes	Yes	Yes	No	No
Export variants	Yes	Yes	Yes	Yes	Yes
Assets
Upload assets	Yes	Yes	Yes	Yes	No
Delete assets	Yes	Yes	Yes	No	No
View assets	Yes	Yes	Yes	Yes	Yes

*Members can create games but may need approval depending on organization settings.

Role Hierarchy

Roles follow a strict hierarchy where higher roles inherit all permissions of lower roles:

Owner (5) > Admin (4) > Manager (3) > Member (2) > Viewer (1)

This means an Admin automatically has every permission that a Manager, Member, and Viewer has.

Multi-Organization Support

Users can hold different roles in different organizations. For example, you might be an Owner of your own agency organization and a Viewer in a client's organization.

Your role is evaluated per-organization, and switching organizations via the organization selector updates your permissions accordingly.

Best Practices

Least privilege -- Assign the minimum role required for each person's responsibilities
Limit Owner and Admin roles -- Only essential personnel should have administrative access
Use Manager for leads -- Give project leads Manager access instead of Admin when they don't need team management
Viewer for external stakeholders -- Provide clients with read-only access instead of sharing exports manually
Audit regularly -- Review role assignments periodically in the Members page

Next Steps

Team Members -- Invite and manage your roster
Team Management -- Activity logs, audit trails, and team settings

On this page