Roles & Permissions

Sticklight uses two layers of permissions: workspace roles and project roles. Workspace roles control what you can do across the entire workspace. Project roles let you fine-tune access to individual projects.

Workspace Roles at a Glance

Role	What they do
Owner	Full control over the workspace, including billing, members, and all projects
Admin	Manages projects and members, but cannot access billing
Editor	Builds and publishes projects, but cannot manage members
Viewer	Views projects, but cannot build
Collaborator	External user with access to specific projects only

What Can I Do?

If you want to build and publish

Owners, Admins, and Editors can:

• Create new projects
• Build with AI chat
• Edit manually and visually
• Publish and update sites
• View and edit code (Pro plans)

Viewers can view the preview and leave comments, but cannot make changes.

If you want to manage the database

Owners, Admins, and Editors can:

• Enable Cloud Backend
• Create and edit database tables
• Add and modify data
• Manage secrets and edge functions

Owners and Admins can also:

• Delete database tables
• Delete any data (not just their own)

Editors can delete data they created, but not data created by others.

If you want to manage files

Owners, Admins, and Editors can:

• Access the Files tab
• Upload files and create folders

Owners and Admins can also delete files. Editors cannot delete files.

If you want to connect services

Owners and Admins can:

• Add and remove connectors at the workspace level

Owners, Admins, and Editors can:

• Connect and disconnect their own GitHub account
• Add connectors at the project level

If you want to manage people

Owners can:

• Invite and remove any role, including other Owners and Admins
• Manage billing and subscription
• Delete the workspace

Admins can:

• Invite and remove Editors, Viewers, and Collaborators
• Invite other Admins

Editors can:

• Invite Editors and Viewers to the workspace
• Invite Viewers to specific projects

Viewers cannot invite or remove anyone.

If you want to change settings

Owners and Admins can edit project settings, including custom domains.

Editors can view settings but cannot edit them.

Viewers cannot access project settings.

Project Roles

When someone joins your workspace, their workspace role automatically maps to a project role:

Workspace Role	Project Role
Owner	Project Owner
Admin	Project Admin
Editor	Project Editor
Viewer	Project Viewer

Collaborators are different. They are invited directly to specific projects with a chosen access level: Admin, Editor, or Viewer. They only see the projects they are invited to.

Project role capabilities

Project roles mirror workspace roles for most actions:

• Project Owner and Admin: Full project control, including deleting the project, unpublishing, and managing collaborators
• Project Editor: Can build, publish, and revert versions, but cannot delete or unpublish
• Project Viewer: Can view and comment only

Collaborators

Collaborators are Sticklight users invited to specific projects without full workspace membership. They are useful when you need outside help on a project without giving access to your entire workspace.

What Collaborators can do:

• Access only the projects they are invited to
• Perform actions based on their project role (Admin, Editor, or Viewer)
• Consume workspace credits if they have Editor or Admin access

What Collaborators cannot do:

• See other projects in the workspace
• View the workspace member list
• Access workspace settings or billing

See Managing Workspace Members for how to invite Collaborators.

Who Consumes Credits

Building with AI consumes credits from the workspace balance.

Role	Consumes Credits
Owner	Yes
Admin	Yes
Editor	Yes
Viewer	No
Collaborator (Editor access)	Yes
Collaborator (Viewer access)	No

Reference Tables

Workspace permissions

Capability	Owner	Admin	Editor	Viewer
View workspace members	✓	✓	✓	✓
Invite Editors and Viewers	✓	✓	✓	✗
Invite Admins	✓	✓	✗	✗
Remove Editors and Viewers	✓	✓	✗	✗
Remove Admins	✓	✗	✗	✗
Create projects	✓	✓	✓	✗
Delete projects	✓	✓	✗	✗
Manage billing	✓	✗	✗	✗
Purchase credits	✓	✗	✗	✗
View credit balance	✓	✓	✓	✗
Add workspace connectors	✓	✓	✗	✗
Delete workspace	✓	✗	✗	✗

Project permissions

Capability	Owner	Admin	Editor	Viewer
Build with AI	✓	✓	✓	✗
Publish	✓	✓	✓	✗
Unpublish	✓	✓	✗	✗
Connect custom domain	✓	✓	✗	✗
Enable Cloud Backend	✓	✓	✓	✗
Create database tables	✓	✓	✓	✗
Delete database tables	✓	✓	✗	✗
Upload files	✓	✓	✓	✗
Delete files	✓	✓	✗	✗
Edit project settings	✓	✓	✗	✗
Delete project	✓	✗	✗	✗
View version history	✓	✓	✓	✗
Revert to previous version	✓	✓	✓	✗
Invite collaborators	✓	✓	Viewers only	✗
Remove collaborators	✓	✓	✗	✗
Transfer project	✓	✓	✗	✗
Leave project	✓	✓	✓	✓

Project Transfer and Permissions

When a project is transferred to another workspace, all permissions reset completely. Every prior grant is wiped.

• The recipient becomes the sole Owner of the project (and any other workspace members receive the corresponding access)
• The sender stays on as an Editor (with build and publish access, but no ownership)
• All other members and collaborators lose access

The new Owner controls who has access going forward. They can invite members or remove the original sender if they choose.

See Transferring a Project for the full transfer process.

FAQs

Can I have multiple Owners?

Yes. A workspace can have multiple Owners, and any Owner can promote another member to Owner. All Owners share billing permissions.

What happens if I remove someone?

They lose access immediately. Any work they contributed remains in the project.

Can I change someone’s role?

Yes. Owners and Admins can change roles for existing members. See Managing Workspace Members.

Why can Editors invite other Editors?

This lets team members bring in collaborators without needing Admin approval for every invite. Editors can only invite Editors and Viewers, not Admins or Owners.