Skip to content

Actions

An action is the enforcement response the Robost extension applies when a scenario matches. Different actions are available depending on which section — App Access or Sensitive Data Detection — the scenario belongs to.

These actions control whether an employee can use an AI application at all. They are set in the Outcome field of an App Access scenario.

ActionLabel in UIWhat happens
allowAllowAccess is permitted. The employee receives no intervention.
adviseAdviseA small banner appears when the employee navigates to the application.
blockBlockA full-page block prevents the employee from interacting with the application.

For Sensitive Data Detection scenarios, the action is configured through two independent controls: Alerts and Interventions. These are separate fieldsets in the scenario editor.

ValueLabel in UIWhat happens
no_alertNo AlertNo alert is created. Activity may still be monitored depending on the intervention chosen.
raise_alertRaise AlertAn alert is logged and appears in the Alerts inbox for admin review.
ValueLabel in UIWhat happens
monitorNo Intervention (Monitor Mode)Nothing is displayed to the employee. Activity is recorded silently.
warnWarnAn intervention modal is shown, but the employee may proceed after acknowledging it.
blockBlockAn intervention modal is shown and the employee cannot continue; the submission is stopped.

When Warn is selected, an optional Request justification from employee checkbox becomes available. When enabled, the employee is required to supply a written justification before proceeding.

Alerts and interventions are independent. For example, you can set No Alert with Block to stop a submission silently, or Raise Alert with No Intervention (Monitor Mode) to log activity without disturbing the employee. Any combination is valid.

After publishing a section, new action settings apply to new browser tabs and navigation events within approximately one minute. Existing open tabs are not immediately affected.