Testing a Policy
There is no built-in policy simulation or dry-run feature in Robost. The recommended way to verify a policy is to exercise it directly with the browser extension installed in your own browser.
Manual testing workflow
Section titled “Manual testing workflow”1. Install the extension in your test browser
Section titled “1. Install the extension in your test browser”Follow the Manual Install guide to load the extension and enroll it against your Robost server. Confirm the options page shows Enrolled: Yes before continuing.
2. Publish the policy you want to test
Section titled “2. Publish the policy you want to test”Open Configure in the admin dashboard and make sure the scenario you want to test has been published. Unpublished changes are not enforced by the extension. After publishing, wait up to one minute for the new rules to propagate.
3. Navigate to the target application
Section titled “3. Navigate to the target application”Open a new tab and go to the AI application covered by your policy — for example, ChatGPT, Claude, or Gemini. App Access policies (Allow / Advise / Block) fire on navigation, so you should see the effect immediately on page load if a matching scenario is active.
4. Submit a prompt containing the relevant content
Section titled “4. Submit a prompt containing the relevant content”For Sensitive Data Detection policies, type or paste content that matches the detection type your scenario targets — for example, a string that looks like a credit card number for a PCI detection type. Submit the prompt.
- If the intervention is No Intervention (Monitor Mode), nothing is shown; proceed to step 5 to confirm the alert was logged.
- If the intervention is Warn, an in-page modal appears. You can acknowledge it (and provide a justification if that option is enabled) and continue.
- If the intervention is Block, an in-page modal appears and the submission is prevented.
5. Confirm the alert was recorded
Section titled “5. Confirm the alert was recorded”If the scenario is configured with Raise Alert, navigate to the Alerts Inbox in the admin dashboard. The alert should appear shortly after the submission, showing the detection type, employee, application, and action taken.
If no alert appears after a minute, check that the scenario is published and that the extension is enrolled against the correct server.