Creating a Policy

Where to find it

Navigate to Configure in the left sidebar (the SlidersHorizontal icon). The page is titled Configuration Designer and is available at /configuration.

How policies are structured

The Configuration Designer organises rules into two sections:

• App Access — controls whether employees can use an AI application at all.
• Sensitive Data Detection — controls what happens when the extension detects sensitive content in a prompt.

Each section has one Default Scenario (applies to all employees and all applications) and any number of Exception Scenarios (narrower rules that override the default for a specific subset). Exception scenarios are evaluated in priority order; the first matching scenario wins.

Creating an exception scenario

1. In the relevant section, click the + card at the end of the exception scenario row. This opens the Add Exception Scenario side panel.

2. Fill in the Scenario Name field. The name is required; an error message is shown if you attempt to save without one.

3. Set Conditions. Each condition shows a pill-shaped button that opens a searchable dropdown. For App Access scenarios the available conditions are:

   • Where the Employee is — search and select specific employees, or leave as “All Employees”.
   • and the App is — select specific application plans or app groups, or leave as “All Applications”.

   For Sensitive Data Detection scenarios, two additional conditions are available:

   • and the Domain is — select specific domains observed in your environment.
   • and the Detection Type is — select from the 25 detection types in the registry, or leave as “All Detection Types”.

   Clicking “Select specific” on any condition switches it from all-inclusive to a specific list. Clicking “Use all” reverts it.

4. Choose an Outcome (App Access) or configure Alerts and Interventions (Sensitive Data Detection). See Actions for what each option does.

5. Click Save. The scenario is created immediately and appears in the section’s exception scenario list.

Editing or deleting a scenario

Click any existing exception scenario card to open the edit panel, pre-populated with its current settings. Make changes and click Save. To remove a scenario, click Delete Scenario at the bottom-left of the edit panel. The default scenario cannot be deleted; only its action and enabled state can be changed.

Publishing changes

After saving, an Unpublished Changes badge appears on the section header and a sticky footer bar is shown. The footer displays a note about propagation timing (“Please Note: Enabling interventions may take up to 1 minute to take effect and will only apply to new tabs or navigation.”) and two buttons:

• Publish <Section> Changes — snapshots the current scenario list and pushes it live. The extension will begin enforcing the updated rules within approximately one minute on new navigation.
• Reset to Last Published — discards all unpublished edits and restores the last saved snapshot.

Publishing is per-section; publishing App Access does not affect Sensitive Data Detection and vice versa.