Omniscio

PM Portfolios

A portfolio groups projects. Its page shows Total items, Done, Overdue and "At risk: N of M projects", names the riskiest project with a one-line reason, and tags every project High, Medium, Low, "Not enough data yet" or "Couldn't check right now". The numbers are worked out once on the server, so the page, the CLI and the AI always agree.

On this page

Cross-board aggregation for Mission Control: group multiple boards into a named portfolio and see a unified status summary.

What it is

A portfolio is a named grouping of projects within a workspace. Each has a title, an optional description and a list of linked projects.

Its roll-up is computed once, on the server, from this computer's synced copy of your projects:

  • Total items and Done — every live, unarchived item; "done" uses the app's one finished rule (a done status or a done group).
  • Overdue — unfinished, unarchived items with a date before today.
  • At risk: N of M projects — each project's risk comes from the risk heatmap's own score over all open work (High from 0.7, Medium from 0.4, Low below). A project that has never finished any work reads "Not enough data yet" and never counts as at risk; a project whose score could not be worked out reads "Couldn't check right now". Both still count in M.
  • Riskiest — the highest-scoring at-risk project (a tie goes to more overdue items, then A to Z), with a reason such as "6 items overdue and work is slowing down".
  • Status distribution — items by the label of each project's first status column.

Only projects you are a member of are shown or counted. A linked project you are not a member of — another account's, or a teammate's project you were not added to — never appears, and you can only link projects you are a member of.

Where to find it

Portfolios live in a Mission Control workspace. You create one there, give it a title and optional description, link the boards you want it to cover, and open its summary view to see the cross-board rollup. The same operations are exposed over the CLI routes listed under For agents, so a portfolio can also be built and read programmatically.

How it behaves

  1. Create — workspace-scoped, with a title and optional description.
  2. Link / Unlink projects — add or remove projects; the summary refreshes.
  3. View the summary — the portfolio's own page shows the four tiles, the progress bar, the Riskiest note (with "Also at risk" and "not enough data yet" lines, an "Open <project>" link and a "See the risk heatmap" link while Omni is on, which opens the heatmap in Omni's Control Center), the status bar, and a risk tag on every project row. A portfolio with no projects says so and offers Link Project.
  4. Ask the AI — on Home or My Work, "How is the Q4 Launch portfolio doing?" (or just "How is Q4 Launch doing?") answers from the same roll-up and ends with an "Open Q4 Launch" button.
  5. Delete — soft delete (is_deleted = 1) that cascades to project links within a transaction.

Portfolios need you signed in to Omniscio: signed out, the page and the CLI refuse every portfolio action and ask you to sign in. Portfolios, the Home / My Work question box and goals are desktop-only for now — a paired phone or web access cannot reach them (decided 2026-10-17). Portfolios are planned to come back to the phone before public launch.

Portfolios need you signed in to Omniscio. With nobody signed in, every portfolio action answers "Sign in to Omniscio to use portfolios." and changes nothing, and the AI question box leaves portfolios out of its answers: it does not name or count one, and it does not trace a board through one. Board answers still work. Portfolios also stay on the computer: a paired phone or web access cannot open them, and cannot use the AI question box.

Sharing between teammates

Portfolios and their links to projects are shared across a workspace's members: one person creates, edits, links or deletes a portfolio and every other member of that workspace sees it on their next sync. This is about PEOPLE, and it does not change the desktop-only device rule above: a paired phone or web access still cannot open a portfolio. A team guest sees no portfolios, because a guest is invited to individual boards and a portfolio belongs to the workspace.

The sync pulls the workspace's portfolios and links in one bounded snapshot and pushes this computer's changes; anything already on a computer when sharing first turns on is uploaded rather than discarded.

mission-control.md is the parent feature doc, and pm-predictive-analytics.md explains the risk heatmap whose score each project's risk tag comes from, and pm-cross-board-intelligence.md covers the AI question box that answers portfolio questions. If what you want to roll up is not boards but objectives above them, pm-goals.md covers goal tracking, which sits one level higher. The full list of library pages is in INDEX.md.

Last verified 2026-11-04