Roles

This page defines each access level you see in Orbit. For how a person ends up with a level — SharePoint permissions, editor seats, and admin rules — see Permissions.

Workspace roles

Orbit shows one of three role badges for a person in a workspace:

Role	What it allows
Reader	Open and read notes, follow live edits, and search the workspace. Readers never need a license.
Editor	Everything a Reader can do, plus create, edit, move, share, and delete notes. Requires an editor seat.
Admin	Everything an Editor can do, plus manage workspace settings and view the workspace’s member list.

Two rules decide these levels:

• Reader vs Editor comes from your own Microsoft 365 permissions on the workspace’s OneDrive folder or SharePoint library. Write permission without an editor seat shows as Editor reach but behaves as Reader.
• Admin is Orbit’s own rule: the workspace creator and your organization’s tenant admins are workspace admins. SharePoint permissions never grant it.

Note share roles

A note share carries one of two roles, chosen when the share is created:

Role	What it allows
Can view	Read the shared note.
Can edit	Read and edit the shared note. Editing through a share also requires the editor to hold a seat.

A share grants access to that one note only — never to the rest of the workspace.

Organization roles

Organization roles control who can use the organization tabs in settings (analytics, licenses, people, workspaces, audit):

Role	What it allows
Member	Normal user. No organization-wide settings access.
Tenant admin	Manage organization settings, licenses, and workspaces.
Tenant owner	Everything a Tenant admin can do, plus assign the Tenant owner and Tenant admin roles.

Tenant admins and owners are also workspace admins in every workspace of the organization.

See Organization admin settings for what each organization tab does.