# Roles and permissions

What owners, admins, members and participants can each do, and why the last owner cannot be removed.

Source: https://launchgenius.app/help/roles-and-permissions
Last updated: 2026-08-25

A workspace has owners, admins and members. A launch also has participants, who
are not workspace members at all: they joined through a link and need no
account.

| Can | Owner | Admin | Member | Participant |
|---|---|---|---|---|
| Schedule, hold, cancel or delete a launch | Yes | Yes | No | No |
| Edit launch details and the brief | Yes | Yes | No | No |
| Manage billing | Yes | Yes | No | No |
| Manage contacts and create invite links | Yes | Yes | No | No |
| Approve, reject or suggest edits | Yes | Yes | Yes | No |
| Write and schedule posts | Yes | Yes | Yes | Own only |
| Add or remove media library files | Yes | Yes | Yes | No |
| Browse and use the media library | Yes | Yes | Yes | Launches they joined |
| Triage failures | Yes | Yes | Yes | No |
| Change an owner's role, remove an owner | Yes | No | No | No |

The last owner can never be demoted or removed, because a workspace with no
owner has nobody who can manage billing or recover it.

Workspace invite links can grant member or admin, never owner. Ownership is
handed over deliberately by an existing owner.

## Participant is not a role in your workspace

Somebody on a launch's roster can write and manage their own posts on that
launch and nothing else. They cannot see your contacts, your other launches,
your billing, or anyone else's drafts.

Being a participant on somebody's launch does not let you create standalone
posts of your own. That needs membership of a workspace.

## Cohorts are not permissions

A cohort groups the roster and suggests when that group posts. It grants
nothing and restricts nothing. Two people in different cohorts have exactly the
same abilities on a launch.