Problem Definition

In Confluence 9.2, non-Confluence Admin users (like Space Administrators, for example) can no longer call /rest/api/group/<GROUP_NAME>/member. A 400-level error occurs.

Suggested Solution

Allow Space Administrators to make this REST call for groups that have permission to view and add content to that space.

Why This Is Important

Here are a couple of scenarios to justify the critical need for Atlassian to reinstate the feature allowing users to list group members via a REST API call:

Scenario 1: Dynamic Approval Workflows for Customer Sub-Teams

A software development team that supports four distinct customer sub-teams. To streamline their support process, they've implemented a unified Jira ticket portal. However, the approval workflow for each ticket needs to be dynamically routed to a specific approver group based on which customer sub-team the request originates from.

Our users need the ability to:

Programmatically assign approver groups: They want to set the approvers for a Jira ticket to a specific group that they own and manage. This assignment needs to happen automatically, triggered by a webhook call to Confluence (where these groups are defined and managed). Without the ability to list group members via REST, they cannot reliably identify and assign the correct group based on the sub-team's context.

Scenario 2: Enhanced User Experience (UX) for Customer Identification

Consider a user experience goal to automatically detect which customer sub-team is making a request, rather than forcing the requester to manually fill out a field (e.g., "Which sub-team do you represent?"). This provides a much smoother and more efficient experience for the end-user.

To achieve this, our users need the ability to:

Verify group membership via API: They want to check if a specific user (the requester in this case) is a member of one or more known customer sub-teams (represented by Confluence groups). This real-time check, performed through a REST API call, would allow the system to automatically categorize the request and route it appropriately, significantly improving the user's interaction and reducing friction.

In both these scenarios, the absence of a REST API to list group members creates significant roadblocks, forcing teams into inefficient manual processes or compromising the desired user experience. Reinstating this functionality would be a substantial improvement for our users' ability to build robust and automated workflows within the Atlassian.

Workaround

Make this call with a user who is a member of the confluence-administrators group.