api docs: Document can_manage_all_groups final semantics.

This also does the feature level 305 stamp.
This commit is contained in:
Tim Abbott 2024-10-11 16:00:38 -07:00
parent 2b6df48ebb
commit 3554afde36
3 changed files with 12 additions and 11 deletions

View File

@ -31,6 +31,11 @@ format used by the Zulip server that they are interacting with.
* [`PATCH /user_groups/{user_group_id}`](/api/update-user-group): Added * [`PATCH /user_groups/{user_group_id}`](/api/update-user-group): Added
`can_add_members_group` parameter to support changing the user group which `can_add_members_group` parameter to support changing the user group which
can add members to the specified user group. can add members to the specified user group.
* The `can_manage_all_groups` permission now has the natural semantics
of applying to all groups, regardless of the role of the user given
this permission. Since its introduction in feature level 299,
`can_manage_all_groups` had temporarily had unusual semantics
matching those of the original`user_group_edit_policy` setting.
**Feature level 304** **Feature level 304**

View File

@ -34,7 +34,7 @@ DESKTOP_WARNING_VERSION = "5.9.3"
# new level means in api_docs/changelog.md, as well as "**Changes**" # new level means in api_docs/changelog.md, as well as "**Changes**"
# entries in the endpoint's documentation in `zulip.yaml`. # entries in the endpoint's documentation in `zulip.yaml`.
API_FEATURE_LEVEL = 304 # Last bumped for adding `export_type` field. API_FEATURE_LEVEL = 305 # Last bumped for adding can_add_members_group to usergroup.
# Bump the minor PROVISION_VERSION to indicate that folks should provision # Bump the minor PROVISION_VERSION to indicate that folks should provision
# only when going from an old version of the code to a newer version. Bump # only when going from an old version of the code to a newer version. Bump

View File

@ -4395,11 +4395,9 @@ paths:
defining the set of users who have permission to defining the set of users who have permission to
administer all existing groups in this organization. administer all existing groups in this organization.
**Changes**: Semantics to change in Zulip 10.0 (feature **Changes**: Prior to Zulip 10.0 (feature level 305), only users who
level TBD). The original implementation of this setting were a member of the group or had the moderator role or above could
had different semantics, where only users who were a exercise the permission on a given group.
member of the group or had the moderator role or above
could exercise the permission.
New in Zulip 10.0 (feature level 299). Previously the New in Zulip 10.0 (feature level 299). Previously the
`user_group_edit_policy` field controlled the permission `user_group_edit_policy` field controlled the permission
@ -16279,11 +16277,9 @@ paths:
defining the set of users who have permission to defining the set of users who have permission to
administer all existing groups in this organization. administer all existing groups in this organization.
**Changes**: Semantics to change in Zulip 10.0 (feature **Changes**: Prior to Zulip 10.0 (feature level 305), only users who
level TBD). The original implementation of this setting were a member of the group or had the moderator role or above could
had different semantics, where only users who were a exercise the permission on a given group.
member of the group or had the moderator role or above
could exercise the permission.
New in Zulip 10.0 (feature level 299). Previously the New in Zulip 10.0 (feature level 299). Previously the
`user_group_edit_policy` field controlled the permission `user_group_edit_policy` field controlled the permission