[UXPROD-4673] Improve FQM's permission model Created: 24/Jan/24 Updated: 05/Feb/24 |
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Ramsons (R2 2024) |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Kathleen Moore | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Release: | Ramsons (R2 2024) | ||||||||
| Development Team: | Corsair | ||||||||
| PO Rank: | 0 | ||||||||
| RCA Group: | TBD | ||||||||
| Description |
|
Current situation or problem: Once resource/data-level permissions become available, (generic read/write/edit/etc permissions for users/items/loans/etc data instead of the API-level permissions we have now), FQM should respect those permissions transitively. So for example, if someone does a query on Items but doesn't have read permissions for user data, then they wouldn't be able to see the columns containing user data In scope Out of scope Use case(s) Proposed solution/stories Links to additional info Questions |