User Roles & Permissions in Dyspatch

User permissions control and specify what a user has access to, and which tasks they can perform.

Dyspatch provides two tiers of permissions: organization roles, and workspace access levels. The combination of the permissions assigned to a user will ensure they have the correct visibility, editing access, and controls for their area of expertise.

Organization administrators have full access to all workspaces within an organization. All other organization roles are given access only to the workspaces that they have been added as collaborators.

Roles Overview

Dyspatch offers four key organization roles to grant various levels of access to key areas of the app:


An Org Admin has complete feature capabilities and control. This role is responsible for managing workspaces, content access, and user seats and permissions. They are the only role that can create or delete workspaces.

Admins are added to all workspaces by default, with the “can publish” access level.


An Org Developer is primarily responsible for creating and managing apps, blocks, and themes. They can configure integrations, webhooks, and API keys in the administrative portal, but they cannot create or modify workspaces, users, or teams.

Developers can collaborate on emails for workspaces they have been specifically added to. They can be assigned any access level.


An Org Editor is primarily responsible for creating and collaborating on emails. They can upload images to the organization’s library, and view apps, blocks, and themes. Editors are typically granted “can edit” access in workspaces, and require approval from Org Admins or a collaborator with “can publish” access to publish the emails they have created.

Editors can collaborate on emails for workspaces they have been specifically added to. They can be assigned any access level.


An Org Viewer is a restricted organizational role; they can only view and leave feedback on emails. They cannot see any other part of the Dyspatch app. This role is meant for stakeholders that want to be kept informed, or only want to leave feedback for their teammates.

Viewers can collaborate on emails for workspaces they have been specifically added to. They are defaulted to “can comment” access at all times, no matter which workspace or team they are added to.

The tables below outline in more detail what each organization role is able to accomplish in Dyspatch:


Org Viewer*Org Editor*Org Developer*Org Admin
View & Comment on Emails
Create, Edit, and Delete Emails-
Test Emails-
Export Emails-
Approve Email Drafts-

* Only in Invited Workspace. Permissions for Editors and Developers may differ based on their workspace access level.

Apps, Blocks, Themes & Image Library

Org ViewerOrg EditorOrg OwnerOrg Admin
View Installed Apps-
Configure & Manage Apps--
View Blocks-
Create, Edit & Delete Blocks--
Manage & Organize Blocks--
View Themes-
Create, Edit & Delete Themes--
Assign Blocks to Themes--
Pin Block to Themes--
Image Library
View Image Library-
Upload & Manage Images-

User & Team Management

Org ViewerOrg EditorOrg DeveloperOrg Admin
Manage Users in Organization---
Update User Permission Levels---
Create & Manage Teams---
Create & Manage Workspaces---

Administrative Portal

Org ViewerOrg EditorOrg DeveloperOrg Admin
Create & Manage Integrations--
Generate API Keys--
Create & Manage Webhooks--
Create & Manage Locale Groups--
Manage Billing Details---

Workspace Access Levels

In addition to organization roles, Dyspatch offers more granular control at the workspace-level to suit your teams’ preferred ways of collaborating. Users must be assigned to a workspace to collaborate on emails, and will have the following access levels available:

Can Publish Users with the “can publish” access level are the gatekeeper for their workspace's published content. Their primary responsibilities are to approve email drafts and manage collaborators and approvers in their workspace.

All Admins are assigned as owners by default. Developers and Editors can be granted publishing access as needed.

Can Edit Users with the “can edit” access level are focused on building and managing email content. They can create, edit, and test drafts with the Dyspatch email builder. While they can create content, they require final approval from a user with publishing access, or an Org Admin, to publish their work.

Developers and Editors can create, edit, leave feedback, and submit emails for publishing approval.

Can Comment Users with the “can comment” access level are restricted to viewing and commenting on emails.

Viewers are assigned “can comment” access by default. Developers and Editors can be granted comment-only access as needed.

The table below outlines in more detail what each access level can do in a workspace:

Can CommentCan EditCan Publish
View & Comment on Emails
Preview Email in Mobile/Desktop, HTML/AMP, etc.
Create, Edit & Delete Emails-
Create & Manage Locale Groups-
Generate Litmus Device Tests-
Send Test Emails-
Create Shareable URLs-
Export Emails-
Approve or Reject Drafts✓*/✓**✓*
Publish Email Drafts--

* If a user is added to a workspace as an approver, they will be able to leave feedback and approve or reject a draft that has been submitted for review. They will not be able to publish the draft. Learn more about approval workflows.

** Org Viewers cannot be assigned as approvers in a workspace. This permission only applies to Org Editors and Org Developers where they have “can comment” access level on a workspace.

Updating User Permissions

Managing organization roles

If you are an Org Admin, you can manage user roles on the Users page in the administrative portal.

  1. Select the " 3 dot " menu icon for a given user, and select the “Edit User Settings” option from the dropdown menu.
  2. Select one of the four organization roles in the “Organization Role” dropdown field.

Managing workspace access

If you are an Org Admin, or you have the “can publish” access level on a workspace, you can manage all of the workspace’s user permissions.

From the administrative portal:

  1. On the Workspaces page, select the " 3 dot " menu icon for a given workspace, and select the “Collaborators” option from the dropdown menu.
  2. On the collaborator modal, set the access level for each individual user or team.

From a workspace page:

  1. On a workspace page, select the “View Collaborators” button.
  2. On the collaborator modal, set the access level for each individual user or team.
search icon

Didn't find what you're looking for?

Ask our support team, we're here to help!

Contact Support