snapshot: preserve role-aware notification preferences and operational alerts
This commit is contained in:
@@ -79,7 +79,7 @@ Snapshot commit:
|
||||
|
||||
### Phase 1. Product Core Standardization
|
||||
|
||||
Status: next
|
||||
Status: completed
|
||||
|
||||
Purpose:
|
||||
|
||||
@@ -117,8 +117,18 @@ Deliverables:
|
||||
- branding flow
|
||||
- PDF/letterhead override behavior
|
||||
|
||||
Delivered:
|
||||
|
||||
- generic branding model and management UI
|
||||
- shared branding context across shell/auth/pages
|
||||
- configurable favicon, logo, sender display, footer/legal text, and PDF letterhead
|
||||
- company-domain-driven email defaults and validation
|
||||
- platform vs company admin separation for product-level controls
|
||||
|
||||
### Phase 2. App Registry and Navigation
|
||||
|
||||
Status: completed
|
||||
|
||||
Purpose:
|
||||
|
||||
- stop hardcoding app cards and app visibility in the homepage template
|
||||
@@ -129,9 +139,13 @@ Deliverables:
|
||||
- title / subtitle / icon / route / required capability / enabled flag
|
||||
- homepage and navigation driven by registry data
|
||||
- ability to enable/disable apps per deployment
|
||||
- role-based app visibility and section grouping
|
||||
- drag-and-drop ordering with filter-safe behavior
|
||||
|
||||
### Phase 3. Trial Mode Lifecycle
|
||||
|
||||
Status: completed
|
||||
|
||||
Purpose:
|
||||
|
||||
- allow limited-time test environments for demos and sales
|
||||
@@ -145,9 +159,18 @@ Deliverables:
|
||||
- cleanup command / scheduled deletion
|
||||
- DB/media cleanup policy
|
||||
|
||||
Delivered:
|
||||
|
||||
- platform-only trial management UI
|
||||
- shared trial banner and expiry enforcement
|
||||
- integration restriction during trial mode
|
||||
- cleanup/verification management commands
|
||||
|
||||
### Phase 4. New Business Apps
|
||||
|
||||
Only start after phases 1-3 are stable.
|
||||
Status: next
|
||||
|
||||
Only start after phases 1-3 are stable and the workflow regression suite is green.
|
||||
|
||||
Candidate apps:
|
||||
|
||||
@@ -191,22 +214,21 @@ These should move into configuration progressively, not all at once in one risky
|
||||
|
||||
## Immediate Next Slice
|
||||
|
||||
Implement first:
|
||||
Implement next:
|
||||
|
||||
1. `PortalBranding` model
|
||||
2. branding management page
|
||||
3. shared branding context processor
|
||||
4. replace header/logo/title references on:
|
||||
- home
|
||||
- shared header
|
||||
- login/auth pages
|
||||
5. make PDF letterhead configurable
|
||||
1. restore and keep green the onboarding/offboarding regression suite
|
||||
2. extend dynamic onboarding configuration:
|
||||
- field visibility
|
||||
- section visibility
|
||||
- guarded required/optional controls
|
||||
3. remove remaining hardcoded customer/product leakage from docs, fixtures, and fallback assets
|
||||
4. continue security and observability hardening before the next business app
|
||||
|
||||
This is the first productization slice because it gives:
|
||||
This is the next productization slice because it gives:
|
||||
|
||||
- generic portal identity
|
||||
- customer-specific configurability
|
||||
- a cleaner base for every future app
|
||||
- reliable core workflow behavior
|
||||
- safer deployment-neutral product defaults
|
||||
- a configurable onboarding experience for future customers
|
||||
|
||||
## Guardrails
|
||||
|
||||
|
||||
Reference in New Issue
Block a user