Actions
User Story #293
open
Epic #49: Implement user, groups and permissions management
Feature #270: Understanding access
As an administrator, I want to ask why one person was allowed or refused one action, so that I can fix access instead of guessing
User Story #293:
As an administrator, I want to ask why one person was allowed or refused one action, so that I can fix access instead of guessing
Start date:
Due date:
% Done:
0%
Estimated time:
Description
With denials and inheritance in play, "they should be able to do this but can't" is the question that will be asked most often. It has to be answerable without reading the database.
Acceptance criteria
- An administrator can ask whether a given person may perform a given action on a given object
- The answer names what decided it: which grant, in which place, addressed to the person or to which group
- A refusal distinguishes "explicitly denied" from "never granted"
- The answer reflects the same rules the platform enforces, not a separate calculation
Rejection reason
Superseded by the rewritten epic #49
Updated by
Actions