docs(cannamanage): update wiki pages and sprint plans + brand pipeline doc

2026-06-11 09:02:14 +02:00
parent bf721c1379
commit 17d14aae09
8 changed files with 2181 additions and 162 deletions
@@ -464,4 +464,41 @@

 ---

+## Could Have — v2 (Additions)
+
+### US-026: Staff Member Management
+
+**As a** Club Admin, **I want to** create staff accounts with configurable permissions, **so that** my team members can do their work without having access to data they don't need (DSGVO principle of least privilege).
+
+**Priority:** Must Have (upgraded from Could Have — see note)
+**Acceptance Criteria:**
+- [ ] AC1: Admin can create staff accounts with email + temporary password
+- [ ] AC2: Admin assigns permissions per staff account from a defined permission set (`RECORD_DISTRIBUTION`, `VIEW_MEMBER_LIST`, `VIEW_MEMBER_QUOTA`, `ADD_MEMBER`, `VIEW_STOCK`, `RECORD_STOCK_IN`, `VIEW_COMPLIANCE_REPORT`, `MANAGE_GROW_CALENDAR`)
+- [ ] AC3: Pre-created role templates available: **Ausgabe** (distribution desk), **Lager** (stock/cultivation), **Vorstand** (board member)
+- [ ] AC4: Staff accounts cannot access billing, club settings, or staff management
+- [ ] AC5: All distributions recorded by staff include `recorded_by = staffUserId` in audit trail
+- [ ] AC6: Admin can deactivate a staff account; historical data is retained for audit purposes
+- [ ] AC7: Staff member sees only the navigation sections permitted by their granted permissions
+
+> **Note:** Promoted to core / Must Have. Staff management is not a v2 feature — clubs have multiple people involved from day one. DSGVO requires that each person only accesses data relevant to their function. Designing this post-MVP would require schema, API, and permission model rework.
+
+---
+
+### US-027: Grow Calendar
+
+**As a** Club Admin or authorised staff member, **I want to** maintain a cultivation calendar for each grow cycle, **so that** the club has a central record of what was planted, when to expect harvest, and the grow diary with notes and photos.
+
+**Priority:** Could Have (v2)
+**Acceptance Criteria:**
+- [ ] AC1: Admin/staff can create a grow entry with: strain name, planted date, expected harvest date, grow medium, notes
+- [ ] AC2: Grow entries are linked to a batch — when the harvest is registered as a batch, the grow entry is marked as completed
+- [ ] AC3: A grow diary allows adding timestamped notes and optional photos per grow entry
+- [ ] AC4: Grow calendar view shows a visual timeline of active grow cycles (Gantt-style or calendar grid)
+- [ ] AC5: Admin can set who has access to the grow calendar via staff permission `MANAGE_GROW_CALENDAR`
+- [ ] AC6: Photos are stored per-tenant and never exposed to members or other tenants
+
+**Notes:** The grow calendar bridges cultivation management and compliance — it provides provenance traceability from seed/clone to distributed batch. This directly supports §26 CanG batch traceability requirements for the origin of cultivated product. Photo attachments are a nice-to-have within this story; the core diary functionality is the v2 deliverable.
+
+---
+
 *Source: [STRATEGY.md](../STRATEGY.md) | Related: [01-PROJECT-CHARTER.md](./01-PROJECT-CHARTER.md)*