Roles and What Each One Can Do

There are two roles. Owners control billing, members, and roles. Members can change workspace settings and send invites, but cannot touch billing, change roles, or remove people.

Last updated 1 day ago

Team workspaces have two roles: owner and member.

What Each Role Can Do

Permission

Owner

Member

Manage roles

Yes

No

Manage billing and subscription

Yes

No

Change workspace settings

Yes

Yes

Add and remove members

Yes

No

Send and manage invitations

Yes

Yes

Both roles can write, edit, and publish content in the projects they have access to. The role controls administration, not whether someone can do the work.

Worth Knowing about Members

Members can send invitations. This surprises people. A member can invite someone else into the workspace, though only to projects the member can access themselves.

Members can change workspace settings. That includes the workspace name and logo.

Members cannot see or change billing. They cannot buy credits, change the plan, or cancel. If a member reports that billing will not open, that is the expected behaviour rather than a fault.

Members cannot remove people or change roles. Only owners can.

Owners

The person who created the workspace is its owner. Owners have every permission, and their credit spend is never limited by a monthly cap.

What a Role Does Not Control

Two things are separate from the role and are set per person:

  • Project access. Which projects someone can open. Set when you invite them, changeable afterwards.
  • Monthly credit limit. How much of the shared credit pool they can spend. Owners are exempt.

So a member with access to one project and a low credit limit is quite different from a member with access to everything and no limit, even though both are members.

Personal Workspaces

Personal workspaces have one person, who is the owner. Roles do not apply.

Changing Someone's Role

Owners can change roles from Settings β†’ Members.

Notes

Both roles see the same navigation. The difference appears when a member opens a section they cannot act in.

Removing someone from the workspace does not delete the content they created. Their documents stay in the projects where they were written.