Claude Enterprise puts 25 settings sections behind one nav, grouped into four blocks that do not match how anybody actually governs AI. Here is the whole tree, what each block controls, and the six settings worth opening on your first day as an Owner rather than the twenty-five you will otherwise scroll past.
Anthropic now lets an Enterprise organisation put its own server in front of every prompt and return allow or deny before the model runs. It is the strongest inline control Claude has shipped. It also never receives raw image bytes, so a screenshot of the document you are trying to stop walks straight through, and the failure mode when your server goes down is a setting somebody has to choose.
The Enterprise console offers one toggle that keeps all model inference in US regions for a 10 per cent surcharge. Underneath it are two independent settings, one of which is a one-way door you set when you create a workspace and can never change. The surcharge is the part everybody reads and the least expensive of the three costs.
Three tools failed within a minute of each other with three unrelated errors, and the folder they blamed had ordinary permissions the whole time. macOS TCC had revoked it. Two tccutil resets fixed that with no restart, because Terminal and Claude Code hold separate TCC identities and each one needs its own grant.
Ask the Claude add-in in Excel to roll a workbook forward into next month and you get a permissions error, which reads like a misconfiguration and is not one. The add-in has no file management at all, and that limit is missing from the unsupported list. Here is what it does do well, why it beat Claude Code on the same spreadsheet, and the settings field that fixes the complaint everybody has.
Anthropic shipped write tools for the Microsoft 365 connector on July 7, 2026, and left them switched off for every organization that had connected before that date. Nothing in the product says so. Here is how to check in ten seconds, the two admin gates in two different consoles, the scope that deserves a second look, and the write path already running in your building that will derail the diagnosis.
Claude Code sessions can now message each other over a Unix socket on your own machine. I had 23 sessions running and only 14 of them could see each other. Here is what the message channel fixes, what it cannot fix, and why the guard I trusted for months was never a guard at all.
Adding an organization-wide instruction block does add tokens to every prompt, and that objection is correct. A controlled 180-call test on Claude Sonnet 5 shows one brevity line cutting output 23.9 percent and returning 14.2x its own cost, while the block carrying it fails to break even uncached.
A shared Claude conversation returns HTTP 200 whether or not you can read it, and the page carries six characters of visible text. Team and Enterprise chats are organization-only by design, attached files never travel with the snapshot, and the one programmatic route is a Compliance API that has no idea what a share link is.
Claude Code loads your CLAUDE.md into every subagent except two. Explore and Plan skip it by design, and no setting changes that. So the agents you fan out most widely are the ones that never see your rules. ETH Zurich measured what the file costs on the occasions it does load.
A git worktree isolates your working directory and your index. It does not isolate the stash stack, which is shared by every checkout in the repository. Here is what I measured on git 2.50.1, why MERGE_AUTOSTASH escapes the problem through an accident of spelling, and how one defensive stash can make a worktree look safe to delete.
Merge queues, merge trains, and speculative merging all rest on one assumption nobody states: that a per-branch green tick means the code works. Our own CI runs no unit tests at all, and master went red twice in two days from pull requests that were each green on their own. Here is what to build before you buy the queue.