Claude for Your Team · Lesson 2 of 7

Settings that protect the business

25 minutes. For the owner. Walk through the settings that decide where your data goes, how long it stays, and what Claude can reach.

---

A Team plan starts with sensible defaults. But "sensible for most companies" isn't the same as "chosen by you." This lesson walks the settings page section by section, so every choice that matters is one you made on purpose and wrote down.

You'll need to be signed in as an Owner or the Primary Owner. Open your Team Setup Checklist to Part 2 and tick as you go.

What Anthropic says: by default, it doesn't use inputs or outputs from commercial plans, which include Team, to train its models.

There's one exception worth knowing. If someone on your team clicks the thumbs up or thumbs down on a reply and sends feedback, Anthropic says it may use that chat to train its models. Feedback is kept for up to five years (Anthropic says it's de-linked from user and customer IDs before training use).

Your choice: Go to Organization settings > Data and privacy and find the Rate chats setting. Turning it off removes the feedback buttons for everyone.

• If your team handles customer details, pricing or anything private in their chats, turn it off. It's the simplest way to make sure no chat leaves through a well-meant thumbs up.
• If you leave it on, tell the team in Lesson 3: never rate a chat that has customer or employee details in it.

If you're on an individual plan instead

On Free, Pro and Max, it's different. Anthropic trains on chats from those plans when the Help improve our AI models setting is on. Check it at claude.ai/settings/data-privacy-controls. With it on, Anthropic keeps that data for five years. With it off, the usual retention is 30 days. If you use an individual plan for any business work at all, turn it off today.

On a Team plan, chats stay in Claude until someone deletes them. When a person deletes a chat, Anthropic says it disappears from their history immediately and from its back-end storage within 30 days.

You can't set a custom retention period on Team. Custom retention controls are an Enterprise feature. So on Team, retention is a habit, not a setting:

• People can delete chats they no longer need.
• Incognito chats aren't saved to the person's chat history or to memory. On Team plans, Anthropic notes two things: incognito chats are still kept for 30 days for safety, and they're included in organization data exports. So incognito is a tidy-up tool, not a secret room. Tell your team that plainly.

Exports. Only the Primary Owner can export the organization's data, from Organization settings > Data and privacy. Do one test export now, so you know how it works before you need it.

Claude can remember context across chats. On Team plans, Anthropic says owners control whether memory is available, and it's off for each member until they turn it on.

You manage it in Organization settings > Capabilities.

Know this before you touch it: turning memory off for the whole organization permanently deletes all memory data for everyone. It's not a pause.

A sensible default for a small business: leave memory available, and let people turn it on for themselves. Projects (Lesson 4) also have their own separate memory, so work in one project doesn't leak into another.

Still in Organization settings > Capabilities, look at:

• Web search. An Owner must enable it here before anyone can use it. Most teams want this on. It's how Claude checks a current fact.
• Code execution and file creation. On Team plans, this is on by default, with network access limited to package managers only. Leave it on. Claude needs it to make files, and Anthropic says Docs, Slides and Design need it too.

Connectors let Claude read from (and sometimes write to) your other tools: email, calendars, shared drives, your CRM. They're useful. They're also the setting with the most reach, so this one deserves care.

Here's how it works on a Team plan, per Anthropic:

• Only Owners and the Primary Owner can add a connector for the organization, in Organization settings > Connectors.
• Each person then connects it with their own sign-in. Claude can only see what that person can already see in the other tool (unless the connector uses one shared key, so ask before adding one of those).
• Owners can disable connectors here too, including Google Workspace connectors, and can turn off specific interactive connector features.

Your rule: add only connectors from companies you already trust with that data, and only for a job you can name. "Read our shared drive so the office can find the warranty PDFs" is a job. "Connect everything" isn't. Anthropic's own advice is to connect only to servers built and hosted by organizations you trust.

If you use Microsoft 365, note that its connector needs a Microsoft Entra Global Administrator to approve it, and it's read-only unless you turn on more. That's a job for your IT partner. Lesson 5 covers using connectors day to day.

Two places control what leaves the building.

Projects. In Organization settings > Data and privacy, you'll find Share projects and, under it, Public projects. Both are on by default on Team. They only control sharing *inside* your organization. Leave them on; shared projects are the point of Lesson 4.

Artifacts (Docs, Slides, Design, Dashboards). In Organization settings > Artifacts, look at:

• External sharing: lets people share an artifact with anyone who has the link.
• Email invitations outside your organization: lets people invite named outsiders.

For most small businesses, turn External sharing off to start. A slide deck shared by public link can be forwarded anywhere. You can turn it back on later for a person or a reason you choose. If you want to keep emailing a proposal to one named customer as an option, leave email invitations on and cover it in Lesson 3.

In Organization settings > Organization and access:

• Verify your domain. In the Domains section, choose Add or edit domains, add your domain, click Verify, and add the TXT record it gives you at your domain provider. Anthropic says to allow about 10 minutes before you click Refresh.
• Restrict organization creation. Once your domain is verified, this toggle (under Security) stops people from creating new Claude organizations, including personal accounts, with your company email domain. This is the setting that backs up Lesson 3's rule. Turn it on.
• Single sign-on is available on Team, in the Authentication section, and optional. If you already sign in to everything with Microsoft or Google, ask your IT partner to set it up. It means when someone leaves and their company login is turned off, their Claude access goes with it.

On a Team plan, the domain setting blocks new personal accounts on your domain. It doesn't move existing ones. That's why Lesson 1 asked people to switch.

Work through sections 1 to 7 with the Team Setup Checklist open. For each setting, write what you chose, who changed it and the date.

Check it worked

• Rate chats is set on purpose, and you know which way.
• Memory, web search and file creation are set the way you want.
• Only connectors you can name a job for are added.
• External artifact sharing is set on purpose.
• Your domain is verified and Restrict organization creation is on.
• The Primary Owner has done one test data export.

---

Next: the team's turn. One rule, a few habits, and a card for every desk.

→ Lesson 3: Daily use: the company account rule

Previous: Pick the plan and set it up · Next: Daily use: the company account rule