What are the rules for?
Two decisions come first. The settings and the rules page follow from them.
This matches how the admin settings work. On Team and Enterprise only an Owner can switch a connector on for the company, so your rule says who asks and who answers.
An Owner still has to switch each connector on once before anyone can use it. Your rule then works as "the Owners switch on a short list, and people connect what they need from it".
Think of what would hurt if it leaked or got changed by mistake. Then add what to do if one of them ends up in a chat.
Who can change what?
Guess first. Step 2 shows where to check it.
Show the answer
Owners and the Primary Owner only. Admins can invite and remove members, but they can't enable integrations or change project sharing. A regular member can ask: on Team, every connector page has a Request button, and the request goes to an Owner.
Check it in Anthropic's roles table: Roles and permissions, under Features and integrations.
Set the controls, then write the rules
Five steps. Tick each one when you've checked it, even if you left the setting as it was.
Steps 1 to 3 happen in Organization settings, the admin pages of a Team or Enterprise plan. Open them in your browser at claude.ai/admin-settings/organization. On a personal plan (Free, Pro, Max or Ultra) there are none, so tick steps 1 to 3 and go to step 4.
-
Check who owns the setup.
Open Settings › Account to see who the Primary Owner is, then Organization settings › Members to see everyone's role. Keep the Owner list short, because Owners can change every setting below.
-
Switch on only the connectors you decided on.
Open Organization settings › Connectors, click Browse connectors and choose Add to your team for each one on your list. Leave the others alone: a connector stays off for the team until an Owner adds it.
Members' requests for other connectors reach an Owner on the Requests tab in Organization settings › Notifications. Requesting is on by default on Team and off on Enterprise.
-
Check who can publish Skills and share Projects.
A Skill is a saved routine, like the one you built in lesson 5. In Organization settings › Plugins & skills, open the Policy tab and find Publishing. Open puts a Skill any member publishes into the company library without review. Requires review means an Owner approves each one first. Team usually starts on Open.
In Organization settings › Data and privacy, under Sharing, Share projects is on by default. Turn it off if Projects should stay private. Projects that are already shared stay shared.
-
Fill in the rules page.
Who owns Claude: Who switches on connectors: Claude must not touch: Where to ask for help: We review these rules:
See a filled-in example
Who owns Claude: Dana in IT, who sends these rules to every new hire on day one
Who switches on connectors: Only IT
Claude must not touch: staff pay and HR files, customer card numbers, passwords. If one ends up in a chat, delete the chat and tell Dana.
Where to ask for help: #claude-help in chat. Ask there before you connect any tool that isn't on the list.
We review these rules: first Monday of every quarter
Team Owners can see usage under Analytics: click your initials in the lower left corner. Use it at your review date.
-
Send the rules to the team.
Paste the copied text into an email or your team chat, and give it to every new hire on day one. Tick this when it has gone out.
If you see this instead
- You can't find Organization settings
- You're on a personal plan (Free, Pro, Max or Ultra), or your role is User. Most of these settings need an Owner or Primary Owner. Settings › Account shows who the Primary Owner is: ask them to change your role under Members.
- A colleague says a connector is missing
- No Owner has added it yet. They can click Request on its page in the connector directory. On Enterprise, requests stay hidden until an Owner turns on "Let members request connectors".
- A connector is on, but Claude can't reach someone's files
- Switching it on doesn't sign anyone in. Each person has to connect it with their own account, and Claude then sees only what that account can open.
Do your rules answer real cases?
Give Claude your rules and three real cases, and see which ones the rules settle.
Test your rules on three cases
Open a new chat in Claude. Paste the rules you copied in step 4 where it says [your rules], and send this:
Here are my company's rules for using Claude: [your rules] Three cases: 1. An employee wants to connect their personal Dropbox. 2. Someone pastes a spreadsheet of staff salaries into a chat. 3. A new hire starts on Monday. For each case, quote the line of the rules that decides it and say what the person should do. If the rules don't cover a case, say so instead of guessing.
You pass when you can find each line Claude quoted, word for word, on your own rules page, and the action it gives for each case is one you'd accept. A quote that isn't on your page fails that case, however good the answer sounds.
If it says a case isn't covered, add to your answers in step 4, copy the rules again and rerun.
What a clear set of rules says
Case 1: a personal Dropbox
A tool that isn't on the list goes through whoever handles new tools. If Dropbox is worth having, someone requests it and an Owner decides. A rule like "ask IT before you connect a tool that isn't on the list" settles this.
Case 2: salaries pasted into a chat
Your off-limits line should name pay and HR files and say what to do next: delete the chat and tell whoever owns Claude. On Team and Enterprise the chat isn't used for training by default. Deleting it removes it from your history at once and from Anthropic's storage within 30 days.
Case 3: a new hire
An Owner or Admin invites them. If staff sign in through your company's own login (called SSO), Claude can also be set to add them the first time they sign in. They connect their own accounts and get the rules page on day one. If your rules never mention new hires, add a line saying who sends it.
Two questions from memory
Who can switch on a connector for the whole company on a Team plan?
Owners and the Primary Owner. Admins can't. Members can send a request, and each person still signs in to the service themselves.
A connector is switched on for the whole company. Can Claude now reach everyone's files?
No. Switching it on doesn't sign anyone in. Each person connects it with their own account, and Claude then sees only what that account can open.
No setting enforces any of this, so each person has to follow the rules page on their own account.
Your plan, complete
What you've decided
- First task for Claude
- Who starts
- Training setting
- Profile
- First Project for
- Documents in it
- Project instructions
- Shared with the team
- File storage
- Folders Claude should use
- Storage connected
- Daily tools to connect
- Mail and calendar
- Routine turned into a Skill
- Skill
- Task handed to Cowork
- Cowork run
- Who switches on connectors
- What Claude must not touch
- Rules sent to the team