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.
Key Technical Questions
- Can we filter by "Scope" and still return a correct "Assignment Count" at the user level in a single query?
- Should we implement a lazy-loading approach for the "Expanded" view?
- What is the impact on pagination when grouping results by user?
Resource
Design: https://www.figma.com/design/onU2END2OXaF7RRLWEHsZI/AuthZ---v2?node-id=7480-15473&t=vd1RV9X7ew93eodw-0
Related #281
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
Key Technical Questions
Resource
Design: https://www.figma.com/design/onU2END2OXaF7RRLWEHsZI/AuthZ---v2?node-id=7480-15473&t=vd1RV9X7ew93eodw-0
Related #281