Ebbe BaßandClaude Sonnet 5.5
24de5878ed
Includes the BMAD install config, the initiative ticket tree, the portal context-resources scripts, and the .gitignore change that tracks BMAD files (generated _bmad/render/ is ignored). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Sk72AxLwQnYttF6VFSxQLt
48 lines
2.5 KiB
Markdown
48 lines
2.5 KiB
Markdown
---
|
|
tracker_id: ""
|
|
key: ""
|
|
type: epic
|
|
title: "The admin announces changes and runs the portal"
|
|
parent: initiative-ping-mee-portal
|
|
covers: [CAP-5, CAP-6, CAP-7, CAP-8, CAP-10]
|
|
after: []
|
|
assignee: ""
|
|
risk: medium
|
|
---
|
|
|
|
# The admin announces changes and runs the portal
|
|
|
|
## Description
|
|
|
|
Publishers announce planned downtime and changes, users receive them by e-mail and see them on the dashboard, and the Admin manages the look, reads the audit log and watches the status of backups, mail and background jobs. It finishes the portal and proves it ready for the internet.
|
|
|
|
## Outcome
|
|
|
|
Every planned downtime reaches opted-in users by e-mail and banner, and the admin can see that the portal is healthy; the second part of the spec's success signal.
|
|
|
|
## Done when
|
|
|
|
1. A Publisher writes an announcement with an always-set severity and optional window, expiry and schedule, and it appears as a banner and in the list at the right time.
|
|
2. Every user in the OU with a valid e-mail address and no opt-out receives it, and the Publisher sees counts and reasons beforehand.
|
|
3. The dashboard shows active announcements and the account card including the password date.
|
|
4. The Admin changes the accent colour with a contrast warning, uploads a background, edits settings, reads the audit log and sees backup age, failed e-mails and job runs.
|
|
5. Consistent backup files appear on schedule, the nightly AD reconciliation runs, and audit retention applies.
|
|
6. Security tests (injection, cross-user, throttling, sessions) and the accessibility pass succeed, and a smoke checklist exists for the test OU.
|
|
|
|
## Boundaries
|
|
|
|
Announcements, announcement e-mail, the dashboard, the Admin pages, the maintenance jobs and the final hardening. Not account features (epic-account-self-service). Touch point owned here: the Veeam copy job that copies the backup folder.
|
|
|
|
## References
|
|
|
|
- parent — _bmad-output/initiative-ping-mee-portal/initiative-ping-mee-portal.md, section Requirements
|
|
- spec — _bmad-output/specs/spec-ping-mee-self-service-platform/SPEC.md, CAP-5, CAP-6, CAP-7, CAP-8, CAP-10
|
|
- architecture — ARCHITECTURE-SPINE.md, AD-4, AD-11 to AD-16
|
|
- design — DESIGN.md and EXPERIENCE.md; mock-ups key-announcement-editor.html, key-admin-appearance.html, key-admin-status.html, key-admin-audit.html, key-dashboard.html
|
|
- constraint — SPEC.md, section Constraints
|
|
|
|
## Notes
|
|
|
|
- Waits on epic-account-self-service because: the dashboard account card shows picture status and uses the profile data it creates.
|
|
- Not yet sliced: this epic is broken into stories when it is selected.
|