The multi-tenancy your awareness tool was supposed to have.
"Does not handle multiple companies well; the admin workaround is clunky." That's the number-one complaint about the MSP-friendly awareness tools — and it's exactly the gap Watchword was built to close. True parent → child tenancy, one pane of glass, no re-login to switch clients, a cross-client risk board, white-label client reports, and strict per-tenant isolation — running today.
One pane of glass, every client
- Tenant tree: your MSP tenant sits over unlimited client tenants in a single console. Pick a client in the tree and the Training, Templates, Simulator, and Program tabs all operate on that client.
- Switch clients with no re-login: the whole tree is your operator context. One click swaps a client's roster, campaigns, assignments, and progress into the active context — no sign-out, no sign-in.
- Cross-client risk board: one row per client — phish-prone %, high-risk count, completion %, and overdue training — plus portfolio totals, sortable so you know which client to work first.
- White-label client reports: hand a client a report rendered in their brand color, headed with their name and a "prepared by [your MSP]" line — and stating plainly it contains no data from any other client.
- Free NFR tenant for your own team.
Compliance evidence your clients can use
Every client's training completions and sim results become signed Awareness & Training evidence mapped to HIPAA, NIST 800-171 (CMMC L2), SOC 2, PCI, and ISO — and flow into the Sightline / Bastion / Ward graph. If you resell other DosanjhLabs tools, the evidence compounds: one program, many satisfied controls, across every client.
Send safely, per client
Every client tenant carries its own list of authorized send domains. A domain only earns a place on that list by passing a real DNS-TXT proof — publish the TXT record we give you, Watchword does a live DNS-over-HTTPS lookup and requires an exact match. A mandatory domain-authorization gate then clears each recipient per send: no proven domain, no send, ever, with scoped, short-lived per-(tenant, domain) tokens so a leaked token can't be replayed against another client. How sending safely works →