Omniscio

Mission Control Comment Visibility

Mission Control Comment Visibility puts a lock-or-globe choice on every comment: internal comments are for the team, external ones are visible to stakeholders. The default is internal, and the read path filters by the reader's board role so a viewer cannot be shown a team-only note.

On this page

What it is

Mission Control Comment Visibility adds a visibility mark to each comment on a board item. Every comment is stored as internal or external, and the mark travels with the comment wherever it is read — the item's comment thread and the item's activity timeline both respect it.

The idea is simple: a team discusses an item among itself, then chooses which parts of that discussion an outside stakeholder may see, one comment at a time, rather than maintaining a second channel for the outside world.

The switch is pmCommentVisibilityEnabled, on by default and listed in Settings → Lab.

Where to find it

  • An item's comment thread shows an "Internal" badge on internal comments and none on external ones, and the composer's lock/globe button switches the next comment's visibility (data-ui-anchor="pm-comment-visibility-toggle").
  • The item's activity timeline shows the same comments under the same rule.
  • Settings → Lab → Mission Control Comment Visibility turns the whole surface on or off.

How it behaves

The two values

internal and external are the only two visibility values a comment can carry. The composer starts on internal every time it opens, so the safe choice is the default and making a comment external is a deliberate act — the button is labelled "Internal (team only)" or "External (visible to stakeholders)" accordingly.

Who sees what

Reading is filtered by the reader's board role, not by the comment's author:

Reader Sees
Board owner, admin or member every comment, internal and external
Anyone else (a guest or viewer who is not a board member) only external comments

The filter is applied in the main process on the way out, so an internal comment is never sent to a client that should not have it — filtering is not a display-only rule. The same predicate is used for the item timeline, so a viewer cannot recover an internal comment by switching views.

Downstream use

A comment's visibility rides along on the board event the automation engine receives (comment_added), so an automation can tell an internal note from one shared with stakeholders — for example to notify the outside contact only for external comments.

Comments themselves are described in mission-control-part-3.md; boards, roles and sharing are in mission-control.md and mission-control-part-4.md. Every other page in this library is listed in INDEX.md.

Last verified 2026-11-10