35.1 Purpose of Restricted Paths

Restricted paths prevent the Chat widget from mounting on selected URL paths inside an origin that is otherwise allowed to run the Agent.

This allows you to install one widget snippet broadly while keeping the Agent off sensitive, transactional, or inappropriate areas of the same site.

35.2 Opening Restricted Paths

1. Open the Agent.
2. Select Settings.
3. Locate Restricted paths.

The Settings page describes this as the path-level companion to Allowed Origins.

35.3 One Path Per Line

Enter one restricted path or path pattern per line.

Examples include:

• /admin
• /admin/*
• /checkout
• /account/*

35.4 Exact Paths

A value such as:

/admin

matches the exact path itself.

35.5 Wildcard Paths

The * character is used as a wildcard.

For example:

/admin/*

blocks paths underneath /admin rather than only the exact /admin path.

35.6 Case Handling

The deployed Settings guidance indicates that Restricted Path matching is case-insensitive.

35.7 Saving Restricted Paths

After entering the paths, select Save paths.

The interface then reports how many paths are blocked.

35.8 No Restricted Paths

An empty Restricted Paths list means there are no path restrictions. The widget can mount throughout the already allowed origin, subject to its other runtime rules.

35.9 Common Uses

Restricted Paths are useful for areas such as:

• Administrative interfaces.
• Checkout flows.
• Customer account areas.
• Login pages.
• Pages where another support or transaction workflow should take priority.

35.10 Relationship to Allowed Origins

Do not use Restricted Paths as a substitute for Allowed Origins. First authorize the correct website domains. Then use Restricted Paths to suppress the Agent only on specific parts of those websites.

35.11 Testing

After saving, test both an allowed page and a restricted page. Confirm that the widget appears where intended and remains absent from blocked paths.