Technical Feasibility: Grouped Roles & Permissions View (Backend/API Strategy)

[MaferMazu]

Description
Problem Statement
The new design proposes grouping roles and permissions by user, introducing two states: Collapsed (summary count) and Expanded (detailed scope/assignments).

Currently, our API returns a flat list. Transitioning to a grouped structure poses a challenge for filtering (especially by Organization or Scope). If the initial query only returns counts for the collapsed view, filtering by specific assignment details may require expensive joins or multiple API calls, potentially impacting performance.

Objectives

• Analyze Data Fetching: Determine if the current API can support filtering on nested data without returning the entire payload.
• Filter Consistency: Evaluate how to apply "Organization" and "Scope" filters in the collapsed view while maintaining accurate result counts.
• Performance Check.

Resource
Design: https://www.figma.com/design/onU2END2OXaF7RRLWEHsZI/AuthZ---v2?node-id=7480-15473&t=vd1RV9X7ew93eodw-0

Related #281

[MaferMazu]

It is possible to filter the info (by scope, org, and role); besides, we didn't have the info in the front. It is how it is done right now. When we filter, we pass as params and create a new request to the backend to obtain the filtered info.

The strategy will be to have a first request to obtain the base info, and then, when we filter, we make another request; and if I want detailed info, I make another one (paginated); but we still need to define things there, for example: are we going to show all the info or only the one related to the filter?

We still need to define the details, but in general, it is possible and a good practice.

cc @gviedma-aulasneo