Mission Control — Documents, Spreadsheets & Forms
Documents, spreadsheets and forms are ordinary Mission Control project types, offered beside boards and dashboards with nothing to switch on first. Each is scoped to one workspace with the same never-really-deleted storage as the rest of the product, and each has its own sidebar section, list and detail pages, six routes, and ready-made starter templates.
On this page
What it is
Status: shipped and always available. Nothing has to be turned on to use them,
and no in-development switch hides them. Part of the Mission Control PM system, so
they require missionControlEnabled like every other project type.
Mission Control is Omniscio's built-in project-management system. A workspace there collects a team's work — today that means boards, dashboards, goals and portfolios. This area adds three more kinds of thing you can keep in the same place:
- A document — a title and a body of text, in one of three states: draft, published, or archived.
- A spreadsheet — a title, a description, a saved configuration, and a data payload (the cell content, stored as a JSON string).
- A form — a title, a description, a configuration, a state (draft, active, or closed), a count of responses received so far, and every response itself. Only an active form accepts a response. Each response is saved with the time it arrived and its answers, one per field, labeled with the field's label; the count always equals the number of saved responses. Responses read back newest first, and only for someone who can see the form's workspace.
Each one belongs to exactly one workspace. Anyone who can already see that workspace can create, rename and delete them; nobody outside it can see them at all. Each type gets its own section in the left-hand navigation, its own list page, and its own detail page.
All of this is live today. It is on by default — nothing to reveal — and a single setting turns it off again.
Where to find it
Showing and hiding a section
There is nothing to reveal. Each of the three has its own show/hide toggle in Mission Control → Settings → Sidebar, and all three start ON. Turning one off hides only that sidebar section — it never hides the other two, and it never refuses a read or a write.
What you see
- Left navigation gains three collapsible sections — Documents, Spreadsheets, Forms — listing the items in the current workspace. Each section header carries a See all button beside its + that opens the section's full list page.
- Six pages become reachable:
/documentsand/document/:documentId,/spreadsheetsand/spreadsheet/:spreadsheetId,/formsand/form/:formId. - Templates: the template picker offers Documents, Spreadsheets and Forms beside Boards and Dashboards, each with a live count of its built-in starters. Deploying one creates a real item of that type rather than a board.
- Recently visited starts listing documents, spreadsheets and forms alongside projects, dashboards, goals and portfolios, and its empty-state sentence names them too.
How it behaves
What happens when a sidebar section is hidden
Hiding is a display preference, not a feature gate:
- Only that one section disappears from the left navigation.
- The six paths stay reachable — a bookmark or a typed address still opens them.
- Every command-line route keeps answering.
- Nothing is refused, and the other two sections are untouched.
How it works
Storage. Three tables — pm_documents, pm_spreadsheets, pm_forms —
each carrying a workspace_id, an is_deleted flag, and an index on the pair.
Nothing is ever really deleted. Deleting hides an item: it disappears from
every list and every lookup, and its record stays on disk. Someone who deletes
the wrong thing has lost a click, not a week. The is_deleted flag is stripped
from every row handed back, so it never leaks into the interface.
You only ever reach your own workspace's content. Every read and every write is checked against the workspace the item belongs to. Knowing an item's identifier is not permission to see it, and that holds on reads exactly as firmly as on writes. Asking for an item that does not exist stays a plain "not found" rather than an authorization error, so the check cannot be used to probe for which identifiers are real.
How the interface gets its data. Mission Control runs as an isolated sub-app, so it asks its host for data across a bridge rather than talking to the database itself. The host answers all seventeen calls (list / get / create / update / delete for each of the three types, plus submit a response and list the responses for forms). Each answer is validated on the way back: a malformed row degrades to an empty list or a null rather than reaching the interface, and a failed delete tells the user instead of failing silently.
The interface checks no feature switch at all: the three are ordinary project types, so the picker, the template list and Home's recents treat them exactly as they treat boards and dashboards.
Not finished yet
The area is shipped and available to everyone. Still outstanding:
No user-facing help page. This library entry exists; the public help site has nothing on the area yet.
The detail pages now support inline editing. Documents have inline title and content editing. Spreadsheets have inline title and description editing plus an editable grid (click cells to edit, add/remove rows). Forms have inline title, description and status editing plus an editable field list with drag-to-reorder (add/remove fields, set type/label/required/options).
There is no rich text editing yet. Responses are saved and can be read back, and a form page has a Fill out button and an Answers list. With Omni on and allowed, each answer is sorted and filed where the person chooses (see ai-project-manager.md, "Omni on forms"). Saving a document makes Omni pull out its action items and file them the same way, and saving a spreadsheet makes Omni list what looks off, without filing anything (see ai-project-manager.md, "Omni on documents" and "Omni on spreadsheets"). Saving through
PATCH /pm/documents/:idorPATCH /pm/spreadsheets/:idstarts Omni exactly like a save on the page.
Sharing between teammates
Documents, spreadsheets, forms and their responses are shared across a workspace's members. One person creates, edits or deletes one and every other member of that workspace sees it on their next sync (a few minutes, or as soon as they open the app). A team guest sees none of them: a guest is invited to individual boards, and a document has no board to be invited to.
Each type syncs by pulling the workspace's whole collection in one bounded snapshot (200 per type, 500 maximum, and the app is told when a list was cut short) and by pushing whatever this computer changed since the last sync. Two people editing the same item is settled by time: the later save wins, and a save that would overwrite a newer one is re-based once rather than silently dropped. Anything already on a computer when sharing first turns on is uploaded, not discarded.
An app pointed at a server that predates sharing behaves exactly as it did before: everything stays on the computer and nothing is lost or reported as an error.
Related
The workspace this content lives in, and the boards, dashboards, goals and portfolios it sits alongside, are described in mission-control.md. The nearest siblings inside that workspace are pm-goals.md and pm-portfolios.md for the other things a workspace collects, and boards.md for the boards themselves. A reader who arrived here from the template picker will want pm-feature-profiles.md, which decides which Mission Control features a board shows at all, and pm-onboarding-features.md for the import flows that bring content in from other platforms.
Last verified 2026-11-04