Actions
User Story #294
open
Epic #49: Implement user, groups and permissions management
Feature #270: Understanding access
As the owner of a server, I want to see who has access to it and how, so that I can tell whether it is shared more widely than I thought
User Story #294:
As the owner of a server, I want to see who has access to it and how, so that I can tell whether it is shared more widely than I thought
Start date:
Due date:
% Done:
0%
Estimated time:
Description
The reverse question matters as much as the forward one: not "what can this person do" but "who can touch this".
Acceptance criteria
- One view per object lists everyone who has access to it
- Each entry says how: directly, through a group, or from further away
- Denials placed on the object are shown too
- Administrators are shown as always having access
- The view stays usable on an object shared with many people
Rejection reason
Superseded by the rewritten epic #49
Updated by
Actions