help: Update documentation for add_custom_emoji_policy.

This commit is contained in:
sahil839 2021-05-17 23:43:38 +05:30 committed by Tim Abbott
parent b8854a9d92
commit 0d6f378ad7
8 changed files with 18 additions and 7 deletions

View File

@ -4,7 +4,7 @@ By default, anyone other than guests can add custom emoji to a Zulip organizatio
are available to all users.
Organization administrators can also
[change who can add custom emoji](/help/only-allow-admins-to-add-emoji).
[change who can add custom emoji](/help/configure-who-can-add-custom-emoji).
## Add custom emoji
@ -57,4 +57,4 @@ administrators can delete anyone's custom emoji.
## Related articles
* [Change who can add custom emoji](/help/only-allow-admins-to-add-emoji)
* [Change who can add custom emoji](/help/configure-who-can-add-custom-emoji)

View File

@ -3,8 +3,13 @@
{!admin-only.md!}
By default, anyone other than guests can [add custom emoji](/help/add-custom-emoji) to the
organization. However, you can change your organization's settings to only
allow administrators to add new emoji.
organization. However, you can restrict the permission to add custom emoji to other sets of
roles:
* Organization administrators
* Organization administrators and moderators
* Organization administrators and all members
* Organization administrators and [full members](/help/restrict-permissions-of-new-members)
### Change who can add custom emoji

View File

@ -130,7 +130,7 @@
* [Restrict user group management](/help/restrict-user-group-management)
* [Restrict name and email changes](/help/restrict-name-and-email-changes)
* [Restrict profile picture changes](/help/restrict-profile-picture-changes)
* [Change who can add custom emoji](/help/only-allow-admins-to-add-emoji)
* [Change who can add custom emoji](/help/configure-who-can-add-custom-emoji)
* [Block image and link previews](/help/allow-image-link-previews)
* [Disable message edit history](/help/disable-message-edit-history)
* [Manage editing of old messages](/help/configure-message-editing-and-deletion)

View File

@ -14,7 +14,7 @@ problematic behavior:
* Restrict who can [create streams](/help/configure-who-can-create-streams),
[create bots](/help/restrict-bot-creation), [send private
messages](/help/restrict-private-messages), or
[add custom emoji](/help/only-allow-admins-to-add-emoji).
[add custom emoji](/help/configure-who-can-add-custom-emoji).
* Link to a code of conduct in your
[organization description](/help/create-your-organization-profile)
(displayed on the registration page).

View File

@ -18,6 +18,7 @@ Currently, the following actions support limiting access to full members.
- [Adding users to streams](/help/configure-who-can-invite-to-streams)
- [Restricting posting to a stream](/help/stream-sending-policy)
- [Restricting inviting users to organization](/help/invite-new-users)
- [Restricting adding custom emoji](/help/configure-who-can-add-custom-emoji)
### Set waiting period for new members

View File

@ -53,7 +53,7 @@ priority.
- Zulip also supports customizing whether non-admins can
[create streams](/help/configure-who-can-create-streams),
[invite to streams](/help/configure-who-can-invite-to-streams),
[add custom emoji](/help/only-allow-admins-to-add-emoji),
[add custom emoji](/help/configure-who-can-add-custom-emoji),
[add integrations and bots](/help/restrict-bot-creation),
[edit or delete messages](/help/configure-message-editing-and-deletion),
and more.

View File

@ -469,6 +469,7 @@ def write_instrumentation_reports(full_suite: bool, include_webhooks: bool) -> N
"help/community-topic-edits",
"help/delete-a-stream",
"for/working-groups-and-communities/",
"/help/only-allow-admins-to-add-emoji",
"api/delete-stream",
"casper/(?P<path>.+)",
"static/(?P<path>.+)",

View File

@ -768,6 +768,10 @@ urls += [
"help/community-topic-edits",
RedirectView.as_view(url="/help/configure-who-can-edit-topics", permanent=True),
),
path(
"/help/only-allow-admins-to-add-emoji",
RedirectView.as_view(url="/help/configure-who-can-add-custom-emoji", permanent=True),
),
path("help/", help_documentation_view),
path("help/<path:article>", help_documentation_view),
path("api/", api_documentation_view),