DM Portal App

App: apps/dm · **Port: 3002 · Audience: Internal digital marketing team and HITL reviewers

The DM Portal is the internal-facing interface for the agency’s own team. Reviewers use it to manage work across all tenants simultaneously — approving agent outputs, intervening in pipelines, raising ad-hoc requests, and monitoring the health of all active campaigns.

Status

Contents

Key Screens

Key Behaviours

• Cross-tenant — A reviewer sees all assigned tenants in one queue, not one at a time
• HITL enforcement — No agent output is published without passing through this portal’s approval flow
• Bulk actions — Reviewers can approve/reject multiple items at once
• Live streaming — Activity output streams in real time (SSE) during agent execution
• Rejection feedback — Reviewer notes on a rejection are appended to the agent’s prompt on retry

Tech

• Framework: Next.js 15 (App Router)
• Auth: Cookie-based (dm_access_token / dm_refresh_token). Calls /auth/v1/login with app: "dm". JWT verified server-side in (dm)/layout.tsx. Roles allowed: reviewer, admin, super_admin.
• Theming: next-themes — Light / Dark / System, three-way cycle toggle in topbar. CSS tokens via Tailwind v4 @theme inline.
• Real-time: Socket.IO — agent:event for live agent monitoring. SSE planned: GET /dm/v1/activities/:id/stream.
• API prefix: /dm/v1 — scope-aware access control via requireDMAccess (allows reviewer, admin, super_admin).
  • GET /dm/v1/users — TenantMember-based; per-tenant or all accessible tenants
  • GET /dm/v1/agents — all active agentConfig rows (read-only)
  • POST /dm/v1/tenant/switch — validates access + writes tenant.switched audit log
  • GET /dm/v1/context — client context with status and change log (in calendar.ts)
  • POST /dm/v1/context/revise — trigger context regeneration (enqueues context-file-writer)
  • GET /dm/v1/strategy — strategy + versions + change log
  • POST /dm/v1/strategy/status — change status (draft/pending_review/rejected only)
  • POST /dm/v1/strategy/revise — trigger strategy regeneration (enqueues strategy-writer)
  • GET /dm/v1/goals — goals with current-period activity progress
  • GET /dm/v1/goals/archived — archived deliverable plans with their goals
  • GET /dm/v1/deliverables — templates + per-item Deliverable rows + inProgress counts
  • GET /dm/v1/deliverable-plan — plan with goals, templates, strategyStatus
  • GET /dm/v1/channels/health-summary?tenantId= — channel health overview (includes pendingSuggestionsCount per channel)
  • GET /dm/v1/channel-action-items?tenantId=&channelId= — list action items for a channel
  • GET /dm/v1/channel-action-items/channel-info?tenantId=&channelId= — channel metadata + latest insight
  • POST /dm/v1/channel-action-items/generate — trigger action suggestion generation
  • PATCH /dm/v1/channel-action-items/:id/status — approve / dismiss / done
  • POST /dm/v1/channel-action-items/:id/execute — execute approved item → Activity + agent queue
• Tenant switching: Sidebar SidebarTenantSwitcher — mandatory, no “All Tenants” option. “Switch client” label hidden when only 1 tenant. Sets dm_active_tenant + dm_active_tenant_name cookies via POST /api/tenant/switch (which calls /dm/v1/tenant/switch for audit logging). Tenant list from GET /auth/v1/me/tenants.
• Tenant gate: Layout blocks page content if no tenant selected. Auto-selects via /api/tenant/auto-select if only 1 tenant. Shows “Select a client to continue” if multiple tenants and none chosen.
• Related API doc: api/dm.md