# Roles and permissions [#roles-and-permissions]

Use the organization role for membership, administration, and **Shared** work. A **Private** workspace has its own access list. A **Local** workspace stays in the original app or browser profile and has no sharing roles.

## Organization roles [#organization-roles]

| Capability | Owner | Editor | Viewer |
| --- | :---: | :---: | :---: |
| Open Shared workspaces and view the member list | Yes | Yes | Yes |
| Create, edit, and delete content in Shared workspaces | Yes | Yes | No |
| Create Private or Shared workspaces | Yes | Yes | No |
| Rename or delete Shared workspaces | Yes | Yes | No |
| Invite, remove, or change members | Yes | No | No |
| Manage organization details and billing | Yes | No | No |
| Create and download backups or view the Audit log | Yes | No | No |
| Delete the organization | Yes | No | No |

Team organization owners can [invite members](/teams/share-a-workspace) as Editor or Viewer. Personal organizations have one member.

## Private-workspace roles [#private-workspace-roles]

| Workspace access | What it allows |
| --- | --- |
| **Workspace owner** | Manage access, change visibility, transfer ownership, and edit content. |
| **Editor** | Edit the workspace's content and manage its extensions. |
| **Viewer** | Open and read the workspace. |
| **No workspace access** | The workspace stays hidden from this member. |

A workspace owner can grant workspace access to existing organization members. For example, an organization Viewer with the workspace Editor role can edit that Private workspace while staying a Viewer of Shared work. Use [Share a workspace](/teams/share-a-workspace) to grant access.