# How to turn AI off for one team

Guide, 8 Nov 2026, read 8 Nov 2026

**The short answer.** Three platforms publish an off switch on 8 Nov 2026: Shapes (separate switches for AI chat, AI-built Vibes and MCP access, on by default, under Account settings and Security), Rippling ('admins can enable or disable AI features') and BambooHR (a setting under Account Settings). None of the three publishes a per-team switch; the rest publish less. The workaround is permissions.

## What is published

| Platform | The switch, as published |
| --- | --- |
| Shapes | Three separate switches: AI chat, creating and editing Vibes with AI, access from external AI tools through MCP; all on by default; super admin, Account settings, Security. |
| Rippling | 'Admins can enable or disable AI features.' |
| BambooHR | Bamboo AI on or off under Account Settings, Ask BambooHR. |
| HiBob | MCP is turned on company-wide in Bob; no agent switch stated. |
| Workday | Agents registered and governed in the Agent System of Record; no single switch. |
| Gusto | The admin chooses data categories for the MCP server; users disable automatic tool execution in their client. |
| Lattice | Admins activate the AI Agent in a setup experience; role access left to the admin. |
| Humaans, Personio, Deel, Factorial, Sage, ADP, Paylocity, Taito.ai, Leena AI, Moveworks | Not stated on the pages read. |

## Turning it off for one team

No vendor on the matrix publishes a per-team switch. The route that exists is permissions: an agent that acts under each person's permissions (Factorial's wording, Shapes's permission-aware views, HiBob's 'within permissions') does nothing for a team whose role cannot see the agent's inputs. Shapes's field-level permissions, Rippling's attribute-keyed policies and Workday's security groups are the permission models that reach the field; a team can be fenced off from the agent's data where the agent cannot be fenced off from the team.

## The connector switch

The outside door is separate. Shapes's MCP access switch turns off every outside client at once; Gusto's admin scoping limits what categories the server exposes; HiBob's server is on company-wide. A leaver's token is the case to test: revoke access in the HRIS and check the client no longer answers.

## Sources

- Shapes AI switches: https://shapes.co/releases/turn-ai-features-on-or-off (read 8 Nov 2026)
- Rippling AI: https://www.rippling.com/platform/ai (read 8 Nov 2026)
- Bamboo AI settings: https://www.bamboohr.com/product-updates/bamboo-ai (read 8 Nov 2026)
- HiBob MCP: https://www.hibob.com/platform/core/ai/mcp (read 8 Nov 2026)

Last reviewed 8 Nov 2026. Canonical: https://bestaiagentsforhr.com/guides/how-to-turn-ai-off-for-one-team/
