diff --git a/docs/sources/permissions/organization_roles.md b/docs/sources/permissions/organization_roles.md
index 5998c681be5..2e701b732a7 100644
--- a/docs/sources/permissions/organization_roles.md
+++ b/docs/sources/permissions/organization_roles.md
@@ -1,6 +1,6 @@
 +++
-title = "Organization Roles"
-description = "Grafana Organization Roles Guide "
+title = "Organization roles"
+description = "Grafana organization roles guide "
 keywords = ["grafana", "configuration", "documentation", "organization", "roles", "permissions"]
 type = "docs"
 [menu.docs]
@@ -10,32 +10,42 @@ parent = "permissions"
 weight = 30
 +++
 
-# Organization Roles
+# Organization roles
 
 Users can belong to one or more organizations. A user's organization membership is tied to a role that defines what the user is allowed to do
 in that organization.
 
-## Admin Role
+## Admin role
 
 Can do everything scoped to the organization. For example:
 
-- Add and Edit data sources.
-- Add and Edit organization users and teams.
-- Configure App plugins and set org settings.
+- Can add, edit, and delete data sources.
+- Can add and edit users and teams in organizations.
+- Can configure app plugins and organization settings.
+- Can do everything allowed by the Editor role.
 
-## Editor Role
+## Editor role
 
-- Can create and modify dashboards and alert rules. This can be disabled on specific folders and dashboards.
-- **Cannot** create or edit data sources nor invite new users.
+- Can view, add, and edit dashboards, panels, and alert rules in dashboards they have access to. This can be disabled on specific folders and dashboards.
+- Can create, update, or delete playlists.
+- Can access Explore.
+- Cannot add, edit, or delete data sources.
+- Cannot add, edit, or delete alert notification channels.
+- Cannot manage other organizations, users, and teams.
 
-This role can be tweaked via Grafana server setting [editors_can_admin]({{< relref "../administration/configuration.md#editors_can_admin" >}}). If you set this to true users
-with **Editor** can also administrate dashboards, folders and teams they create. Useful for enabling self organizing teams.
+This role can be tweaked via Grafana server setting [editors_can_admin]({{< relref "../administration/configuration.md#editors_can_admin" >}}). If you set this to `true`, then users
+with the Editor role can also administrate dashboards, folders and teams they create. This is especially useful for enabling self-organizing teams to administer their own dashboards.
 
-## Viewer Role
+## Viewer role
 
-- View any dashboard. This can be disabled on specific folders and dashboards.
-- **Cannot** create or edit dashboards nor data sources.
+- Can view any dashboard they have access to. This can be disabled on specific folders and dashboards.
+- Cannot add, edit, or delete data sources.
+- Cannot add, edit, or delete dashboards or panels.
+- Cannot create, update, or delete playlists.
+- Cannot add, edit, or delete alert notification channels.
+- Cannot access Explore.
+- Cannot manage other organizations, users, and teams.
 
-This role can be tweaked via Grafana server setting [viewers_can_edit]({{< relref "../administration/configuration.md#viewers-can-edit" >}}). If you set this to true users
-with **Viewer** can also make transient dashboard edits, meaning they can modify panels and queries but not save the changes (nor create new dashboards).
-Useful for public Grafana installations where you want anonymous users to be able to edit panels and queries but not save or create new dashboards.
+This role can be tweaked via Grafana server setting [viewers_can_edit]({{< relref "../administration/configuration.md#viewers-can-edit" >}}). If you set this to `true`, then users
+with the Viewer role can also make transient dashboard edits, meaning they can modify panels and queries but not save the changes (nor create new dashboards).
+This is especially useful for public Grafana installations where you want anonymous users to be able to edit panels and queries but not save or create new dashboards.