Actions
User Story #279
open
Epic #49: Implement user, groups and permissions management
Feature #266: Roles
As an administrator, I want to create, edit and delete roles, so that I can describe access once and reuse it
User Story #279:
As an administrator, I want to create, edit and delete roles, so that I can describe access once and reuse it
Start date:
Due date:
% Done:
0%
Estimated time:
Description
A role is a named set of permissions picked from the catalog. It can name whole families at once, for example everything a module offers, so that a role does not silently fall behind when that module gains a capability.
Acceptance criteria
- A role has a name and a set of permissions chosen from the catalog
- A role can include a whole namespace or resource rather than listing every permission
- A role is marked as usable platform-wide, on a single object, or both, and cannot be given in the wrong place
- Editing a role changes what its holders can do immediately
- Deleting a role warns when it is in use and removes the access it granted
- Roles are listed and searchable
Rejection reason
Superseded by the rewritten epic #49
Updated by
Actions