Visibility

Make your agent public for embedding or private for testing only.

Visibility controls whether your agent can be embedded on external websites or is only accessible in the dashboard Playground.

Visibility Settings

Public

  • Widget can be embedded on websites
  • Anyone with the embed code can use the agent
  • Domain restrictions still apply (if configured)

Private

  • Widget cannot be embedded externally
  • Only accessible in the dashboard Playground
  • Useful for testing and development

Configuring Visibility

  1. Go to your agent's Settings tab
  2. Click Security
  3. Find Visibility
  4. Toggle Private on or off
  5. Save changes

When the toggle is off, the agent is Public. When it is on, the agent is Private.

When to Use Each Setting

Use Public When

  • Agent is ready for visitors
  • Training content is complete
  • You've tested in Playground
  • Embed code is on your website

Use Private When

  • Still building/training the agent
  • Testing new content or settings
  • Not ready for public use
  • Using as an internal tool

Switching Between Settings

You can change visibility at any time:

Going from Private to Public:

  1. Test thoroughly in Playground
  2. Verify all content is appropriate
  3. Configure domain restrictions
  4. Set rate limiting
  5. Switch to Public
  6. Deploy embed code

Going from Public to Private:

  1. Switch to Private
  2. Widget immediately stops loading
  3. No visitor data is lost
  4. Resume by switching back to Public

What Happens to Existing Conversations

Switching visibility doesn't affect:

  • Existing conversation history
  • Collected leads
  • Training content
  • Settings

It only affects whether new sessions can start via the embedded widget.

Private Agent Use Cases

Development and Testing

Keep agents private while:

  • Building initial training content
  • Testing new AI instructions
  • Experimenting with actions

Internal Tools

Use private agents as:

  • Internal knowledge bases (access via dashboard)
  • Team-only documentation assistants
  • Testing grounds for new features

Staging/Preview

Maintain separate agents:

  • Production: Public, on live site
  • Staging: Private, for testing changes

Visibility + Domain Restrictions

Both can work together:

VisibilityDomain RestrictionsResult
PublicNoneWidget works everywhere
PublicConfiguredWidget works only on listed domains
PrivateAnyWidget doesn't work anywhere (dashboard only)

For maximum security, use Public visibility with strict domain restrictions.

Next Steps