WitnessAI Documentation
List
Start Here
Start Here
Analytics
Analytics
Conversations
Conversations
Users
Users
Alerts
Alerts
Policy
Policy
Administration
Administration
Apps & Resources
Apps & Resources
Release Notes
Release Notes
Administrator Guide
Administrator Guide
Create a Policy
Below are the steps to create a Policy.
Policies can have one or more Guardrails. For details on each guardrail and its features, see Guardrails.
Create a New Policy
- Click Policies in the left-side menu.
- Click Add New Policy in the upper-right corner of the console.
- Enter a Policy Name and Policy Description.
- Click Continue.
The new policy opens in the editor. Its details sidebar has General and Sources & Destinations, and the Guardrails section is below them.
Configure Source & Destination
In the Source section, add one or more combinations of Any, Users, or Groups.
Choosing Any for both Source and Destination is not permitted. If both are set to Any, the policy is disabled and shows a warning on the Policies list.
In the Destination section, add one or more combinations of Any, Providers, Models, Applications, Private Applications, and Lists.
Add Guardrails
- In the policy editor, go to the Guardrails section.
- Select a guardrail from the list to open its settings.
- Use the toggle to enable the guardrail, then configure its action and other options.
- Repeat for each guardrail the policy should enforce.
See the Guardrails pages for each guardrail's settings.
Choose a Policy Type
On the General tab, the Policy Type field sets what the policy does. A Guardrail policy applies the policy's guardrails. A Block policy applies no guardrails and blocks all activity that matches its sources and destinations.
Save the Policy
Click on the Save button in the upper-right of the page.
Note: Saving a new policy adds it to the Policies list, with a default setting of ENABLED. It’s good practice to toggle off the ENABLED status until the new policy has been tested.
On the Policy page, scroll down to the bottom. New Policies always start at the bottom, just above the Observability Policy that’s pinned to the bottom.
This is a good precaution. Since the Advanced Policy framework processes Policies from the Top down, also called “First-match precedence”, having a brand new, possibly untested Policy appear at the top of the list could have some unfortunate effects, potentially blocking all traffic for everyone.
WitnessAI Documentation
List
Start Here
Start Here
Analytics
Analytics
Conversations
Conversations
Users
Users
Alerts
Alerts
Policy
Policy
Administration
Administration
Apps & Resources
Apps & Resources
Release Notes
Release Notes
Administrator Guide
Administrator Guide
Made with Bullet