Member, Manager, Admin, and Owner

For everyone. App permission levels and what each can do.

Last updated About 1 hour ago

For everyone.

Every teammate has an app permission — Member, Manager, or Admin — shown in the Permission column on the Members tab. One person is also the organization owner (who created the workspace).

Permission levels

Permission	Who gets it	What it unlocks
Member	Default for new invites	Use chat, create projects and SOPs, complete assigned work.
Manager	Assigned by a manager or admin	Everything a member can do, plus invite and deactivate people at or below their own level, create and delete channels, and manage projects and SOPs org-wide.
Admin	Assigned by an admin	Everything a manager can do, plus org settings, billing, time-off policies, exports, and member wipe.
Owner	Who created the organization	All admin powers. Shown as Org owner in the Permission column. Cannot be deactivated. Must transfer ownership before leaving or deleting the org.

Rank matters

Permissions rank Member < Manager < Admin. Managers can only assign Member or Manager — not Admin. Managers and admins can only change or deactivate people at or below their own rank.

Owner stays Admin. The organization owner's membership always keeps Admin-level access. You cannot drop the owner to Member or Manager.

Who can invite and deactivate

Managers and admins can invite teammates and deactivate or reactivate people at or below their own permission level. Members cannot.

You cannot deactivate:

The organization owner — transfer ownership first.
The last active admin — promote someone else to Admin first.
Anyone above your own permission level.

Other rules

Create channels: managers and admins.
Create projects or SOPs: any member.
Org settings and billing: admins (and the owner).

Custom org roles (job titles on the Roles tab) are a separate concept — they do not grant Admin or Manager powers. See Org roles vs app permissions.