Editing an Access Policy
Change the name, scope, or action of an access policy that is already in force.
You edit a policy from the Edit Policy panel, which opens with the current configuration already filled in. Nothing changes until you save.
Changes take effect as soon as you click Update. There is no separate deploy step, so a policy governing live agent traffic starts behaving differently straight away.
Steps
-
Go to AI Security › Policy.
The Access Policies tab opens by default.
-
Find the policy you want to change.
Use Search policies if the list is long. The Action column tells you whether the policy currently allows or denies, and the Status toggle whether it is in force.
-
Click the policy.
The Edit Policy panel opens, showing the name, description, source, destination, and action of the policy.
-
Check that the Policy Name field shows the policy you intended.
The panel opens from a row click, so this is the only confirmation that you have the right one.
-
Make your changes.
Policy Name and Description identify the policy. Renaming it does not affect anything that refers to it.
Source sets whose calls the policy applies to, and any source IP restriction.
Destination sets which gateway connector and which tools it covers.
Action sets whether matched calls are allowed or denied, and whether a notification is raised.
For any individual change, see the topic for that setting.
-
Click Update.
The panel closes and the change takes effect. The Last modified by and Last modified columns update on the policy row.
-
If the policy still does not behave as you expect, check its position in the order.
Because policies are evaluated top-down and the first match wins, a policy may be correct and still never reached. Use Change Priorities to move it.
Result
The policy is updated and applies to agent traffic immediately.