Project

General

Profile

Actions

Feature #139

closed

Epic #49: Implement user, groups and permissions management

How are permissions defined in the system?

Feature #139: How are permissions defined in the system?

Added by Bricklou 6 months ago. Updated 9 days ago.

Status:
Rejected
Priority:
Normal
Assigned To:
-
Target version:
-
Start date:
03/28/2026
Due date:
% Done:

0%

Estimated time:

Description

Open question: What is the permission model?

  • Is it a flat list of granular permissions (e.g., 'user.create', 'user.delete', 'report.view')?
  • Are they hierarchical/scoped (e.g., by resource type, module)?
  • Who can define new permissions—admins or developers only?
  • Are they hardcoded or database-driven?
  • What's the permission model—RBAC (role-based), ABAC (attribute-based), ACL-based?

This affects the implementation of features #127, #52, #54, #59, #60


Rejection reason

Answered by the permission model specification

Updated by Bricklou 6 months ago Author Actions #1

  • Tracker changed from Epic to Feature

Updated by Bricklou 6 months ago Author Actions #2

  • Status changed from Draft to To Do

Updated by Bricklou 6 months ago Author Actions #3

  • Status changed from To Do to Draft

Updated by Bricklou 9 days ago Author Actions #4

  • Status changed from Draft to To Do

Updated by Bricklou 9 days ago Author Actions #5

  • Status changed from To Do to Draft

Updated by Bricklou 9 days ago Author Actions #6

  • Status changed from Draft to To Do

Updated by Bricklou 9 days ago Author Actions #7

  • Status changed from To Do to Rejected
  • Rejection reason updated (diff)

Superseded by the rewritten epic #49

Updated by Bricklou 9 days ago Author Actions #8

  • Status changed from Rejected to To Do

Updated by Bricklou 9 days ago Author Actions #9

  • Status changed from To Do to Rejected
  • Rejection reason updated (diff)

Answered. The model is role-based with named permissions and per-object grants, contributed by the platform and by modules, stored rather than hardcoded. See #49 and the permission model specification; the catalog itself is #265.

Actions

Also available in: PDF Atom