MSP Per-Client Proof
What it is
Two things for a partner (vCISO, MSP, MSSP) that manages client workspaces:
- A Proof column on the vCISO roll-up (
/vciso) that shows, per client, whether the client's current proof receipts are still fresh. - A white-label proof bundle page: when a client shares proof, the public page carries the partner's name instead of CMDash's, if the partner has white-labelling.
When to use it
To see at a glance which of your clients' proof has gone stale, and to send a client's proof to their customer or insurer under your own firm's name.
Before you start
- Tier: the vCISO console has its own plan requirement; see vCISO multi-client. Receipts themselves need no tier.
- White-label: the partner workspace must hold white-labelling. What counts is the partner's effective entitlement, never the client's own plan.
- Role: sharing a proof bundle from a client workspace is done inside that workspace by an OWNER or ADMIN (the same share dialog used for board packs).
How to
Read the Proof column
Each client shows one of:
| Shown | Meaning |
|---|---|
| Fresh | Every claim that has a current receipt is inside its freshness window. |
| Stale | At least one claim is past its window. One lapsed claim makes the client Stale, even if others are fresh. |
| No receipts | The client has no current receipt. |
| Unavailable | CMDash could not read this client's receipts. This is not "no proof" and not "fresh". |
Fresh and Stale also show "N of M claims fresh". Hover for the claim ids and each claim's state. The column is sortable; the order puts Stale first, then Unavailable, No receipts and Fresh. The roll-up reads a bounded number of a client's current receipts (100).
The column carries only claim ids and freshness times: never a receipt's signature, statement, numbers or evidence. Each client is read under its own workspace context, with no new access.
Send a white-label proof bundle
- Enter the client's workspace and open
/proof. - Select receipts and create a proof bundle share link.
- The public page the link opens, and the verifier it links to, show the partner's name in place of CMDash's mark, heading and the "Start free" prompt, with a footer reading "Provided by <partner>".
The partner name is frozen into the link when it is created, so changing branding later does not change links already sent. If the partner has no white-labelling, or the lookup fails, the page uses CMDash branding. It never fails the share. Only the heading, the tab title and the page chrome change: the verification, the checks and the "what this does not prove" list are exactly the public verifier's.
Common questions
Does the partner see the client's receipt contents in the roll-up? No: claim ids and freshness only. To see a receipt, enter the client's workspace.
Does white-labelling hide that CMDash did the checking? The page is branded as the partner; the verifier is the same code and the receipts are the same signed documents.