Skip to content
TalkDemo
Template · Guardrails

Guardrail checklist for demo tenants and AI demo agents

Tick these before an AI agent or a new hire demos your product: the tenant, the login, allowed URLs, blocked actions and reviews.

How it works

Short answer: A guardrail checklist for demo tenants lists what to set up before anyone, a new hire or an AI agent, demos your product in a shared demo account. It covers five areas: the tenant and its sample data, how the login is stored, which URLs the demo may reach, which buttons and actions are blocked, and how actions are logged and reviewed. Copy the checklist below and tick each item before go-live.

Key takeaways

  • Never demo in production, and never put real customer data in the demo tenant.
  • Keep the demo login in a vault, out of prompts, docs and flow steps.
  • Allow only the URLs the demo needs, and block destructive actions by name.
  • Review refused actions weekly; each one is a flow or a rule to fix.

The guardrail checklist for demo tenants

Demo tenant guardrail checklist (plain text)
GUARDRAIL CHECKLIST FOR A DEMO TENANT

The tenant
[ ] A separate account or workspace used only for demos, never production
[ ] Realistic sample data, no real customer names, emails or phone numbers
[ ] A dedicated demo user with the smallest role that can show every flow
[ ] A reset plan: how and how often the sample data goes back to a clean state

Credentials
[ ] Demo login stored in a vault, not in a prompt, a doc or a flow step
[ ] Two-factor sign-in off for the demo user, or handled by the browser service
[ ] Password rotated after anyone with access leaves the team

Where the agent may go
[ ] URL allowlist: only the hosts and paths the demo needs
[ ] Links to billing, account settings, user invites and data exports blocked

What the agent may click
[ ] Blocked buttons and actions: delete, remove, cancel subscription, invite, export, send email, change password
[ ] Read-only mode for forms if saved changes would confuse the next demo
[ ] File uploads off unless a flow needs them

Watching it
[ ] Every action and refused action logged with the session
[ ] Someone reviews refused actions weekly and fixes the flow or the rule
[ ] Flows re-checked after each product release

Why an AI agent needs stricter rules than a person

A person giving a demo knows not to click Delete account. An AI agent only knows what it is told, and a prompt is not a control: a buyer can ask it to do something odd, or text on a screen can look like an instruction. Limits that matter should be checked in code before each click, with the agent's instructions as a second layer, not the only one.

Use it in TalkDemo

  • Demo credentials are sealed and typed into the login form by the browser service; the AI never sees them.
  • The agent's Guardrails tab holds the URL allowlist, blocked selectors and actions, and read-only mode.
  • Every browser action passes a guardrail check in code before it runs, and refused actions are logged on the session timeline.
  • Flow health marks a flow as broken after repeated failures at the same step, so release changes surface quickly.

See guardrails and how TalkDemo protects your demo tenant.

FAQ

Questions about guardrail checklist for demo tenants

A separate account or workspace of your product that exists only for demos, filled with realistic sample data instead of real customer records.

Only if a flow you demo needs admin screens. Give the demo user the smallest role that shows every flow, and block the rest by URL and action.

After each product release and whenever the sample data starts to look used. Read-only mode reduces how often you need to.
Private pilots

Let your product give the next demo

We set up your first agent with you: your core flows recorded on your demo tenant, your docs indexed and your qualification questions agreed. Then you test it before it goes live.

Talk to us