Omniscio

Mission Control (the project management system built into the app)

Omniscio's own project management system, opening as a sidebar project like any other: boards of typed columns, a set of alternate views over the same data, and the cross-board surfaces around them. This is the overview page — the detail sits on the parts below it.

On this page

What it is

Omniscio's built-in project management system, built as an isolated React sub-app and surfaced inside Omniscio as a sidebar virtual project. Gated on missionControlEnabled (default off). Phase 2 (Board core / Main Table) shipped (on top of Phase 0 auth + Phase 1 workspace shell) — opening a board renders the signature Main Table: groups of items with a typed-EAV column engine (status, text, long-text, numbers, people, date, timeline, dropdown, checkbox), inline cell editing, status pills with Edit Labels, a Column Center to add columns, and group-footer summaries. Phase 2b added the item card (a modal with an Updates feed), item duplicate/delete, and a batch-action bar (multi-select → archive/delete). Phase 2c added drag-and-drop reorder (items within/across groups + groups, via @dnd-kit) and a WS realtime board channel — every mutation publishes a board-changed event over /realtime and connected clients reload (the client disconnects on unmount). Phase 3a added the view system: a views table + a view-switcher (Main Table + saved views), the first alternate view — Kanban (group items by a status column, drag a card between columns to set its status) — and four more column types (link, email, phone, rating). Phase 3b added two more views — Calendar (place items on a month grid by a date column, with an unscheduled strip) and Cards (a gallery) — plus an add-view menu and the country/week/world-clock column types. Alternate views are just views rows whose type (a free string) + config the frontend switches on, so a new view is a component + a render branch — no backend change. Phase 3c added the Main Table view controls — search (across the item name + all column text), sort (by a column or name, asc/desc), a per-column contains filter, and hide-columns — all client-side over the loaded board data (no backend). Phase 3d added the Chart view — bucket items by a column and render the counts as a bar or pie (group-by + chart type are local UI state); it's a config-only view over the loaded data. Phase 3e added the Timeline/Gantt view — bars across a time track by a timeline column, with month gridlines, an unscheduled strip, milestone markers (zero-duration items render as diamond shapes instead of bars), and a Critical Path toggle (CPM algorithm highlights the longest dependency chain with accent color on bars and arrows). A dependency arrow runs from the item a Dependency column LISTS to the item that lists it — when item B lists item A, B waits for A, so the arrow goes from A to B (BUG-B056 fixed 2026-10-16; the AI reads links the same way). So the board now has six views (Main Table, Kanban, Calendar, Cards, Chart, Timeline). Phase 3f added the last view — Form: a board→form whose submissions create items, backed by a public (unauthenticated), tokened submit endpoint (formsPublicRoutes in Omniscio's cloud service). That endpoint is deliberately narrow: token-gated, create-only, accepts values only for the form's configured fields, validates each through the column-type registry, and returns no board data. The board now has ten views: Main Table (default) plus nine addable views — Kanban, Cards/Gallery, Calendar, Chart, Timeline/Gantt, Roadmap, Form, Workload, and Map (the last three added post-Phase 3; see dedicated sections below). Phase 4 begins the cross-board surfaces. Phase 4a shipped Search Everything — a backend GET /search?q= and a SearchPage (debounced, opens a result on click; the top-bar search routes here). It began items-only (grouped by board); a parity fast-follow broadened it to four result types — items, boards, dashboards, and people, grouped by type (private boards you're not a member of are excluded from every group) — see Grouped search below. Phase 4b shipped My Work — a backend GET /my-work that returns the items assigned to me (matched by auth.userId against any People column value, account-scoped) each with one derived date (the board's first date/timeline column the item has set), and a MyWorkPage that buckets them into monday's six date sections (Past dates / Today / This week / Next week / Later / Without a date) as a table; clicking a row opens its board. A fast-follow upgraded My Work pixel-near: GET /my-work now also resolves, per the item's board, the first column of each type (group, people, status, priority) so the page renders the full table — name · Group · Board · People · Date · Status · Priority — with colored, collapsible time-bucket sections, an overdue alert on past dates, a New item / + Add task board→group picker (creates via the shared POST /items), and a working Calendar tab. The calendar is the board's grid reused: CalendarView's month/week/day grid was extracted into a shared presentational CalendarGrid (driven by a generic CalEvent[] + useCalendarNav/CalendarNav); the board became a thin adapter and MyWorkCalendar feeds it cross-board items as uniform light-blue "Due date" events. The enrich is read-only (no migration); status vs priority are distinct backend column types, so they separate cleanly. Bucketing/overdue math is unit-tested (tests/unit/plugins/mission-control/my-work-buckets.test.ts); spec docs/superpowers/specs/mission-control-my-work-design.md, plan docs/superpowers/plans/2026-06-08-mission-control-my-work.md. Phase 4c shipped Notifications — a notifications table whose rows are written ONLY as a server-side side-effect of an owner-checked mutation (a People-column write that adds you → an assigned notification; an @YourName in an item update → a mentioned one; the actor is never notified about their own action), read via GET /notifications + GET /notifications/unread-count (both owner-scoped by auth.userId) with POST /:id/read + POST /read-all, and a NotificationsPage (a bell feed with tabs All / Unread / I was mentioned / Assigned to me, mark-read on click, mark-all-read) plus a top-bar bell badge. Phase 4d shipped Dashboards — a dashboards table (workspace-scoped + account-isolated like boards) with an opaque config JSONB (boardIds + widgets); it's config-only (no per-widget backend), with CRUD via dashboardsRoutes in Omniscio's cloud service. The DashboardPage computes every widget client-side over the existing ownership-checked GET /boards/:id/full (so a foreign board id in config just 404s — no leak); a left-nav "Dashboards" section lists + creates them. Phase 4d-redesign rebuilt it pixel-near monday: a header (favorite star, inline-rename, Export ▾ / Invite / ⋯ overflow), a toolbar (+ Add widget dropdown, N connected board → connect-boards modal, type-to-filter, save with dirty-dot, People + Filter scopers, settings gear), a polished empty state, and a drag-and-resize grid (react-grid-layout; per-widget layout {x,y,w,h} stored in config). Editing is always-on with a draft + debounced-autosave model (no Edit/View toggle). Widgets: Numbers (abbreviated $378k figure), Chart (bar / column / pie / donut / line), the sprint trio Velocity / Planned-vs-unplanned / Burndown (frontend-computed from configured sprint/effort/done/date columns — Velocity faithful, the other two documented approximations since there's no sprint-history backend). Battery/Table/Apps remain in code but off the menu. Toolbar People/Filter write config.filters and scope every widget's data via a shared applyFilters (a rule only constrains boards that have its column); Export rasterises the grid with html-to-image (PNG / print-to-PDF); Invite reuses the member directory. Pure logic (dashboardLayout / sprintData / dashboardFilter) is unit-tested; design spec at docs/superpowers/specs/mission-control-dashboard-redesign-design.md. Phase 4e shipped the Activity log — an activity_log table whose rows are written ONLY server-side (via lib/activity.ts) as a side-effect of an owner-checked item mutation (item created / renamed / deleted and column value changed, each with a prev→next summary; the actor is joined separately, not baked into the text), read via GET /activity?boardId=&itemId?= (gated by ownedBoard, newest-first), and surfaced two ways — the ItemCard Activity tab (item-level) and a board-level Activity modal from the board header (both render a shared ActivityFeed). All Phase 4 cross-board surfaces now ship (Search, My Work, Notifications, Dashboards, Activity log). Next: the automations engine (Phase 5).

Where to find it

It appears as its own project in the sidebar once the feature is enabled, and everything from here down lives inside it.

UI surface

A "Mission Control" row in the projects sidebar (alphabetical slot after MCP Servers, before PR Merge Queue), shown only while missionControlEnabled is on. Enable it at Settings → Built-in Apps → Mission Control. Clicking the row mounts the Mission Control app full-pane. Mission Control IS a spawnable session host (spawnable-session-host): __mission_control__ is in SPAWNABLE_VIRTUAL_PROJECT_SENTINELS + MANAGED_WORKDIRS, with a Projects | Sessions tab strip at the top of its left column, PM-oriented system-prompt shim, and Ctrl+T support. On the Sessions tab the left column lists Mission Control's sessions and the main area switches away from the board: picking one shows that session there, and with none picked it shows a Welcome to Mission Control. screen with a Start a session card and ten cards under it, nine coaching cards and Browse Super Prompts, then a Level up section of seven more coaching cards (see The Sessions tab welcome and its coaching cards below; the tab strip stays, so Projects brings the board back); on a phone, picking a session opens it on the session screen and Back returns to Mission Control. Auth is via Omniscio's Firebase Global Auth — users sign in once via Omniscio; when not signed in to Omniscio, a "Not signed in" placeholder is shown.

Give feedback

The round avatar menu at the top right of every Mission Control screen has a Give feedback item, between Settings and Log out, on desktop and on a phone. It opens Omniscio's own Send Feedback form, already on Feedback with app logs unticked, so screenshots, the reply-to address and the "sent / saved on this computer / couldn't send" messages work exactly as they do from the toolbar's Feedback button.

Every report sent from there starts with the line [FEEDBACK: mission-control] Sent from Mission Control. That line is a routing label: when Owner-Assigned Bug Routing is on and a rule maps mission-control to a person, the report goes straight to that person with no AI guess, and the Help Desk does not take it first. With no such rule, the report travels the normal report road. Feedback sent from the toolbar button carries no label. Contract: mission-control-give-feedback-contract.md.

How it behaves

Entity types

Mission Control supports seven entity types (the McEntityType union in types-branded-ids.ts). Agents building import, onboarding, or cross-entity code need to know all seven — not just boards.

Type Category Description Feature dir Routes Extra gate
board Work management Kanban/table project boards — the primary work surface features/board/ /board/:id —
dashboard Reporting Cross-board widget dashboards (Phase 4d) features/dashboards/ /dashboard/:id —
goal Strategy OKR-style goals and objectives features/goals/ /goals, /goal/:id —
portfolio Strategy High-level portfolio views across boards features/portfolios/ /portfolios, /portfolio/:id —
document Content Rich-text documents features/documents/ /documents, /document/:id pm-documents
spreadsheet Content Spreadsheet workbooks features/spreadsheets/ /spreadsheets, /spreadsheet/:id pm-documents
form Content Standalone form builders (distinct from in-board Form view) features/forms/ /forms, /form/:id pm-documents

All seven require missionControlEnabled. Documents, spreadsheets, and forms also require the pm-documents feature flag (default on) — when off, their nav sections, template categories, and routes are hidden. See pm-documents-spreadsheets-forms-contract.md.

Template categories vs. entity types: Five of the seven are template categories (boards, dashboards, documents, spreadsheets, forms). Goals and portfolios are entity types but NOT template categories — they have no preset/template system. See pm-template-categories.ts. The template directory also files every built-in template under one of 11 topics (pm-template-topics.ts), so people can browse by Topic or by Format — see mc-templates.md.

Competitor-to-MC entity type mapping

Eleven import adapters (registered in adapter-registry.ts) convert competitor data into MC entities. The import IR operates at four levels: board → group → column → item. The PLATFORM_TO_PRESET mapping in pm-import-platforms.ts routes each platform to a starting preset.

Source Competitor entity MC type Import status Notes
Trello Boards board Importable Preset: trello
Notion Databases board Importable Preset: notion
Notion Pages document Not yet (supported: false) Adapter exists, path not wired
Jira Projects board Importable Preset: engineering-jira
Jira Confluence pages document Not yet No adapter yet
Monday Boards board Importable Preset: operations
Monday Workdocs document Not yet (supported: false) Adapter exists, path not wired
Asana Projects board Importable Preset: asana
Asana Goals goal Not yet (supported: false) Adapter exists, path not wired
Linear Teams board Importable Preset: engineering-linear
Linear Projects — Not yet (supported: false) No MC equivalent for Linear's project grouping
ClickUp Lists / Spaces board Importable Preset: clickup
ClickUp Docs document Not yet (supported: false) Adapter exists, path not wired
Airtable Tables / Bases board Importable Preset: airtable
CSV — board Importable Generic file import
Google Sheets — board Importable Generic file import
Excel — board Importable Generic file import

Import gaps (declared supported: false in adapters): Competitor pages/docs (Notion pages, Monday workdocs, ClickUp docs) → MC document; competitor goals (Asana goals) → MC goal. The MC entity types exist and have full UIs — only the import adapters need wiring.

No MC equivalent yet: Wiki/knowledge-base systems (beyond documents), whiteboards/canvas (Miro, FigJam-style), and standalone timeline tools exist as competitor entity types but have no dedicated McEntityType. Timelines are handled by the board's Timeline/Gantt view rather than a separate entity.

Workspace shell (Phase 1)

Once authenticated, the panel mounts a MemoryRouter (Omniscio owns the real URL) → an AppShell: a top bar (wordmark, search bar, a Settings gear that opens Mission Control Settings, notifications bell with unread badge, an Open in new window button on desktop that pops Mission Control out into its own window (hidden inside a window that is already popped out), and an account menu — an avatar button at the far right that opens a dropdown with the user's identity, a theme toggle, and a log-out option; matches Ollert's AccountMenu pattern) and a left nav with a workspace switcher (a monday workspace header + ⋯ actions menu — see Workspaces functionality below), a "My Work" entry (the cross-board My Work table + calendar — see Phase 4b), and the board list for the active workspace. The row for the board that is open is highlighted and marked as the current page, and opening a workspace route picks that workspace when none was chosen before. The left nav is mounted beside the routes, not inside one, so it reads the open board and workspace from the location with useMatch (BoardNavRow.tsx, useLeftNavState.ts); useParams is always empty there. The Favorites, Boards, and Dashboards sections are each independently collapsible — click the section header (chevron + label) to toggle; state persists in localStorage (mc.nav.<section>.collapsed) and is swept on sign-out. Action buttons (+, T) remain visible when a section is collapsed. The shared hook is useNavCollapse (features/nav/lib/useNavCollapse.ts). Clicking + creates a board (with a default group) and navigates to it. Home shows recent boards (first-N for now) with empty states; workspace and board routes render their own pages (the board is a Phase-2 placeholder). The whole tree comes from one backend aggregate, GET /nav/tree → { workspaces: [{ ...ws, folders, boards }] }, fetched by useNavTree().

The backend (Omniscio's cloud service) adds account-scoped CRUD modules — workspaces, folders, boards (each guarded by a shared requireAuth Elysia plugin that verifies the Firebase ID token via admin.auth().verifyIdToken() and derives { userId, accountId }, filtering every query by accountId; dual-auth: also accepts legacy JWT during migration) — plus the /nav/tree aggregate. Registering a new account auto-seeds a "Main workspace".

Dashboards, Home's board rows and goals are NOT in that aggregate, so the left nav, Home and the Goals page load them once per workspace — at most six requests at a time (mapWithConcurrency + WORKSPACE_FANOUT_CONCURRENCY in lib/workspace-fanout.ts), and the left nav and Home share one in-flight dashboards request per workspace. On an account with hundreds of workspaces those lists fill in over several seconds instead of firing every request at once; the all-at-once version queued ~3,900 requests on a 1,298-workspace account, timed most of them out and showed the "Could not reach the server" banner even though the server was healthy. Leaving the page stops the remaining requests.

Member invites

An admin invites an address from Invite to Mission Control; the backend creates a pending member (assignable immediately) plus a 7-day invitation token, and mails an accept link. Mail goes out over whichever transport the deployment configured — the SMTP2GO HTTP API when SMTP2GO_API_KEY is set (the unified deploy's only email config), plain SMTP when SMTP_HOST is — and POST /members/invite returns emailSent so the dialog can say "created, but the email could not be sent" instead of closing on a false success.

The invite and password-reset emails, and the page each link opens, carry the Omniscio look: a dark header with the orb logo, the OMNISCIO wordmark and "Mission Control", the aurora colours, one clear button, and an Omniscio LLC footer. The invite says who invited you, shows their personal note in its own card, and says when the invitation expires. The pages say Open in Omniscio and never the retired product name. Emails come from Omniscio Mission Control <missioncontrol@omniscio.com>. How the pages are built: mission-control-public-pages-map.md.

The link opens the app at /invite/<token> (deep link agentmc://monday/invite/<token>). The invite is not consumed by signing in: signing in gives a person a team of their own (the F001 consent rule) and leaves the pending invitation exactly where it is. Joining happens only when they press Accept invitation, which calls POST /invitations/:token/accept with their identity token; the route matches the invitation against the verified email on that token and adds a membership in the inviting team with the invited role. It never moves the person out of their own team and never asks them to empty it first, so the old "Move your own work first" refusal is gone. A different address gets 403, a membership already claimed by a different sign-in gets 403, an unverified email gets 403, and an accepted/expired token gets 410. The legacy name+password accept still works for a never-signed-in invitee, but is refused (409) for an address that already signs in with Omniscio.

Turning Mission Control off only hides it. Your boards, items, columns, values and attached files all stay, on this computer and in the cloud, and turning Mission Control back on shows them exactly as they were. The switch never deletes or erases anything (the mc-account-switch settings side effect only clears the cached sign-in). Deleting your Mission Control data is planned as a separate, confirmed action and is not built yet. Contract rule: off-switch-hides-never-wipes in mission-control-integration-invariants-contract.md.

What erasing a person removes on this computer. The per-person erase (DELETE /pm/data/user/:id, your own id only) works from one list of every place Mission Control keeps a person, pm-person-data-map.ts. It deletes their own records: board membership, notification settings, watches, votes, time off, working hours and Team Chat links, their personal views, and their approval records when the email is given. Work the team keeps stays and loses only the person: comments, form answers and items they made show [deleted] as the author, and they are cleared as owner of goals, documents, sheets and forms. Their id is also replaced inside saved filters, automations and other saved settings, matching the exact id only. The whole erase succeeds or changes nothing. Queued edits waiting to upload are left alone, so nothing rewritten is pushed to the team. Older backups, logs and the cloud copy are handled by later Layer 9 slices. Contract rule: a-mission-control-person-is-erased-from-one-map in erasure-subsystem-contract.md.

Following an invite while Mission Control is off. Mission Control is off by default, and its sidebar row exists on every install but is hidden while the switch is off. So an invite link (mission-control-invite) or a board / workspace / dashboard share link (mission-control-join) no longer opens a hidden panel or drops the token. Instead, it asks once: "Turn on Mission Control to join {team}", or "…to open this shared board / workspace / dashboard" for a share link. The team name comes from the public GET /invitations/:token/info lookup, and if that lookup fails it says "your team". Turn on Mission Control writes missionControlEnabled = true (the same write the Settings toggle makes) and continues into the SAME link with the token kept. Cancel changes nothing and shows no error. The one other place that turns it on is a SUCCESSFUL accept (see "What the invite page shows, and where accepting lands"). The prompt lives in the deep-link router (askToTurnOnMissionControl), and the switch it uses is missionControlSwitch in src/renderer/src/features/mission-control/mission-control-invite.ts.

An invite survives download and install. The invite web page tells someone without Omniscio to download it and sign in as the invited email. After that, nobody has to open the email again:

  • Once the app is showing and onboarding is finished, the desktop app asks main whether a Mission Control invite is waiting (mission-control:take-pending-invite) once on every launch, and again whenever the signed-in account changes. Anyone signed in is asked, whether or not Mission Control is already switched on.
  • Main calls GET /invitations/mine with the signed-in identity token. That route answers only for the caller's own verified email (an unverified one gets 403), never creates or changes an account, and returns the open invitations newest first.
  • Only a FINAL answer counts: a JSON list, even an empty one. The unverified-email 403, a network error, a 5xx, and an older server that answers with the HTML invite page all leave the check open, so the next ask simply tries again. missionControlInviteCheckedAt records when the last answer landed.
  • An invitation is shown ONCE. Its token is remembered in missionControlInviteSeenToken, so a later launch does not re-open an invitation the person has already seen and left; an invitation that arrives later has its own token and is still surfaced. The token goes through the ordinary mission-control-invite link, so the person sees the same turn-on prompt.

Share links are not tied to an email, so their page still says "open this link again". Inviting to a workspace. A workspace's … menu has Invite people, which opens the same dialog for that workspace and sends its workspaceId. The dialog says the person starts in that workspace and can explore anything else their plan allows: they join the whole account, and the workspace is where they start, not a limit. The workspace is stored on the invitation and granted only when they accept. Each workspace gets its own invitation: re-inviting a still-pending person to the SAME workspace resends that invitation, while inviting them to a DIFFERENT workspace creates a second one with its own email. Accepting any one of a person's open invitations into the account grants every workspace they were invited to and closes the rest in the same transaction, so whichever email they open, no workspace is lost. The Users list shows a pending person once however many invitations they have open.

Copyable invite link. POST /members/invite also returns inviteToken, the invitation's link key (its id — never the secret token that goes only in the email), for a new invitation and for a resend to a still-pending person (an already-active member gets none). The link works only for the invited person: it opens the invite page, which accepts through a sign-in as the invited address, so whoever sent the invitation cannot use it to accept on someone else's behalf. The app builds the link as <backend address>/invitations/<token>, the same address the board, dashboard and workspace join links use, so it never points at localhost in a real install. After Invite the dialog stays open and lists each invited person with a Copy link button, plus "Links expire in 7 days" and Done. When the email could not be sent it says "Copy the invite link below and send it yourself" instead of asking to invite again. A server that returns no token keeps the old behaviour: the dialog closes on success.

What the invite page shows, and where accepting lands. Before accepting, the page reads GET /invitations/:token/info, which returns the team's name, the invited workspace's name (null for a whole-team invite, or once that workspace is deleted) and the inviter's name — never the invitee's email, because anyone holding the link can call it. The page says "Sam invited you to join Launch Plan in Acme." (or "…to join Acme." for a whole-team invite). Accepting returns workspaceId: the invited workspace if it still exists, otherwise the team's main workspace. Mission Control then restarts in place — it does not reload the Omniscio window — after clearing the previous account's device-local caches, and opens that workspace with a one-time line, "You're in! Sam invited you to Launch Plan.", that "Got it" dismisses for good. That workspace is only where the invitee starts; it is not a limit on what they can open. A whole-team invitation, and an older server that sends no workspaceId, land them on Mission Control Home with the same one-time line, naming the team rather than a workspace. Accepting also turns Mission Control on when it was off, and closes the setup wizard the invitee never needed to run, so an invited teammate does not land on an empty screen.

When the accept is refused, the page says which refusal it was. A 403 means the invitation is for a different account and a 410 means it is invalid, already used or expired; both have their own page. A 401 ("open this invitation in Omniscio and sign in as the invited address") and a 409 ("this invitation belongs to an account that has already signed in") get a Sign in as the invited address page with Switch account, because signing in as the invited address is the only thing that fixes either. A genuine connection failure still says so, and a 5xx says the server could not accept it rather than blaming the connection. Every other refusal — a revoked invitation, a throttled request, any status the page does not know by name — is reported as an invitation problem with Try again, and never as a wrong account, because the only recovery that page offers is to sign out. Try again retries whichever call failed — the accept after a refused accept, the invitation lookup after a failed lookup.

Replying to an email posts an update

When Mission Control emails someone about one item (a mention, an assignment, or a reply to their update), they can answer that email and their reply is posted as an update on the item, under their name. Each of those emails carries its own reply address, reply+<code>@reply.omniscio.com. Summary emails, invites and password resets never do.

  • Only the person the email went to can post, and only while they can still edit the board. The reply must come from their account's email address and pass the standard sender checks (DMARC, or a DKIM signature by their domain). Permission is checked when the reply arrives, so someone removed from the board, or a viewer, posts nothing.
  • Only the new words are posted. The quoted earlier email, the signature and the "On … wrote:" line are removed. A reply sent only as formatted email is read as plain text first.
  • Photos and files come along. They are saved to the item's Files tab under the replier's name, the same place the app's own "Attach a file" puts them, and the update names them ("Attached from email: photo.jpg, plan.pdf. They're in this item's Files tab."). A reply with only a photo and no words still posts.
  • Up to 10 files and 15 MB of files per reply. Anything past that, a blocked file type, and a file that can't be read or saved are named in the update with the reason. There is no virus scan.
  • The same file types are refused everywhere a file enters Mission Control — email replies, the Files tab, a Files column, and local boards. Blocked: programs and scripts (.exe, .js, .ps1, .sh and the like, even disguised as "invoice.pdf.exe" or as a photo whose bytes are a program), web pages (.html, .svg), macro-enabled Office files (.docm, .xlsm, .pptm and the like), and archives or disk images (.zip, .7z, .rar, .gz, .iso and the like). Ordinary Office files (.docx, .xlsx, .pptx and the older .doc, .xls, .ppt), PDFs and images are fine. The app refuses a blocked file before uploading it, and the team server refuses it again, so skipping the app does not get one in. Files already saved before a type was blocked stay where they are.
  • An upload to the Files tab that fails partway leaves nothing behind. When the file reaches storage but can't be added to the item, the app asks the team server to delete it again. Only the person who uploaded it can, and only while it is not attached to the item: someone else asking is refused, and a file that did get attached stays put (remove those from the Files tab as usual). Uploads started before the team server learned this record no uploader, so a failure from one of those can't be cleaned up this way. A file an agent adds through the app's own upload route (POST /pm/items/:id/attachments) is cleaned up the same way, and if that cleanup fails it is logged while the agent still sees the original error (pm-item-file-upload.ts). When Omni makes that upload, it always waits for the person's OK first: nothing reaches the team server until the card is approved, and then the app itself replays it (presign, upload, register). mc-item-file-omni-upload.spec.ts proves that whole round trip end to end, against a fake team server, a fixture storage bucket and a fake signed-in account, with the card approved inside the isolated test app. How it is wired: DELETE /items/:id/files/orphan?key= on the team server, keyed on the uploader segment the presign writes into the storage key; mc-file-client-routes-declared.test.ts fails if the app ever calls a file route the team server does not declare.
  • Signature logos are not files. An image that is only part of the signature or of the quoted earlier email is skipped quietly. A photo placed in the new words, and any inline document such as a PDF, is kept.
  • When the team server has no file storage set up, the words still post and the update says a file was left off.
  • Posted updates show a small "via email" label (tooltip: "Posted by replying to an email").
  • A reply that can't be posted is always explained. The person gets a Mission Control notification and one short email saying why: the item was deleted, they can no longer edit it, or the reply was empty. When someone the email was forwarded to replies, the original recipient gets a notification. The person who replied gets the short email only if their mail passes the sender checks, so a forged address is never mailed. That email's Reply-To stays support@omniscio.com, so an automatic reply to it can never post anything.
  • Automatic mail is ignored. Out-of-office replies, bounces and bulk mail post nothing and get no answer. The same reply delivered twice posts once, and each reply address accepts at most 20 replies an hour.
  • How it is wired: a Cloudflare email worker receives the reply and hands it, with its files, to the team server with a signature. A larger hand-off also carries a signed size notice, checked before the team server reads it. The team server checks it, saves the files and posts it. Deploy the team server before the worker, or replies with files bounce. Reply addresses appear only once the team server has its reply secret set, so a partial deploy changes nothing. Detail: mission-control-updates-map.md and the contract.

What signing out does to your Mission Control data

Most Mission Control data (sprints, goals, automations, views, approval workflows, portfolios, documents, item links) lives only on your computer, so it cannot be pulled back from the cloud. Signing out on purpose, switching accounts, or having an account disabled clears it, as before. If Omniscio signs you out because your login expired (a dead Firebase refresh token), it keeps the data and remembers whose it is. Sign back in as the same account and everything is still there; sign in as a different account and the old data is cleared before that account's boards load. If Omniscio cannot tell whose the kept data is, it clears it to be safe. Boards pulled from the cloud also bring their saved views with them now.

Live updates stop when your login ends

The live-update connection that keeps open boards current no longer outlives the login behind it. The team server asks again every five minutes, using the sign-in each connection was opened with, and closes any connection whose login no longer works (it expired, or the person was removed). It closes all of a person's connections at once when their sessions are revoked: signing out everywhere, changing the password or resetting it. Mission Control reconnects on its own and signs the new connection in with a fresh login, so an ordinary expiry goes unnoticed; with no valid login left, it gives up after three refused attempts and stays disconnected until the person signs in again. A check that cannot reach the login service leaves the connection open until the next one.

Removing a member

An account admin can take a person who already joined out of the account from User management: each joined member's row has a red Remove button that opens a confirm dialog ("Remove {name}?"). The button shows only to admins, never on the account owner's row or your own row, and never for a pending invitee (cancel their invitation instead). The rules it keeps are the member-removal invariant in mission-control-integration-invariants-contract.md.

  • Deactivated, not deleted. DELETE /members/:id sets the person's users.status to removed. Their boards, items and comments stay, and their name stays on past work: the directory still returns them when asked with ?includeRemoved=1 (the app does, so old assignments keep their names), while every other directory read, the people pickers, people search and @mentions leave them out.
  • Cut off at once. Every sign-in path refuses a removed person with 403 {code: "member_removed"}: an access token, a Firebase sign-in by uid or by email, /auth/me, /auth/login and token refresh, and their open live-update sockets on that server are closed. Their sessions, password-reset and calendar-feed tokens and team memberships are deleted. Firebase itself is untouched, because it is also their Omniscio sign-in.
  • Nothing is orphaned. Private boards and closed workspaces they owned pass to the admin who removed them; the member_removed audit row records which ones (before.ownershipMoved).
  • What the removed person sees. The first member_removed answer makes the desktop stop calling the backend (Mission Control's own screens and the app's background calls alike) and Mission Control shows one plain message, "You were removed from this Mission Control account." Invitation routes stay reachable, so a person who is invited back can still accept.
  • Inviting them back. An admin of the same account can invite a removed person again. They show as Pending and stay locked out until they press Accept invitation, which makes them active again.
  • From an agent. DELETE /pm/members/:id on the local command server asks for the same removal; it always waits for a person's approval (pm.members.remove).
  • Not covered. A removed person's own computer keeps the copy of the boards it already downloaded until they sign out; the server refuses them from the next request.

Your role on a board, and which boards you see

A board can give you one of four roles: owner, admin, member or viewer. Owners and admins manage the board; members work on it; a viewer can read it and cannot change it. Every Mission Control screen keeps to this: on a board where you are a viewer, the app refuses edits to cells, new items and columns, group renames, comments and archiving, and says so plainly ("You do not have permission to …") instead of showing a change that was never saved.

  • The role comes from the server, every time a board is downloaded. Your copy keeps its own note of your role so it can answer instantly, and that note is now written from the server's own list of board members. Before this, every downloaded board recorded whoever was signed in as its owner, so a viewer's app believed they owned everything and let them make changes that looked saved, never reached the server, and quietly disappeared.
  • If the server cannot be asked, the app assumes the least. When the role check cannot get an answer, a note that says "owner" is treated as "viewer" until a good answer arrives, so a failed check never hands anyone more access.
  • Only the server's own record can make you an owner. A role list that names you owner for a board the server attributes to somebody else is treated as a bad answer, not as permission.
  • Private boards stay private. A board marked private appears only for the people on it. An ordinary shared board appears for everyone in the account, which is what the server itself does.

The rules, the two places that write the role, and what each failure falls back to are the local-authority-tables-are-amc-owned invariant in pm-sync-contract.md.

Deleting a workspace from the command line

DELETE /pm/workspaces/:id on the local control server deletes a Mission Control workspace for real. It deletes it on the Mission Control backend first, then removes the local copy, so the next sync cannot bring it back. Only an Omniscio super admin (global role admin or owner) may use it; anyone else gets a 403 and nothing is deleted. The backend still applies its own rule as well: the caller must own the workspace or be an admin of the account. The delete is a soft delete on the backend, so it can be reversed there. This is the road for clearing test data and for honouring a data-deletion request. Before this was fixed the route only removed the local copy, and every deleted workspace came back on the next sync.

Belonging to several teams

One person can belong to any number of Mission Control teams (the server calls a team an "account"), with no limit and no paywall today. Inviting someone who already uses Mission Control works like inviting anyone else: the invite route looks the address up only inside the inviting team, so "That email is already in use" no longer happens, and the answer never reveals whether an address uses Mission Control elsewhere.

  • What a team is to the server. A person has one membership row per team, tied together by their Omniscio sign-in. Role, workspace access and assignments belong to the membership, so being an admin in your own team says nothing about a team you joined.
  • Which team a request is for. The app sends the team it is showing in the x-mc-team header (and as teamId in the realtime auth frame). The server answers from that team only if the person is an active member, otherwise 403 NOT_A_TEAM_MEMBER. No header means the person's home team: the membership that became active first, so an older app build keeps working.
  • Switching. People in two or more teams see Your teams in the account menu (the avatar, top right), with the current team ticked and their role in each. Picking another team saves it in the pmTeamId setting (null means the home team), re-pulls the boards, clears this device's recent-board keys and reloads Mission Control. Accepting an invite switches to the joined team. GET /auth/teams lists the signed-in person's teams, home first.
  • Boards saved on this computer. Each saved workspace remembers the team it came from (pm_workspaces.mc_team_id), and the background sync and the offline-edit replay always ask a board's own team. That matters because the sync treats "board not found" as "deleted": without it, switching teams would make every board of the other team look deleted and drop queued edits.
  • A stale choice. If the saved team answers NOT_A_TEAM_MEMBER, the app clears it once and falls back to the home team. Only a read is retried there; a change (creating, editing or deleting something) is never re-sent to another team, so it fails and asks the person to pick their team and try again.
  • Rollout. The server change (a private backend app, migration 0041) ships with that backend's own deploy script and must go out with the app release. The migration only changes two uniqueness rules and adds an empty joined_at column; it edits no rows and refuses to run if a team holds two addresses that differ only by letter case.

The rules are in the one person, many teams contract.

A new Mission Control session

A brand-new Mission Control session shows the gold-and-teal Mission Control atom on a teal glow, the heading "Welcome to Mission Control." in cyan (in the Mission Control wordmark font) and "What project are we working on today?" in gold, with the same Session setup card a regular new session has underneath (Harness, Provider, Model, Thinking, MCP servers). It names no Project Manager, because Mission Control works with Omni switched off. The text is the same every time. Once the Project Manager is answering, or when you come back to an idle Mission Control session, the screen shows the usual working or idle line instead. A session started from a coaching card skips this screen, because it opens on that card's opening message.

The Sessions tab welcome and its coaching cards

On the Sessions tab with no session picked, the main area shows the same Mission Control atom and Welcome to Mission Control. in the Mission Control wordmark font (painted with the brand gradient here, where a new session paints it cyan), the line Pick a session from the list, or start a new one., a Start a session card on its own row, and nine cards under it, three to a row (two when the side panels are open, one column on a phone), in the same card and grid as the Tasks Sessions welcome. With two to a row, the last card, Browse Super Prompts, sits alone on its own row. They are built for a team lead who runs several projects:

Card What it opens
Talk Through a Project Project Deep Dive Coach: think through one project, with pushback, ending in a plan
Break It Down Break It Down: makes the job clear, offers two or three gap-free (MECE) breakdowns, then turns the chosen one into sub-items marked AI does it / AI does it with your OK / A person does it, and waits for your yes before creating anything (the same guide as Omni's "Break down a big job" card; your Omni approval level still applies)
Brainstorm With Me Possibility Explorer: dozens of ideas from creative angles, narrowed to the best few
Cross-Project Analyst Cross-Project Analyst: risks, blocked work and overloaded people across your Mission Control projects; it looks beyond Mission Control only when you ask
Vision Document Creator Manager Vision Document Creator: a vision document your team can act on
Team Workload Balancer Workload Balancer: Mission Control's own workload answer for each person, why, and what could move
What-If Scenario Planner What-If Scenario Planner: how a scope, people or date change ripples through the plan
AI Coaching Opens AI Coaching (below)
Browse Super Prompts Opens the Super Prompts picker, set to launch into Mission Control (below)
  • Each of the first seven opens ONE Mission Control session that shows the prompt's ready-made opening message straight away; nothing is spent until you reply. The session is named after the card you clicked (Brainstorm With Me, not the library prompt's own title), in your app language. The prompts are the same for everyone for now.
  • Back at the top left of a card's session returns you to the cards (Escape does the same); the session keeps running. Only the Mission Control and Tasks card sessions have this Back button; other sessions do not, and neither does a popped-out session window, which has nowhere to go back to.
  • The AI Coaching card opens AI Coaching when it is already on. When it is off, a popup asks first, saying AI Coaching is still in development and builds a private personal profile from your interviews; Turn on and open switches it on and opens it. With no working Anthropic API key (the same check as the Settings switch), the popup points you to Settings → Accounts instead and leaves AI Coaching off.
  • The Browse Super Prompts card opens the same Super Prompts picker used everywhere else, with Mission Control as its only launch target. The prompt you launch opens as a Mission Control session in the main area, like the other cards. Closing the picker without launching opens nothing. A prompt picked here behaves as it does from the picker anywhere else: it starts at once unless it ships a ready-made opener.
  • For one person new to project boards, the picker also holds five getting-started prompts with ready-made openers: Help Me Get Organized, Walk Me Through My First Board, Dump Everything in My Head onto a Board, Plan My Week and Set Up Goal Tracking (search "mission" to find them). Each asks a few lettered questions and ends with a board plan you build yourself, pointing to a matching template such as Personal To-Do or Goal Tracker. They have no cards of their own on this screen.
  • If a card cannot start its session, you see "Couldn't start the session." and nothing opens.
  • Other agents can open any of these prompts into Mission Control with POST /superprompts/:id/launch.

The Level up section

Under the ten cards, a Level up heading ("Coaching that works from your real boards") holds seven more cards in the same grid; with three to a row the seventh sits alone under the middle column. Each opens one Mission Control session on its prompt's ready-made opener, free until you reply, exactly like the first eight. Each one asks before reading your boards, treats what is written on boards as information rather than instructions, uses only data the app really has (and says so when it is missing), walks you through board changes rather than making them unasked, and asks to change a setting only through an approval card in your inbox.

Card Super prompt What it does with your real data
Set Omniscio Up for How I Work mc-work-style-setup Names your work style from an interview plus which features your boards use and how much board work AI agents do, then builds a 4 to 8 step setup plan (views, groups, due dates, an automation preset, a dashboard, Omni on or off, coaching tips on or off)
Map My Cross-Team Timeline mc-cross-team-timeline Measures time spent working versus waiting at each stage and hand-off from item history and links, finds the biggest waits, and re-plans with real numbers
Calibrate My Estimates mc-estimate-calibration Compares how long finished work really took with what was planned, names your pattern, and builds a personal rule of thumb
Design My Daily Rhythm mc-daily-rhythm Counts what is due, overdue and stuck in My Work, then designs a lighter and a fuller daily routine and how to set it up in Mission Control
Scope Guard mc-scope-guard Compares a live project to what existed when it started, sorts what crept in, sets up a Form view intake for new requests, and drafts a stakeholder note
Protect My Capacity mc-protect-capacity Shows what a new request would push out of your real workload and drafts word-for-word "no", "not now" and "yes if" replies (drafts only, never sent)
Level Up in Mission Control mc-feature-of-the-week Checks which features your boards already use, picks the one with the biggest payoff, and teaches it hands-on on your own board; run it again any time and it moves on

When the Level up section appears. A beginner does not see it: the heading and all seven cards stay hidden until either 14 days have passed since you first turned Mission Control on (or first opened a board, or first used it, whichever came earliest), or you have used Mission Control on 10 different days. A day counts once, however many times you use Mission Control that day; opening the Sessions tab counts, and so does working on a board, on your computer or your phone. Work an agent does through the command interface does not count. Anyone who first opened a board two or more weeks before this rule arrived keeps the section straight away. Turning Mission Control off and on again does not restart the clock; resetting all coaching tips in Settings does. Until the app has checked, the section stays hidden, so it never flashes up for a beginner. The record is three coaching counters on this computer (mc:enabled, mc:board:opened, mc:active-day), read through the mc-analytics:level-up-status channel; the lobby counts the visit with an engagement/lobby-opened Mission Control analytics event first.

The Level up reminder. For someone who uses Mission Control, an inbox card Your Mission Control level-up invites them to run Level Up in Mission Control: the first one 14 days after they first open a board, then 14 days after each previous card. Its Start the session button opens the session. It never shows while one is still open, while Mission Control or Tips & Guidance is off, during a brand-new user's first day, or when no board was opened in the last 14 days. If the last two cards were both put away without being used, the next one waits 30 days. The cards themselves are the only record, so a restart neither repeats one nor forgets one.

Setting up the project after the plan

When you and your project manager have a plan for a new project and you say you want it set up, it can build the project in Mission Control for you. There is no separate Project Setup prompt to launch any more; it all happens in the same chat.

  • A teal line with the Omni mark reads Project Setup starts here, with two buttons: Continue here and Start a fresh chat (a fresh chat already holds your plan, and the buttons show how much of this chat's memory is used).
  • Your project manager asks only what it still needs, then lists what it will make and shows Build it and Not now. Nothing is built before you press Build it.
  • Build it creates the project with its groups and items, any Tasks with their notes, a vault note and a check-in schedule, in a workspace you can open. The check-in still waits for your OK in your inbox. A note in the chat lists what was made and anything that was not.
  • Your choices are remembered, so the next setup starts with "same as last time?".
  • The A/B question buttons stay hidden for that chat while you are choosing, so you only see one set of buttons.

More: AI Project Manager.

The project manager's name

Your AI project manager is called Omni by default. Rename it in Settings → Mission Control → Name and look (the Omni area) → Name your assistant (the setting is pmAssistantName). The new name shows live, with no restart, on every screen that talks about it (the welcome line, the "Keep going with ..." and "Ask ..." buttons, setup, the Tasks screens, the settings cards and labels, the Stats tab, the Inbox filter, the keyboard shortcut names, the daily-limit alert and the Mission Control team-chat bot) and in how it names itself in its replies.

It does not change the voice Session Briefing (that stays Omni), the sidebar label "AI Project Manager" (the only place that keeps that name), or other assistants such as Momentum, Chief of Staff and Ask Omniscio. The name takes letters, numbers and spaces, up to 40 characters; an empty box goes back to Omni. Details: settings-extra-hijklmnopq.md.

What Omni knows about you

Turning Mission Control on means Omni remembers what it learns about you (how you work, what you prefer, your role), so it gets better at helping you. The Enable Mission Control card says so in one line: stored only on this computer.

  • It is kept in Global Memory's About You, even with Global Memory off. Only the Project Manager uses it then; turning Global Memory on later shares it with your other sessions, with nothing to copy. Details: global-memory.md.
  • The background review that finds those facts is the Learning Loop, not Global Memory's old end-of-session summarizer: it reviews finished sessions, has its own daily limit and off switch, and keeps no facts about the person while Global Memory is off. With Global Memory on it is switched on for you.
  • See and erase it in Settings → Mission Control → Omni's memory → What Omni knows about you (it shows the name you chose): each item has Erase, and Erase all clears everything (both ask first). Erasing removes the words from this computer.
  • You can stop it being saved. Let your AI project manager remember what it learns about you, the switch in that same card, is on by default; turn it off and Omni stops saving new facts about you, what it already saved stays until you erase it, and the rest of Mission Control keeps working. Details: settings-extra-hijklmnopq.md.
  • The section stays visible after Mission Control is turned off while anything is still saved, so nothing is hidden. It is desktop-only, like the Memory panel.

Agent crews and the inbox agent on Home

The Home page shows an Agent crews card under the What-next card while Agent crews is on. It lists each live crew on this computer with its open tasks and, when some are stuck, how many are blocked.

  • Click a crew to open it in the Overseers hub. Past eight crews, Open all crews opens the hub itself.
  • The inbox agent row reads Running and opens the inbox agent's session. When the inbox agent is switched on but not started, it reads Not started and opens Settings → Inbox agents.
  • What it never shows: an ended crew, or a crew from another computer or account. Crews never travel with a backup or a sync.
  • When it hides: the card is absent while Agent crews is off, and it lists no crews while Overseers is off. There is no inbox agent row while the inbox agent is off. On a phone using web access, only the inbox agent row can load, because the crew list is not served there.

Your project manager knows the same crews. A Mission Control or Omni session's standing context lists up to ten live crews with their open and blocked tasks, plus the inbox agent's state. For more, it reads GET /overseer/hub and GET /inbox-agent. GET /crew/mine and GET /crew/directory answer only a session that is itself in a crew, so they refuse a project manager session. Rules: mission-control-integration-invariants-contract.md home-shows-own-live-crews.

Code work on a linked GitHub repo

Mission Control sessions normally run in their own scratch folder, so code written there can never be landed. Link an item to a GitHub repository and its code work runs in the right place instead.

  • Link the repo. Add a GitHub repo column from the Column Center (it is a Link column) and paste the repository's address on the item. Each item can point at a different repository.
  • Start code session. An item with a GitHub link shows a Start code session button on its card. It opens the shared Start session dialog for the card: anything you type in Message leads the card's brief, and the model you pick there is the one the session uses. The session opens in the hub (the project in your sidebar) for that repository, stays linked to the item, and knows the item's details. Read-only boards do not show the button, and neither does the phone or web version.
  • One hub per repository. If you already have a project for that repository, it is reused. A second one is never made.
  • Setting one up. With no project for the repository yet, a short dialog asks where to keep it, then downloads it and starts the session. On the Free plan the dialog shows how many of your free projects you have used, but only while the project limit is on. A paid plan sets the project up for you, and saving a GitHub link on an item prepares it in the background.
  • At your plan's limit, the dialog says so before anything is downloaded, with an Upgrade plan button.
  • Agents can do the same: GET /pm/code-hubs/resolve?repo=<url> finds the project for a repository, and POST /pm/items/<id>/start-code-session starts the session. A Mission Control session offers to move code work into the right project and only does so after you say yes.

How it works inside: mission-control-code-hubs.md.

  • Mission Control part 2 — the Main Table, the alternate views, and the per-board features.
  • Mission Control part 3 — workspaces, accounts, people, permissions and publishing.
  • Mission Control part 4 — the integrations: templates, calendars, meetings, search and notifications.
  • Mission Control part 5 — the automation engine, the event bridge, the data mirror and the command surface.
  • mc-templates.md — saving a board's structure as a reusable template.
  • mc-email-updates.md — opt-in mention, assignment, reply and summary emails, and the Settings Email card.
  • PRD Studio — how a one-paragraph idea becomes the finished requirements document a board is planned from.

See also

  • mission-control-integration-contract.md — the invariants + the tests that guard them
  • pm-inbox-contract.md — inbox source invariants + tests
  • pm-board-templates-contract.md — board template save/deploy/gallery/editor invariants
  • pm-calendar-overlay-contract.md — calendar overlay invariants
  • pm-session-link-contract.md — session linking invariants
  • pm-search-integration-contract.md — search/embeddings/knowledge invariants
  • pm-setup-wizard-contract.md — setup wizard + preset picker invariants
  • pm-cross-entity-link-contract.md — cross-entity linking invariants (KMS, mind map, flowchart, whiteboard)
  • pm-voice-actions-contract.md — voice command + semantic search + webhook invariants
  • pm-time-tracker-bridge-contract.md — time tracker bridge invariants (hub-spoke #3)
  • INDEX.md
  • Integration standards

Last verified 2026-11-03