If you’re here, you’re leading or assisting with the rollout of Claude Enterprise at your company. This course is written for that person: the admin, specifically the Owner, since the five decisions ahead are organization-wide settings that take Owner-level access. Every “you” in these lessons assumes you are in that seat. This course walks you through the five decisions that form the foundation of every company’s Claude rollout. The aim is to assemble the rollout plan as you go along.
Rolling out Claude Enterprise across your company is much more than just putting a tool behind single sign-on. Done well, this rollout can transform how your teams work, and the decisions in this course will help you do so according to your company’s unique objectives.
One note on scope: this course focuses on judgment, not mechanics. For step-by-step setup, each lesson links out to help center articles.
The five decisions
Every enterprise rollout answers the same five questions:
- Structure & Identity (Lessons 4 and 5): How many organizations do you run, and which groups live inside them? Every other control scopes to the groups you define here.
- Access (Lessons 6 and 7): Which surfaces (the places members use Claude) and connectors does each group get? That reach depends on the groups existing.
- Governance (Lesson 8): Who can build and share customizations, and how freely? The answer depends on what access already reaches.
- Spend (Lessons 9 and 10): Where do caps sit, and who owns the escalation? Caps attach to groups and get tuned once usage appears.
- Visibility (Lessons 11 and 12): What can you measure, and how long is data kept? Visibility is how you measure the outcomes of the other four decisions.
These decisions should be made in this order because each decision scopes the ones after it.
Four settings that are hard to undo
Four settings require a bit of extra care to help your rollout go smoothly:
- Domain claiming (Lesson 3): this setting brings the personal accounts on your email domain into your organization; once on, it can’t be reversed.
- Organization topology (how many organizations you run) (Lesson 4): merging or splitting organizations later means re-provisioning every affected member.
- Group structure (Lesson 5): most of your controls attach to groups; changing a live IdP-group-to-role mapping shifts access for every member it covers.
- Data retention (Lesson 11): you can change the retention period whenever you like, but conversations already deleted under a shorter window are gone for good.
The interactive widget below maps the five decisions and flags where these four settings live. You’ll review this map in Lesson 13, once all five decisions are made, to see what changing any one of them sets off.
The frame you will use for every decision
Every lesson that sets a configuration decision (Lessons 4 to 11) follows the same three steps, under the same three headings, in this order:
1 · Your decision: what you are deciding, stated in a sentence or two.
2 · The choices you can make: the options in front of you, laid out plainly, and what points you toward one over another.
3 · If you change this later: what to consider before you reverse the decision, for you as the admin and for your members. Every decision carries this slot; where a change is cheap, it says so in a sentence.
Your rollout objective
Instead of starting with settings, the first move is to determine what your company is truly trying to achieve with Claude Enterprise. For many companies the answer is broad transformation: a new way of working, everywhere. For others the mandate is narrower, such as enablement for a specific team, a specific workflow, or a commitment leadership has already made. Whatever the answer, the same five decisions apply. Your objective shapes how you make them.
A useful rollout objective has two halves. The first half is what success looks like. The second is any constraints that are particular to your company or its teams. Whatever the size of your company, you should identify a single company-wide ambition. Be specific — what does it look like and how will you communicate this vision to your employees? Unit-level nuance enters later, through rollout phasing and the audiences you measure for, not through per-unit goals. You’ll start the course with this objective, and then add to it as you get more insights.
Pluto: the example you will follow
Pluto is a fictional example company that will run throughout the course as a way to illustrate the types of decisions you’ll need to make as you deploy Claude Enterprise. Pluto runs five business units: Retail, B2B, Payments & Trust, Platform, and Ops. Payments & Trust operates under financial regulation. It has both ordinary teams and a regulated one, so you can see how those constraints inform decision-making.
Pluto’s rollout objective is for every one of Pluto’s five business units to use Claude in its daily work by the end of the quarter, measured as weekly active usage in each unit, without a single security escalation from Payments & Trust. The first half is the company-wide ambition, specific and tangible. The second is the constraint that must hold. When a choice would get Pluto to broad adoption faster but risks that escalation, Pluto takes the slower path. In every decision-focused lesson, you will learn the concept, see how Pluto applied it, and then apply it to your own company in the activity.
Your companion
The work-along companion is the document you fill in as you work through this course. It is a rollout plan with one section per lesson, grouped under the same five decisions: each lesson ends with you recording either your decision or the context you will take to its owner. It is a record you can walk your stakeholders through at kickoff, and the one you come back to as the rollout moves. Download the work-along companion now and fill it in as you go.
Lesson activity
Determine your company’s rollout objective now, including the company-wide ambition you’re after and the constraint that must hold on the way there. You’ll enter it in the intake questionnaire in the next lesson, and hold every one of the five decisions against it.
→ Record this in the work-along companion, section Lesson 1.
Downloads
What’s next
Before you make any of the five decisions, you need to know who owns each one. In the next lesson, you’ll name an owner for every decision, and run the intake questionnaire that surfaces the calls you will bring to a stakeholder.