Set guardrails for the browser
Control what the agent can do in your demo tenant with an allowlist, blocked buttons and actions, blocked text and a read-only mode checked before each click.
Guardrails decide what the agent may do in your demo tenant. The browser service checks every action against them before it runs, for recorded flows and live clicks alike. The AI never sees these rules and cannot talk its way past them.
Who can do this: Admin, Member; allowing a normally blocked action is Admin only. Viewers can read the guardrails. · Plans: live product mode (Growth and up).
What is checked, in order
- URLs. Only https pages on your demo tenant's host and the hosts on your allowlist. IP addresses, local names and other schemes are always refused. If you add allowed paths such as
/w/demo/(on the Product tab), pages on your tenant's host must sit under one of them; the login page and the start page are always allowed. A link, a redirect or a screen change inside a single-page app that leaves the allowed pages is stopped and the browser goes back to the last allowed page. - Blocked selectors. Elements that match a CSS selector you list, or sit inside one. Password and file inputs are always blocked.
- Blocked actions. Words matched against a button's or link's visible text, label and attributes.
- Blocked text. Your own phrases, in any language or script.
- Read-only mode. No typing, selecting or submitting, except in search boxes.
- Personal data. Anything that looks like an email address or phone number is never typed into your demo tenant.
- Frames. A button or field inside an embedded frame is checked the same way, and the frame's own address must also pass the URL rules. A frame from another site is acted in only if its host is your demo tenant's or on your allowlist.
Defaults that are always on
The agent never clicks anything matching: delete, remove account, deactivate, billing, payment, invoice, subscription, upgrade plan, checkout, purchase, settings, logout, sign out, export, download, invite, API key, API token, password or transfer ownership. Matching is broad on purpose, so it may also refuse a harmless button with a similar label. That is the safe direction.
Allow normally blocked actions
Sometimes a demo needs one of the defaults, such as a walkthrough of role settings or the plans page. A workspace admin can allow these categories for one agent under Allow normally blocked actions on the Guardrails tab:
| Category | Words it allows |
|---|---|
| Settings pages | settings |
| Billing and plans | billing, payment, invoice, subscription, upgrade plan, checkout, purchase |
| Export and download | export, download (the browser still never downloads a file) |
| Invite users | invite (the agent still never types an email address) |
| Delete | delete |
- Open Agents, choose the agent and open Guardrails.
- Under Allow normally blocked actions, turn on the category.
- Type the reason (10 to 200 characters), such as "prospects ask to see role permissions". For Delete, also tick the box confirming the agent may delete records in a demo tenant that resets.
- Click Allow. It applies from the next session. Turn the switch off to block the category again at once.
Every change is recorded in Settings → Activity log with the category, on or off, the reason and who made it. Nothing else moves: read-only mode, the allowed hosts and paths, password and file inputs, the personal-data rule, your own blocked words and text, and remove account, deactivate, sign out, API keys, password and transfer ownership always stay blocked. If you also list a word yourself (for example "settings" in your own blocked actions), your word still blocks it.
Always refused
Popups and new tabs are closed, downloads are cancelled and browser dialogs (alerts, confirmations, prompts) are dismissed, whatever the page or the AI asks. Each check takes well under a millisecond, so guardrails never slow the demo down.
Change the guardrails
- Open Agents, choose the agent and open Guardrails.
- Allowed hosts. Add hosts the browser may load besides your demo tenant, such as
docs.example.com, or*.example.comfor every subdomain. - Blocked selectors. Add CSS selectors for areas the agent must not touch, such as
[data-test=danger-zone]. - Blocked actions and Blocked text. Add words or phrases, one per line.
- Read-only mode. Turn on if prospects should never see the agent fill in forms.
- Click Save, then test a demo and ask the agent to do something blocked.
Suggestions: not sure what to add?
Under each list, Suggestions shows values you can add with one click, such as + close account, + Production or + [data-testid*="delete"]. Hover or tab to a suggestion to see why it is there, for example "Seen on screen Billing settings". Add all adds every suggestion in that list. Suggestions are only added to the form; nothing changes until you click Save guardrails.
Where suggestions come from:
- Your screens. Risky words seen in your screen catalogue come first, and admin areas such as
/developers/webhooksor/adminget a word that keeps the agent from opening them. - A vetted list of actions that change or end something in a real account (close account, revoke, disconnect, refund, publish, send and more), on top of the defaults that are always on.
- Live-environment text such as Production, suggested when your demo tenant's address doesn't look like a demo or staging site.
- Selectors for icon-only Delete or Remove buttons that have no label for the word list to match.
- Extra hosts only when one of your flows opens a page on another host.
A suggestion never blocks a word or page that one of your flows uses, so adding one can't break a flow. Built-in and already-added values are left out.
Suggest more with AI asks AI for ideas that fit your product. It takes a few seconds; the page updates by itself and the new suggestions are marked AI. The AI sees your agent's name, your screens' titles and paths and your flows' names, never your demo login, the values your flows type or anything from a demo. If AI is turned off for your workspace, only the built-in suggestions are shown. You can ask up to 10 times an hour.
What prospects hear
When an action is blocked, the agent says it cannot do that in the demo and offers another way, such as a meeting with your team. For example, asked to "open billing settings", the agent says billing and settings aren't part of this demo and offers to show something else. A blocked action in a recorded flow stops that flow; the agent never routes around a refusal with another selector.
Privacy: the personal-data rule means prospects' email addresses and phone numbers are never typed into your demo tenant, even if a prospect asks the agent to. Collect them with a qualification question instead.
Frequently asked questions
Do guardrails replace a demo tenant?
No. Guardrails are a second line of defence. Always use a dedicated demo tenant. See How TalkDemo protects your demo tenant.
Does the agent work inside web components and embedded frames?
Yes, for live clicks it sees buttons, links and fields inside web components (open shadow DOM) and inside frames from your own site, and every rule above applies there too: a Delete button in a web component is still blocked, and a password field in a frame is never touched. A frame from another site, such as a chat widget, shows to the agent only as a box with its site and title, so it never clicks inside it. Components built with closed shadow DOM can't be reached by live clicks or recorded flows.
Why can't I see the switch for normally blocked actions?
Only workspace admins can change them. Members and viewers see which categories are allowed and why.
Where do I see refused actions?
In the actions timeline of each session. See Review sessions.
Something unclear or missing? Tell us