Actions
Feature #270
open
Epic #49: Implement user, groups and permissions management
Understanding access
Feature #270:
Understanding access
Start date:
Due date:
% Done:
0%
Estimated time:
(Total: 0:00 h)
Description
A permission system nobody can explain becomes a system nobody trusts. With denials in play, "why can this person do that" and "why can't they" must both be answerable without reading the database.
An administrator can see everything a person can do and where each of those came from, ask why one specific action was allowed or refused for one person on one object, and see who has access to a given object and through what. The interface only offers people the actions they can actually perform, while the server still checks every request.
Rejection reason
Superseded by the rewritten epic #49
Updated by
Actions