Skip to content

US‑E4‑01 – Rollenbasierte Zugriffe #5

@mvk-abs

Description

@mvk-abs

User Story
Als IT‑Security Officer möchte ich rollenbasierte Zugriffsrechte auf die Eventdaten verwalten, um unbefugte Änderungen zu verhindern.

**Akzeptanzkriterien**  
```gherkin
Feature: Role‑based Access
  Scenario: Viewer cannot edit
    Given the user has role "Event Viewer"
    When the user attempts to edit the event title
    Then the system returns HTTP 403 Forbidden
```

**UI Notes**  
- CAP App Router → XSUAA Role Collections (Viewer, Editor, Admin).  
- UI5 hides edit buttons when role ≠ Editor/Admin.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions