Configure Claude for your organization
Pick a use case, toggle features on or off, and see exactly which admin settings your deployment needs. The checklist on the right tracks what to configure — and in what order.
Use cases by industry
Select your industry. These are the use cases we see most — each carries a different configuration profile.
Why configuration matters
Every Claude use case carries a different configuration profile. Settings interact in non-obvious ways, and the wrong combination can either break functionality or expose your organization to risk.
Skills require Organization > Libraries > Skills > Cloud Code Execution to be enabled — without it, skills and plugins won't run. As such, further understanding of Code Execution settings (e.g. network egress) is necessary to implement skills securely.
Organization > Claude in Chrome > Enable for your Team is essential for legal research workflows that need to navigate case law databases. But for clinical documentation, where patient portals are in the browser, enabling Claude in Chrome without a strict blocklist means Claude can access those sessions with the user's credentials. Same toggle, completely different risk profile.
An example: a tenant used for code review in Claude Chat alongside financial analysis needs network egress for package installs, but that same egress path is a risk for the financial analysis use case handling MNPI. Multi-use-case tenants need configurations scoped to the most sensitive workflow, not the most convenient one.
Stop guessing at configurations
Tell us your use cases. We map every relevant setting path to a clear recommendation — what to enable, what breaks functionality if disabled, and the specific risks for your combination.