Closing thoughts
Models and harnesses have become more advanced, allowing organizations to not just transform how they produce code, but the entire software development lifecycle. This transformation keeps human judgment central to the process and considers the governance and regulation requirements of large enterprise organizations.
This guide consolidated many of the real best practices our Applied AI team executes on a daily basis for our customers, and we hope you found it a practical and actionable resource.
Resources
The documentation below is what a platform team needs to set up the controls described in this guide, in roughly the order you would roll them out.
- Set up Claude Code for your organization(opens in new tab) (the admin decision map; start here)
- Settings reference and precedence, including every managed-only key(opens in new tab)
- Server-managed settings from the Claude admin console(opens in new tab)
- Permissions(opens in new tab)
- Sandboxing(opens in new tab) (OS-level filesystem and network isolation)
- Hooks guide(opens in new tab) and hooks reference(opens in new tab)
- Skills(opens in new tab)
- Plugins and private marketplaces(opens in new tab) (how skills and hooks are distributed organization-wide)
- Managed MCP(opens in new tab) (central control of the agent's tool surface)
- Enterprise deployment overview(opens in new tab) (Amazon Bedrock, Vertex AI, Microsoft Foundry)
- Enterprise network configuration(opens in new tab)
- Monitoring (OpenTelemetry)(opens in new tab) and the analytics dashboard(opens in new tab)
- Compliance API(opens in new tab) (Enterprise activity feed, chat retrieval and deletion)
- Security model(opens in new tab)