help: Update permissions docs for group-based permissions.

help/custom-emoji.md

@@ -64,9 +64,9 @@ administrators can deactivate anyone's custom emoji.
 
 {!admin-only.md!}
 
-By default, anyone other than guests can [add custom emoji](/help/custom-emoji)
-to the organization. However, you can restrict the ability to do so to specific
-[roles](/help/user-roles).
+You can configure who can add custom emoji. This permission can be granted to
+any combination of [roles](/help/user-roles), [groups](/help/user-groups), and
+individual [users](/help/manage-a-user).
 
 {start_tabs}
 

help/restrict-direct-messages.md

@@ -10,9 +10,12 @@ messages](/help/direct-messages):
   or someone else).
 - Who can **start** a direct message conversation.
 
-These settings are designed so that users can always respond to a direct message
-they've received (unless organization permissions change). They also provide a
-lot of flexibility for managing DMs in your organization. For example, you can:
+These permissions can be granted to any combination of
+[roles](/help/user-roles), [groups](/help/user-groups), and individual
+[users](/help/manage-a-user). They are designed so that users can always respond
+to a direct message they've received (unless organization permissions change).
+They also provide a lot of flexibility for managing DMs in your organization.
+For example, you can:
 
 - Prevent 1:1 DMs between [guest users](/help/guest-users).
 - Allow members to respond to DMs from an admin or moderator, but not to start

help/restrict-message-editing-and-deletion.md

@@ -4,12 +4,10 @@
 
 Zulip lets you separately configure permissions for editing and deleting
 messages, and you can set time limits for both actions. Regardless of the
-configuration you select:
+configuration you select, message content can only ever be modified by the
+original author.
 
-* Message content can only ever be modified by the original author.
-* Any message can be deleted at any time by an organization administrator.
-
-Note that if a user can edit a message, they can also "delete" it by removing
+Note that if a user can edit a message, they can also “delete” it by removing
 all the message content. This is different from proper message deletion in two
 ways: the original content will still show up in [message edit
 history](/help/view-a-messages-edit-history), and will be included in
@@ -36,6 +34,10 @@ irretrievably) removes the message from Zulip.
 
 ## Configure message deletion permissions
 
+These permissions can be granted to any combination of
+[roles](/help/user-roles), [groups](/help/user-groups), and individual
+[users](/help/manage-a-user).
+
 {start_tabs}
 
 {settings_tab|organization-permissions}

help/restrict-moving-messages.md

@@ -2,9 +2,13 @@
 
 {!admin-only.md!}
 
-Zulip lets you configure which [roles](/help/user-roles) can edit
-message topics and move topics between channels. In general, allowing all
-organization members to edit message topics is highly recommended because:
+Zulip lets you configure who can edit message topics and move topics between
+channels. These permissions can be granted to any combination of
+[roles](/help/user-roles), [groups](/help/user-groups), and individual
+[users](/help/manage-a-user).
+
+In general, allowing all organization members to edit message topics is highly
+recommended because:
 
 - It allows the community to keep conversations organized, even if some members
   are still learning how to use topics effectively.

help/restrict-wildcard-mentions.md

@@ -9,6 +9,9 @@ allowed to use `@all` (and, equivalently, `@everyone` and `@channel`) in channel
 with more than 15 subscribers, and `@topic` in topics with more than 15
 participants.
 
+This permission can be granted to any combination of [roles](/help/user-roles),
+[groups](/help/user-groups), and individual [users](/help/manage-a-user).
+
 {start_tabs}
 
 {settings_tab|organization-permissions}