Partner scenarios

Partner scenarios are private to your account by default. Build one when you want to deliver an exercise that's specific to a customer's sector or situation.

Authoring

• Open Partner → Scenarios and click New.
• Add cutscenes, decisions and outcomes. The editor mirrors the live experience so what you see is what they'll play.
• Tag against industries and the CLEAR Decision Loop stages.
• Publish to make it available to share.

Sharing what you've built

Once a scenario is published, open the "Share this scenario" panel on the builder page. You have four ways to share — pick the narrowest one that does the job:

• Keep it private — the default. Only you (and our support team, see below) can see it.
• Share with a specific person — pick someone you're already linked to. They'll see it in their scenario picker straight away.
• Share with everyone in your workspace — every linked customer or partner will see it. Use sparingly.
• Generate an invite code — hand the 6-character code to someone outside your linked list. They redeem it from their dashboard.

You can revoke any share from the same panel at any time. Revoking stops new people seeing it, but anyone who has already loaded the scenario into a session will finish that session normally.

Protecting company and client data

A scenario is training content, not a live case file. Before you write — and before you share — think about what would happen if the wrong person saw it.

• Don't use real names. Use roles ("the duty manager", "the regional finance lead") or made-up names. Same goes for clients — "a national retailer" beats "ACME Foods Ltd".
• Don't paste live secrets. No real passwords, IP addresses, account numbers, regulator case references or system names that would identify a specific environment.
• Strip identifying detail from real incidents. If you're basing a scenario on something that actually happened, change the sector, scale, location or timing so it can't be reverse-engineered.
• Check what AI suggestions added. The AI choice and inject helpers occasionally pull in plausible-sounding names or organisations. Read the suggestion before you accept it.
• Match the share scope to the audience. A scenario built around a single customer's situation should be shared with that customer only — not workspace-wide.
• Treat invite codes like passwords. Send them over a channel the recipient controls. Revoke and re-issue if a code ends up somewhere public.

Who else can see your scenarios?

Our platform administrators can view scenarios you author — including drafts you haven't shared — for support, debugging and content moderation. Every admin view is recorded in an audit log. This is the same access model that applies to the rest of your account (see the Privacy notice for the full detail). It's another reason to keep authored content generic and free of real personal data.