Skip to content

Dashboard: shared vs private tabs + role/scope-gated visibility #101152

Description

@100yenadmin

Control who sees which tabs, instead of every operator seeing everything.

Part of the Modular Dashboard roadmap — see the tracker #101136. Builds on Wave 1 (#101093; PRs #101094 / #101097 / #101098).

Problem

The dashboard has no visibility or scoping model — every operator sees every tab, regardless of whether it's a personal scratch view or something meant for the whole team. Small-business operators sharing one dashboard with contractors or teammates have no way to keep a tab private.

What this adds

  • A visibility/scope field on tabs: shared vs private, with room for role/scope gating.
  • Enforcement in the store so private tabs don't leak to other operators.
  • UI filtering so operators only see tabs in their scope.

How it'd be built

Add a visibility/scope field to the tab schema (extensions/dashboard/src/schema.ts), enforce it wherever the store reads/writes tabs, and filter tab lists in the UI by the requesting operator's scope.

References

Tier 3 — control-hub / multi-user.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:needs-security-reviewClawSweeper marked this issue as needing security-sensitive review.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:securitySecurity boundary, credential, authz, sandbox, or sensitive-data risk.impact:ux-frictionUser-facing flow adds avoidable confusion or support burden without fully blocking progress.issue-rating: 🌊 off-meta tidepoolIssue quality rating does not apply to this item.maturity:stableIssue affects a taxonomy feature currently scored M4/M5.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions