---
title: On-device enforcement
description: How we check sessions and carry out your Allow, Warn, and Block actions on the endpoint itself.
---

We carry out your asset actions and session policies on each endpoint. When you change one, we signal online endpoints over a live connection and they fetch the change: within seconds for asset actions, within about a minute for session policies. An offline endpoint picks it up at its next scan.

## Session policies

When a tool reports a prompt, we check it against your session policies right on the endpoint, before it is buffered for upload. The check itself never waits for our servers. Each message that matches earns the policy's tag, and the tags travel with the session so it shows up as an incident in the console.

What happens next depends on the tool:

- **Claude Code**: we answer the prompt before it reaches the AI provider. Allow lets it through. **Block** (Beta) stops it and shows the person your message. Warn lets it through and marks the session as warned, which you see in the **Enforcement** column on Incidents and Sessions.
- **Codex and AI websites in Chrome**: we tag the session on the endpoint, so it appears under **Incidents › Sessions** for you to review.

You write the message people see when we block a prompt in the policy's **Message to users** field.

:::info
Block is in beta. We're still improving it, so try it on a small group of endpoints before you apply it to everyone.
:::

## Asset actions

For installed AI assets, your action applies per endpoint:

| Action | On the endpoint |
| --- | --- |
| **Allow** | Nothing is removed. The asset is recorded as approved |
| **Warn** | The person gets a **WARNING** notification each time the asset opens |
| **Block** (Beta) | We back the asset up, then remove it. If removal fails, we close the asset each time it opens, within a few seconds of launch |

Blocked assets are kept in a local backup for 30 days before we purge it. Switching a blocked asset back to Allow doesn't reinstall it — the person installs it again, and we leave it alone from then on. A blocked browser extension stays in memory until the browser restarts, then it's gone.

## Where to look next

- [Incidents](/surface/incidents/overview) — where the decisions wait, and what resolving does
- [Session Policies](/surface/policies/session-policies) — setting an action and its message
- [Asset Remediation](/surface/policies/asset-remediation) — Global and By Instance scopes
