> ## Documentation Index
> Fetch the complete documentation index at: https://www.seilers.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Workspace and Document Permissions in Seilers

> Set workspace and document-level roles in Seilers to control who can view, comment on, edit, and administer your playbooks and SOPs across your team.

Seilers uses a role-based permissions system that gives you fine-grained control over who can see, comment on, edit, and administer your playbooks and SOPs. You can set a default role at the workspace level and then override it for individual documents when you need more or less access for specific people.

## Permission Levels

Seilers has four roles, each with a progressively broader set of capabilities.

| Role      | Can View | Can Comment | Can Edit | Can Manage Members |
| --------- | :------: | :---------: | :------: | :----------------: |
| Viewer    |     ✓    |             |          |                    |
| Commenter |     ✓    |      ✓      |          |                    |
| Editor    |     ✓    |      ✓      |     ✓    |                    |
| Admin     |     ✓    |      ✓      |     ✓    |          ✓         |

* **Viewer** — can read any document they have been given access to. Ideal for stakeholders or team members who need to follow a process but should not change it.
* **Commenter** — everything a Viewer can do, plus the ability to leave inline comments and replies. Use this role for reviewers who need to give feedback without touching the document itself.
* **Editor** — can create, modify, and delete content within the documents or workspaces they've been granted access to. This is the right role for team members who actively maintain SOPs.
* **Admin** — has full control over the workspace or document, including adding and removing members, changing roles, and managing settings. Reserve this role for team leads and operations managers.

## Workspace vs. Document Permissions

Seilers applies permissions at two levels, and understanding the relationship between them saves you time when managing access.

**Workspace-level permissions** set the default for every document in the workspace. When you invite someone to your workspace and assign them the Editor role, they can edit all documents in that workspace unless a document-level override says otherwise.

**Document-level permissions** let you override the workspace default for a single playbook or SOP. For example, if most of your team is Editor-level but you have a sensitive HR procedure, you can restrict that specific document to Admins and Viewers only — without changing anyone's workspace role.

<Note>
  Document-level permissions always take precedence over workspace-level permissions for that specific document. A Viewer at the workspace level can be granted Editor access on a single document, and an Editor at the workspace level can be restricted to Viewer access on a sensitive document.
</Note>

## Changing Someone's Role

**To change a workspace role:**

<Steps>
  <Step title="Go to Settings > Members">
    Open **Settings** from the sidebar and select the **Members** tab.
  </Step>

  <Step title="Find the person">
    Locate the team member whose role you want to change. You can search by name or email.
  </Step>

  <Step title="Select a new role">
    Click the role dropdown next to their name and choose the new role. The change takes effect immediately.
  </Step>
</Steps>

**To change a document-level role:**

<Steps>
  <Step title="Open the Share panel">
    Open the playbook or SOP and click **Share** in the top-right corner.
  </Step>

  <Step title="Find the person">
    Locate the person in the list of people with access to this document.
  </Step>

  <Step title="Select a new role">
    Click the role dropdown next to their name and select the new access level. The change applies instantly.
  </Step>
</Steps>

## Removing a Member

**To remove a member from your workspace:**

<Steps>
  <Step title="Go to Settings > Members">
    Open **Settings** from the sidebar and select the **Members** tab.
  </Step>

  <Step title="Find the member">
    Search for the person you want to remove.
  </Step>

  <Step title="Remove them from the workspace">
    Click the **···** menu next to their name and select **Remove from workspace**. Confirm the action in the dialog that appears.
  </Step>
</Steps>

<Note>
  Removing a member from the workspace revokes their access to all workspace documents immediately. Any playbooks or SOPs they created remain in the workspace and are reassigned to the workspace Admin. Their comments and edit history are preserved in the document timeline.
</Note>

<Warning>
  Admins can remove other Admins from the workspace. However, only the **workspace owner** can remove the last remaining Admin. This safeguard prevents a workspace from being left without anyone who can manage members and settings.
</Warning>