Site Controls
Site Controls allow you to customize how Containment.AI handles specific AI platforms and websites, including recording corporate notices and per-site control types.
:::caution Enforcement gap (known limitation) Site control rules are recorded in the dashboard and API, but released extension versions do not yet consume the per-site control type or display corporate notices. Extension enforcement today follows your organization-wide violation policy (block or allow-and-record) configured during onboarding, applied to violating AI submissions on the monitored platforms. Changing a site's control type after onboarding does not currently change what the extension enforces. This gap is tracked and per-site enforcement is planned. :::
Overview
Site Controls enable:
- Per-site access control (Allow, Monitor, or Block)
- Custom corporate notices on AI platforms
- Site categorization and management
- Pre-configured LLM site monitoring
Accessing Site Controls
Site Controls are managed from the dashboard Overview page and through the API. They allow you to set rules for specific websites your users may visit.
Pre-Configured LLM Sites
Containment.AI comes with default configurations for popular AI platforms:
| Site | URL |
|---|---|
| ChatGPT | chatgpt.com |
| Claude | claude.ai |
| Gemini | gemini.google.com |
| Microsoft Copilot | copilot.microsoft.com |
| Grok | grok.com |
These sites can be customized with your preferred control type and notices.
Site Rule Configuration
Creating a Site Rule
- Click Add Site
- Enter site details:
- Site URL: Domain (e.g.,
chatgpt.com) - Site Name: Descriptive name
- Category: LLM, Social, Productivity, or Custom
- Control Type: Allow, Monitor, or Block
- Site URL: Domain (e.g.,
- Optionally configure a corporate notice
- Save the rule
Control Types
| Type | Intended Effect |
|---|---|
| Allow | Standard policy enforcement on the site |
| Monitor | Enhanced monitoring and logging on the site |
| Block | Violating AI submissions on the site are blocked with a block message |
The extension never blocks navigation to a site — enforcement acts on AI prompt submissions on the monitored platforms. See the enforcement-gap caution above: per-site control types are recorded today but not yet consumed by the extension.
Site Categories
Sites are organized into categories:
| Category | Description |
|---|---|
| LLM | AI language model platforms (ChatGPT, Claude, etc.) |
| Social | Social media platforms |
| Productivity | Productivity and collaboration tools |
| Custom | User-defined category |
Corporate Notices
Record custom messages for controlled sites.
Notice Configuration
When creating or editing a site rule:
- Enable Show corporate notice
- Enter the Notice Title (e.g., "AI Usage Notice")
- Enter the Notice Message (e.g., "All AI interactions are monitored per company policy.")
Notices are designed to display as a banner. Additional display styles (modal, toast) and message template variables are roadmap, not configurable today — and per the enforcement-gap caution above, released extension versions do not yet render notices on the monitored sites.
Example Notice
Title: AI Usage Notice
Message: |
All AI interactions on this site are monitored
per company policy. Do not share confidential
information including customer data, credentials,
or proprietary code.
Blocking Sites
Record a Block rule for an AI platform:
- Add site to Site Controls
- Set Control Type: Block
- Configure the block notice message
- Save
The intended behavior is that violating AI submissions on the site are blocked and the notice explains why. Today, blocking follows the organization-wide violation policy rather than the per-site rule (see the enforcement-gap caution above).
Allowing Sites
Explicitly allow platforms with standard monitoring:
- Add site to Site Controls
- Set Control Type: Allow
- Optionally add an informational notice
- Save
Team Scoping
ProfessionalApply site controls to specific teams:
- Different teams can have different site rules
- Scoped by
team_idon each site control - Allows granular access management
Best Practices
Organization
- Start with default LLM sites
- Add custom sites as needed
- Use clear naming conventions
Notices
- Keep messages concise
- Update messages regularly
Access Control
- Use Monitor for initial assessment
- Escalate to Block only when needed
- Document justifications for blocked sites
Troubleshooting
Notice Not Appearing / Site Not Blocked
Released extension versions do not yet consume per-site control types or render notices — see the enforcement-gap caution at the top of this page. If violating submissions are not being blocked at all:
- Verify the extension is installed and the user is signed in
- Check your organization-wide violation policy is set to block
- Confirm the site is one of the monitored AI platforms
Related Topics
- Chrome Extension - Extension settings
- Policy Configuration - Policy setup
- Integration Overview - All integrations