Omniscio

PM Personal Saved Views

PM Personal Saved Views are private board layouts owned by one person: only its owner can see or change it, and it never alters the board for anyone else. When a personal view turns out to be useful to the whole team, its owner can promote it into a shared view.

On this page

What it is

PM Personal Saved Views adds a second kind of saved view to Mission Control boards. A board already has shared views, which everyone on the board sees. A personal view is the opposite: it belongs to one Omniscio user, is stored against that user's key, and is returned only to them.

Both kinds carry the same kind of payload — a view type and a JSON configuration blob describing the layout — so a personal view behaves exactly like a shared one while it is private, and keeps behaving that way after it is promoted.

The feature ships hidden: the switch is pmSavedViewsEnabled in Settings → Lab and starts off.

Where to find it

  • A board's view switcher lists your personal views beside the board's shared views; the panel that manages them can create, rename, reconfigure and delete your own.
  • Settings → Lab → PM Personal Saved Views is the global on/off switch.
  • A personal view's menu carries the promote action, which turns it into a shared view.

How it behaves

Private by ownership

A personal view is created with the board id, a name (up to 256 characters), a view type (up to 64 characters) and an optional configuration blob. It is stored with the creating user's id, and every personal-view call resolves the signed-in Omniscio user rather than the active Claude credential — which is why one person's views can never be listed under another's key.

Listing returns only the caller's views for that board. Updating or deleting someone else's view is refused. Deleting is a soft delete, so a mistaken delete does not destroy the row.

Promoting to a shared view

Promotion converts a personal view into a shared one exactly as it was: the same name, type and configuration, with the personal flag cleared and the owner key removed. Only the owner of the personal view can promote it, and the promote call takes no options, so nothing about the view can change at promotion time.

Promotion is one-way in the UI: a shared view is no longer "yours", so it disappears from your personal list and appears to everyone on the board.

The configuration blob

The configuration is a JSON string, capped at 50 KB and validated as parseable JSON at the write boundary. That bound exists because the value is read back with JSON.parse when the board renders: an unbounded or malformed blob would be a storage and a crash risk, so a bad value is refused when it is saved with a friendly message instead.

Boards, views and how sharing works are described in mission-control.md and mission-control-part-2.md; item-level sharing and roles are in mission-control-part-4.md. Every other page in this library is listed in INDEX.md.

Last verified 2026-11-10