◈AI Codex
Setting up Claude for your companyStep 1 of 14
← Prev·Next →
Business Strategy & ROIField Note

You've been asked to set up Claude for the company. Start here.

In brief

The first two weeks for whoever owns a Claude rollout, as of November 2026: learn how each team works before you configure anything, set the few controls that matter on day one, and know what a good first month looks like.

5 min read··Claude Plans

Contents

♡Sign in to save

Someone decided the company should use Claude, and the setup landed with you. This page covers your first two weeks. It assumes you run IT or operations, not that you are an AI specialist.

Last checked: November 16, 2026. Admin features change every few weeks, and Anthropic's release notes are the record.

Two ways to roll out

Pick one per team. Most companies end up using both.

  • Careful. Set up one team at a time, have shared context ready before anyone logs in, and start with one or two people who want it. This suits legal, finance, compliance and teams that are wary of AI.
  • Wide. Set up the account, the connectors and the guardrails, then let people find their own uses. This suits teams that are already curious and have a manager who backs the effort.

Neither is wrong. Trouble starts when a cautious team gets the wide rollout, or an eager team waits months for the careful one.

Week one: learn the work before you configure anything

The most common mistake is building Projects and instructions before you know what each team does all day. Spend the first week talking to people. Ask each team what they write, summarize or look up over and over, where that information lives, and what they have already tried with AI.

That last question tells you the most. Plenty of people already use AI on their own, and they know where it helps.

By the end of the week you should know four things.

  1. Where to start. Teams with a lot of repetitive written work, such as support, marketing, operations and HR, usually see value first. Engineering will want Claude Code, which has its own setup (step 4 below).
  2. Who owns it in each team. One person who knows the work well and will answer questions. Often that is not the manager.
  3. Which plan. Team suits a department, or a company of up to 150 people. Enterprise is for when you need SCIM, audit logs, the Compliance API or custom retention. The Team vs. Enterprise guide has the full list.
  4. What needs a human check. Usually customer-facing text, personal data, and anything that commits the company to money or a contract. Decide what connectors may change, as well as what they may read.

Week two: set up the shared pieces

Do these in order.

  1. Sign-in. Turn on SSO. Then choose JIT provisioning, which creates accounts on first sign-in but never removes them, or SCIM on Enterprise, which also removes people when they leave.
  2. Spend limits. Set an org cap and a per-person cap before launch. Enterprise bills usage at API rates on top of seats, so this matters more there. Enterprise can also keep the most expensive models to the roles that need them.
  3. Connectors. Add the few that most people need, usually your documents tool, your chat tool and email. Once those are in, look at Ask Your Org, which searches them all at once.
  4. Claude Code rules, if developers are on the plan. The defaults are permissive, so push managed settings for tools, folders and MCP servers before people start.
  5. Projects, only where a team shares context. Support needs the product docs and marketing needs the brand voice. If people mostly work on their own, skip Projects for now and add them when a real need shows up.

On Enterprise, chat and Cowork became a single experience by default on November 16, 2026, unless an admin had already chosen otherwise. The admin checklist lists the settings to check.

For every control and which plan has it, see Claude admin controls in 2026.

What good looks like at 30 days

  • People in several teams use Claude every week, beyond the early fans.
  • At least one team has changed how it does a piece of real work and can say what it saves.
  • People pass along what works, through a channel, a shared Project or skills.
  • You have a short list of what is working, what isn't, and what to fix next.

Analytics live under your initials (bottom left) > Analytics. Look after two weeks to see who is actually using it.

Perfect settings and a perfect policy matter less than all this. You can tighten controls later. It is much harder to win back a team that tried Claude once on the wrong task and gave up.

Further reading

Official training on this: Claude Enterprise Administrator Guide on Claude Academy, free.

Next in Setting up Claude for your company · Step 2 of 14

Continue to the next article in the learning path

Next article →

Weekly brief

For people actually using Claude at work.

Each week: one thing Claude can do in your work that most people haven't figured out yet — plus the failure modes to avoid. No tutorials. No hype.

No spam. Unsubscribe anytime.

What to read next

All articles →