Skip to content

v4.2: Granular Permission Model #3832

@thorsten

Description

@thorsten

The permission model must support realistic editorial and organizational structures.

Scope

  • Category-based permissions
  • Language-based permissions
  • Separation of read / write / publish permissions

Acceptance Criteria

  • Permissions can be assigned per category
  • Language-specific editing is enforceable
  • Permission evaluation is centralized
  • Performance remains acceptable
  • Missing permissions produce clear errors

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions