Actions
User Story #286
open
Epic #49: Implement user, groups and permissions management
Feature #268: Granting access
As the owner of a server, I want to deny one capability to one person, so that they keep the rest of the access their team has
User Story #286:
As the owner of a server, I want to deny one capability to one person, so that they keep the rest of the access their team has
Start date:
Due date:
% Done:
0%
Estimated time:
Description
A team may have access to a set of servers while one person must be kept away from one thing on one of them. Removing them from the team is too blunt.
Acceptance criteria
- A denial can be placed on an object for a person or a group
- A denial names individual capabilities; it can never say "everything of this kind"
- A denial on an object overrides access that came from further away
- Where an allowance and a denial meet in the same place, the denial wins, and naming the person directly outranks naming a group they belong to
- Someone holding the Administrator role is never denied
- The interface shows three distinct states — allowed, denied, not set — and never conflates the last two
Rejection reason
Superseded by the rewritten epic #49
Updated by
Actions