Informational Fresh jira_story: GOV-320

Lesson 1 of 4 — Portfolio Command Centre multi-tenant

Scale & Intelligence · Source: Jira Story GOV-320 (13 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Add a multi-tenant portfolio rollup for MSPs.

Why it matters

Service providers need one view across all governed tenants.

Where this lives

Runs in the Customer AI Governance platform (components: command-centre). A portfolio Command Centre aggregates posture across tenants with isolation preserved. Learn teaches this read-only.

Workflow

Given an MSP with many tenants
When they open the portfolio view
Then a cross-tenant rollup renders

Worked example

An MSP governs 40 tenants. What does the portfolio view show, and what must it never do?

A cross-tenant posture rollup — while never leaking one tenant's data into another's.

Acceptance criteria (authoritative — GOV-320)

Given an MSP with many tenants, when they open the portfolio view, then a cross-tenant rollup renders.

Common pitfalls

Leaking one tenant's data into another's rollup.

Knowledge check

Scenario: An MSP governs 40 tenants. What does the portfolio view show, and what must it never do?
Look for: A cross-tenant posture rollup — while never leaking one tenant's data into another's.

Key concepts

portfolio rollup
multi-tenant
MSP view

For the AI Tutor

Summary: Add a multi-tenant portfolio rollup for MSPs.
When to use: teaching or answering questions about "portfolio command centre multi-tenant".
When NOT to use: the single-tenant role-shaped aggregate (that is GOV-140).
Key concepts: portfolio rollup, multi-tenant, MSP view.

Completion criteria

Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-320's acceptance criterion.

Module: LEARN-MOD-011 (Scale & Intelligence)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-055