Skip to main content

Ops Workspace — Zij, Support & Product Updates (Admin)

Audience: Ops · Support · Engineering · Where in app: Admin sidebar → Ops → Zij (opens /admin/ops/zij in a new tab); the workspace has its own layout (OpsWorkspaceLayout.vue) with Zij · Dev board, Support inbox, Roadmap triage, Announcements, Approvals, Ops overview · Access: see Access.

The ops workspace is the internal tooling built in October–November 2026: a dev board (Zij), the support ticket inbox (in-app, email, agency and Nox hand-off tickets), the public roadmap's triage queue, and the product-updates pipeline that turns a released Zij card into emails, in-app notifications, a changelog post and a release video.

All /ops/* backend routes live in backend/app/routes/opsRoutes.js and are gated by app/middlewares/opsAuth.js. OPS_ENABLED=false (default on) turns every ops route — including the tenant ticket endpoints — into a 404.

Access​

WhoWhat they get
Full super admin (user_type: 'admin', no admin_access.limited)Everything, including Zij Team, the support inbox, roadmap triage, and anything that runs on the worker PC.
Admin staff (admin_access.limited: true)Only with the Ops & Zij section (ops) ticked on Team. Support inbox and roadmap triage stay super-admin only.
Developer (user_type: 'ops_dev')Only the Zij board, at /ops (OpsLayout) — never /admin. Invited from Zij → Team (7-day set-password link).
Ops AI agentsx-ops-agent: <name> (intake, triage, scrum, release, docs, ops_watch) plus x-api-key = BACKEND_API_KEY.

Zij — dev board (/admin/ops/zij)​

Tabs: Board, Table, My tasks, Scrum notes, Team (full super admin), Import from Asana (admin).

  • Stages (ops_stages: name, position, customer_stage, color, wip_limit): built-in ideas / planned / building / qa / released plus custom stages. Cards (ops_cards, keys ZJ-n) also have an announce stage that feeds product updates. New cards and unmapped Asana sections land in the first column that isn't Released.
  • Table (ZijTable): views "All open", "My open", "Unassigned", "Updated recently", "Done", "All"; search, bulk Archive cards, CSV export (zij-cards-YYYY-MM-DD.csv).
  • Descriptions are rich text with pasted images (POST /ops/cards/:id/images).
  • Link previews: GET /share/zij/:id (no login) exposes only key, type, stage and priority so a shared link unfurls without leaking the card.
  • Asana import: the browser parses Asana's CSV export and posts to POST /ops/import/asana; tasks already imported are skipped by asana_task_id.
  • Scrum notes: ops_scrum_notes (date, author, items), CRUD at /ops/scrum-notes.
  • The Module picker was removed (43bee1a3).

Support tickets​

Collections​

  • ops_tickets — number (KK-n), channel (email | inapp | admin | agency | nox), handled_by (team | agency), status (open | waiting_customer | waiting_fix | resolved), priority (P1–P3, default P3), category (how_to | billing | bug | feature | account | other), account (kind direct/agency/sub_account + ids + tier), reply_route (client | agency | both), knock_knock_sent_at / knock_knock_ticket_id (escalation link), status_token (public status page), auto_close_at, card_id (linked Zij card).
  • ops_ticket_messages — kind (customer | team | system | forward_note | internal_note), body/body_html, mentions[] (@mentions in internal notes), attachments[] (local or S3).
  • ops_agent_actions — drafts from the Intake/Triage agents (OpsSupportAgents), approved or rejected on Approvals. Classification is applied directly; anything customer-facing waits for approval. Agency-handled tickets get no AI.

Where tickets come from​

ChannelEntry point
In-app (inapp)Tenant Help & Support page (/support, POST /feedback, multipart, up to 5 images × 8 MB). Type maps to category: bug→bug, suggestion→feature, question→how_to, other→other.
Agency (agency)Agency Help & Support (/agency/support, GET/POST /agency/support-tickets), optionally on behalf of a client.
Email (email)SupportInboxJob (every minute) reads the support mailbox over IMAP and threads by [KK-n] or In-Reply-To/References. Off unless SUPPORT_IMAP_HOST is set (SUPPORT_IMAP_PORT/_USER/_PASSWORD/_TLS, SUPPORT_EMAIL_ADDRESS, SUPPORT_STATUS_BASE_URL). UID cursor in ops_state.
Nox (nox)POST /internal/knox/escalations — a Nox hand-off (billing dispute, refund, account deletion, …) opens a ticket; urgency high → P2. Falls back to email if creation fails.

SupportAutoCloseJob (hourly) resolves waiting_customer tickets past auto_close_at. Customers follow a ticket at /t/:number?token=… (public, rate-limited GET /public/tickets/:number). When a team-handled ticket is resolved, OpsTicketService.learnFromResolved posts the thread to ms-ai POST /knox-v2/internal/product-notes/from-ticket so Nox gets a (reviewed) product note.

Agency client tickets & escalation​

Switch: Admin → Settings → Feature Flags → Agency client tickets (settings key agency_client_tickets; replaced the OPS_AGENCY_CLIENT_TICKETS env var). When on, a managed client's in-app tickets and Nox hand-offs go to its agency — if the agency's client_support.mode is agency ("We handle it" on /agency/settings/client-support; the other options are us and us_copy).

  • Agency UI: Client tickets (/agency/client-tickets, needs agency.manage_clients), status tabs, "Send reply" / "Send and resolve". Notified by bell (client-ticket), socket refresh and email (ops-agency-client-ticket.html).
  • Send to Knock Knock (POST /agency/client-tickets/:id/escalate) claims the client ticket and opens a linked channel: 'agency' ticket in our queue carrying the client's messages and attachments; the client only ever sees "Your support team is working on it".
  • For tickets we answer, the team picks Reply goes to client / agency / both (reply_route).

The tenant Help & Support menu, the agency's Client tickets menu and the Roadmap menu are hidden (frontend/src/common/constants/navVisibility.js: SHOW_SUPPORT_NAV, SHOW_ROADMAP_NAV, SHOW_WHATS_NEW_NAV all false). The routes work; append ?test_support to any URL to show the items in that tab (?test_support=0 hides them).

Claude Code prompts & "Run on my PC"​

Tickets and Zij cards have Prompt for Claude Code (POST /ops/tickets/:id/claude-prompt, /ops/cards/:id/claude-prompt) with "Only find the issue" / "Find and fix it", plus Run on my PC / Find and fix on my PC, which queue an ops_video_jobs row (kind video | investigate | release, mode find | fix — fix leaves uncommitted edits in the local repos). Ticket screens also have Write with Claude (/claude-draft).

The local worker is authenticated by x-video-worker-key = OPS_VIDEO_WORKER_KEY (backend secret; unset → the worker routes 404) and polls POST /ops-worker/video/claim, then PATCH /ops-worker/video/jobs/:id and POST …/result. ops_video_workers.last_seen_at within 60 s = "Worker online"; a running job silent for 15 minutes fails. Only the release worker is in the repo: backend/scripts/release-worker/worker.mjs (OPS_VIDEO_WORKER_KEY=… node scripts/release-worker/worker.mjs; WORKER_API, WORKER_NAME, WORKSPACE, DEMO_URL, DEMO_EMAIL/DEMO_PASSWORD, CLAUDE_BIN, JOB_MINUTES).

Roadmap triage (/admin/ops/triage)​

Public roadmap at /product-roadmap (no login; votes confirmed by email, ops_roadmap_guests), in-app at /roadmap and /agency/roadmap (menu hidden). One vote per account per card (ops_roadmap_votes, account_key agency:/company:/guest:); requests in ops_feature_requests. Voters get "it moved" emails (ops-roadmap-update.html). Triage tabs Queue / Ranking (customer votes, voter MRR, prospects, tickets); actions add to roadmap, decline, move to support, attach to a Zij card. /changelog now redirects to VITE_PUBLIC_CHANGELOG_URL (default the marketing site's changelog; white-label hosts go to /). The Ops overview page has the roadmap link and iframe embed code.

Product updates pipeline​

Announcements (/admin/ops/announcements): tabs "Waiting for approval" / "Sent" / "Discarded"; editor tabs "Content" / "Recipients & send"; audiences "Agency resellers", "Direct customers", "Agency clients"; channels "Email", "Notification in the app", "Public changelog"; previews Knock Knock / White-label / Resell kit; a recipients console (Not sent yet / Sending / Sent / Skipped / Failed or bounced / Can't send) and a release panel ("Make it with Claude Code").

Flow:

  1. Moving a Zij card to announce drafts an ops_announcements row (ms-ai writes email, changelog post, in-app note and video scenes) and queues a release job for the PC worker (screenshots + release.json).
  2. A super admin approves. Per-agency white-label versions are checked, emails go through the BullMQ email queue at PRODUCT_UPDATES_BATCH_SIZE/minute (default 20), each logged in product_update_sends; Postmark bounce/complaint spikes auto-pause (POST /public/postmark/product-updates, basic auth). In-app delivery is a notification of type announcement (see Notifications).
  3. On send in production a WordPress changelog post is created (WP_CHANGELOG_*).
  4. Agencies choose what their clients get: agency.client_updates.mode On / "Let me review first" / Off (/agency/settings/client-updates, decisions on /agency/whats-new). This replaced the short-lived per-agency "Announcements (testing)" pilot (agency.announcements_pilot, retired).

Release videos render on the video-worker deployment (BullMQ product-video queue, one at a time, only where SERVICE_VIDEO=true) — see Deployment. Other collections: product_update_suppressions, product_update_videos, product_update_agency_decisions, product_update_rollouts. Unsubscribe: /public/product-updates/unsubscribe (RFC 8058), frontend /updates/unsubscribe.

Env var (PROD only)backendschedular
PRODUCT_UPDATES_MESSAGE_STREAM (product-updates), PRODUCT_UPDATES_TEST_TOconfigmapconfigmap
POSTMARK_WEBHOOK_USER / _PASSWORD, PRODUCT_UPDATES_UNSUBSCRIBE_SECRET (falls back to FILE_LINK_SECRET)secretsecret
WP_CHANGELOG_SITE / _STATUS (draft) / _CATEGORY_IDconfigmap—
WP_CHANGELOG_USER / _APP_PASSWORD, OPS_VIDEO_WORKER_KEYsecret—

Outside production every product-update email goes only to PRODUCT_UPDATES_TEST_TO.