What the user roles are (Owner, Supervisor, Member, Technical administration permissions)

Every person on your team has a role within WorkOS, which decides what they can see and do.

Owner

Full control of the account: can see the rest of the team's work (with the From others tab in Tasks, Projects and Agenda), open and edit any project, use the Board to distribute projects, create projects and assign them to anyone, manage the Team, and access all settings and integrations.

Supervisor

Can see and manage the tasks of the people who report directly to them (their direct reports), through the My team tab. Can be the assignee of projects and create them (unless the WorkOS administrator has turned it off in your account), but can only make themselves the assignee, and in Projects only sees the ones they are the assignee of or participate in (not those of their direct reports). Doesn't have access to the rest of the account's settings.

Member

The default role: normal use of the app, seeing only their own tasks/projects/meetings and what they share with others (Where I participate in Tasks and Agenda; in Projects, My projects already includes the ones they participate in). Cannot create projects or be the assignee of one: in Projects they only participate.

Technical administration permissions

Not a role on its own, but an extra flag that can be added to anyone (usually combined with the Member role): it grants access to the Notion databases screen, lets them manage other Team members' Role/Direct reports and, in Projects, open and edit any project and use From others and the Board, without needing to be Owner.

Where it's managed

From Settings → Team, whoever has permission can see the list of people and assign their Role. The Owner and people with Technical administration permissions can also add a new person (their user is created automatically) and assign any role, Owner included. Only the Owner marks who has Technical administration permissions.

When a change takes effect

A role change, the Technical administration permissions mark or a user's deactivation take effect in under a minute, even if that person has a session open: they don't need to sign out. If someone goes from Owner to Member, they immediately lose what their role allowed; if a user is deactivated, their session is closed and they can no longer sign back in.

Why it matters

Roles aren't just about administration permissions — they also decide what you see day to day: which tasks/meetings/projects show up in your lists, and which emails or notes you can read. For example, each person's email is private (not even the Owner reads a colleague's), and notes can be restricted by Team.

Permissions summary

To see at a glance what each role can do in each module, read "Who can do what: permissions summary by module".