53 lines
1.4 KiB
Markdown
53 lines
1.4 KiB
Markdown
# Feature: Workspace Review Workflow
|
|
|
|
## Status
|
|
|
|
Draft
|
|
|
|
## Goal
|
|
|
|
Support workspace-scoped social media content review from content creation through comments, revision, approval, and ready-to-publish handoff.
|
|
|
|
## User Stories
|
|
|
|
- As a social media manager, I want content items grouped by workspace, client, and project so that I can manage review work for multiple accounts.
|
|
- As a client approver, I want one clear place to review content, comment, and approve or request changes.
|
|
- As an account manager, I want notifications and review queues so that work does not stall silently.
|
|
|
|
## Backend Modules
|
|
|
|
- Identity
|
|
- Workspaces
|
|
- Clients
|
|
- Projects
|
|
- ContentItems
|
|
- Assets
|
|
- Comments
|
|
- Approvals
|
|
- Notifications
|
|
|
|
## Frontend Areas
|
|
|
|
- `/app`
|
|
- `/app/workspaces/new`
|
|
- `/app/clients`
|
|
- `/app/projects`
|
|
- `/app/content`
|
|
- `/app/content/:id`
|
|
- `/app/reviews`
|
|
- `/app/settings`
|
|
|
|
## Domain Rules
|
|
|
|
- Workspace is the top-level scoping boundary.
|
|
- Content items belong to a workspace and may belong to a client or project.
|
|
- Comments, approvals, assets, and notifications must remain traceable to the workflow entity they relate to.
|
|
- Ready-to-publish state should come from explicit approval workflow transitions.
|
|
|
|
## Done When
|
|
|
|
- [ ] Workspace access is enforced consistently
|
|
- [ ] Content item lifecycle is documented as a state machine
|
|
- [ ] Approval decisions create traceable notifications/events
|
|
- [ ] Review queue behavior is covered by tasks and validation
|