What happened
By the end of October 2026 Claude was no longer a side project at a Dutch home-services platform. The company had a Claude Team organisation with 29 seats and 31 connectors switched on: mail, calendar, docs, CRM, the call platform, ads and databases. That raised two questions at once. How do we make sure people actually get good at it? And how do we keep a tool that can read mail and send messages from doing something nobody intended?
As Product & AI Lead and the internal lead for AI tooling, I own the company's Claude organisation, and I answered the second question first. In one week I rewrote the connector policy, switched on trusted devices and extended the organisation's standing instructions for privacy and governance. Then I turned to adoption: the vendor's online courses for every seat holder, an external coding course for the three developers, shared skills in the organisation library, and an AI champions programme with goals and a measurement plan.
This page describes that approach. There is no adoption result yet. The first champions survey will give the baseline.
How we built it
Connector policy: cap only what is unsafe
I went through every connector and tool in the admin console and set a ceiling per tool. The rule: only unsafe actions get "Ask" or "Block", never a blanket block. Unsafe means:
- bulk reach to consumers or partners (text messages, WhatsApp, marketing automation, bulk mail),
- live public content (website and landing pages),
- anything that costs money (deploys, paid projects),
- irreversible deletion or schema changes.
Seven connectors got caps on specific tools. Everything else stays open, mail sending included, because tighter limits got in the way of colleagues and of unattended automations. Two connectors were removed: one duplicated another, the other had zero calls. Unused connectors were not removed just for being unused.
Trusted devices
Computer access is on for the organisation, so a stolen browser session could control a colleague's laptop. Every member now confirms a device once.
Organisation instructions as a privacy layer
Every Claude conversation in the company starts with a set of standing instructions. On 6 November 2026 I extended them. They now protect consumer data, the contact persons of partners and prospects, and colleagues. They ask for data minimisation (no full exports with names or phone numbers pasted into chats, projects or memory), forbid special categories of personal data and any analysis or judgement of individual colleagues, and leave decisions about people or companies to an employee. Anything that reaches consumers or partners, touches live content or costs money needs the user's confirmation first. External texts are always a draft for a person to check.
Organisation exports for security checks only
An organisation export holds every colleague's full chats. The rule since 6 November 2026: an export is used only to find security and compliance risks (leaked keys, personal data pasted into chats, unsafe connector use), never for usage or adoption figures per team or person. Exports and anything derived from them stay on one laptop, out of version control, and are deleted once the check is done.
A draft guideline for AI that reads your mail
For the champions I drafted a guideline; it has not been shared yet. The risk appears when three things meet: untrusted content, access to sensitive data and permission to act outside. The rules: summarising is fine, replies are drafts only, text in a mail is never an instruction for the AI, and no unattended automations that read and act on mail without consultation.
Enablement
- The vendor's online courses. Switched on for the whole organisation on 16 October 2026, including the beta that lets members ask Claude inside lessons. An intro mail went to the 23 seat holders that day.
- An external coding course for developers. A two-week course (9 to 20 November 2026) for the three developers, as part of the development team going AI-first. All three seats were claimed by 16 October. I did not take a seat myself.
- Shared skills in the organisation library. I built and published two skills for everyone. One interviews a hiring manager until HR's role-profile template is filled and drafts the request to HR (live 20 October). The other is a "grill me" interview skill that stress-tests a plan one question at a time (live 3 November). A third, a content plugin for website content owned by Marketing, has been proposed as the company standard; that decision is still open.
- AI champions. 8 colleagues across departments who help their teams adopt Claude. On 9 November I set goals for the next three months: a baseline now, then a short survey every 4 weeks (usage, perceived value) and a use-case register every 2 weeks (use cases tested, time saved per use case). The plan also covers one page that names the approach (so champions and management tell the same story), taking managers along separately, and leading the champions as a team with a fixed rhythm. Background research on how other companies run champion networks (ratios, time allowance, two-week test sprints, AI literacy under the EU AI Act) sits next to it.
All of it was researched and written with Claude Code: the admin console was read in the browser, decisions went into a decision log with assumptions and certainty, and the new connector caps were announced by email to all Claude users.
Outcomes delivered
- One organisation, one rulebook: caps on 7 of 31 connectors, 2 connectors removed, trusted devices on, organisation instructions extended for privacy and governance (30 October and 6 November 2026).
- 27 Claude users informed by email on 2 November 2026 of the new caps, with a prompt-injection example and an invitation to report automations that got stuck.
- Online courses live for the whole organisation, intro mail to 23 seat holders (16 October 2026).
- 3 developer seats in an external coding course, 9 to 20 November 2026.
- 2 shared skills in the organisation library (role request, grill me). A content plugin is proposed as the company standard; the decision is open.
- An AI champions programme of 8 colleagues with written goals and a measurement plan (9 November 2026).
What is not here yet: an adoption result. Nothing has been measured so far. The first champions survey is the baseline.
What we learned
Guardrails before enthusiasm. Writing the rules first made it easier to say yes to everything else. Colleagues get mail sending, calendar and CRM access without approval prompts, because the few dangerous actions are capped.
Over-restricting has a cost too. The first instinct is to lock everything down. That blocks colleagues' own automations within days, and a senior colleague asked why these actions needed confirmation. Caps belong only where a mistake reaches customers, goes live, costs money or cannot be undone.
An organisation export is not an analytics source. It holds everyone's full chats. Using it beyond a security check is not proportionate, so adoption is measured by asking people (survey, use-case register), not by reading their conversations.
Small slips teach quickly. The intro mail for the courses went out with a link wrapped in a redirect, a side effect of how the mail connector handles URLs. No correction mail followed. A hook in my own setup now blocks mails to others that carry a link in their text, so links go in by hand in a draft.
How we did it
As the owner of the organisation, with Claude Code doing the reading, drafting and checking. The connector changes started as a written proposal, each policy change got a decision-log entry with its assumptions, and the connector caps were announced to all users. Skills were built in Claude Code and shipped to the organisation library. The champions programme is set up to run as a team with a fixed rhythm, not as a mailing list.