AI at Work

10 things to set up in Claude Team on day one

On day one, name two Owners, verify your domain and set up single sign-on, invite people on the right seat type, switch on only the connectors you need, get Microsoft 365 approved by your IT provider and create shared projects for recurring work. Then check the skills, memory and sharing settings, set a monthly spend limit for extra usage and agree a one-page policy. Most of these are an hour's work and save weeks of tidying later.

1. Name your Owners

Every Team organisation has one Primary Owner, who can hand the role on to someone else. Owners manage billing, settings and connectors. Admins can add and manage members.

Name at least two Owners. Anthropic notes that an Owner cannot remove themselves from the organisation; another Owner has to do it, so a second Owner avoids getting stuck when someone leaves.

2. Verify your domain and set up single sign-on

An Owner verifies the company's email domain by adding a DNS TXT record, then connects single sign-on to your identity provider, such as Microsoft Entra ID. Verifying the domain does not affect anyone until SSO is enforced, so you can set it up before telling staff.

Once the domain is verified, you can stop new Claude organisations and personal accounts being created on it. On Team you cannot take over personal accounts that already exist on the domain; that is an Enterprise feature. Ask people with personal accounts to move their own work across.

3. Invite people on the right seat

Team runs from 2 to 150 seats. Standard seats suit most people; Premium seats carry much more usage and can be mixed in for heavy users. Invite from Organization settings, Members: enter an address on your company domain and choose the seat type and role.

Invitations expire after 21 days. By default, when a member invites a colleague, the request goes to an admin for approval.

4. Switch on only the connectors you need

An Owner decides which connectors the organisation offers, and each person still signs in with their own account. Set tool permissions to Always allow, Needs approval or Blocked; these apply to everyone and members cannot override them. Start with the document system you already use and leave the rest until someone has a real need.

What each connector widens is in Claude connectors and MCP explained.

5. Get Microsoft 365 approved

If you use Microsoft 365, the connector needs one approval from a Global Administrator in your tenant, usually your IT provider. It is read-only by default. Your IT provider can also limit it to a pilot group by setting Assignment required on the two enterprise applications.

Forward what your IT provider needs to do to connect Claude to Microsoft 365 to whoever looks after your tenant.

6. Create shared projects for recurring work

Pick two or three jobs that come round every week or month and give each a project with clear instructions and the reference documents it needs. A project can be open to everyone in the organisation or private to invited members with view or edit access. Chats inside it stay private unless the person shares them.

7. Decide how skills are shared

Skills are on by default for Team organisations. Owners can provision skills for everyone, and decide whether members can share skills with the organisation or with groups (both off by default) and publish them to the organisation's library, with review before publishing if you want it.

How a team builds its first skills is in Claude skills: a guide for business teams.

8. Check the data and privacy settings

  • Model training: Anthropic states that Team does not train models on your content by default.
  • Memory: Owners can turn memory off for the whole organisation under Organization settings, Capabilities. Members then cannot switch it back on for themselves.
  • Sharing: on Team, chats can only be shared with people in your organisation, not publicly.
  • Retention: custom data retention periods are an Enterprise feature. On Team, Anthropic says deleted conversations are removed from its back-end systems within 30 days.

9. Set usage and spend limits

Each seat has its own usage allowance, which cannot be shared between people. If you allow extra usage, Owners enable usage credits under Organization settings, Usage and set a monthly limit for the organisation.

Anthropic lists Team standard seats at US$25 a month on monthly billing or US$20 on annual billing, before tax, and the plan includes up to US$500 a month of pooled API credits.

What a typical Irish team pays on each plan is worked through in Claude pricing in Ireland.

10. Agree a one-page policy

  • Work goes on the business plan, never on personal accounts.
  • Which data may go into Claude, and which may not, such as special category personal data without approval.
  • What gets checked before anything Claude drafted leaves the business, and by whom.
  • Where finished work is saved: the document system, not the chat.
  • Who to ask about connectors, skills and new uses, and when the policy is next reviewed.

Common questions

How many people can be on Claude Team?

Between 2 and 150 seats. Larger organisations move to Enterprise.

Does Claude Team include single sign-on?

Yes. Anthropic lists SSO on Team. An Owner verifies the domain and connects your identity provider, and access only changes once SSO is enforced.

Can we set our own data retention period on Team?

No. Custom retention periods are an Enterprise feature. On Team, deleted conversations are removed from Anthropic's back-end systems within 30 days.

Can Team owners share skills with everyone?

Yes. Anthropic says Owners of Team and Enterprise organisations can provision skills for all users, and can control whether members share and publish their own.

For help putting this into practice, see Claude implementation and training for Irish businesses.

Sources and product references

Checked 16 November 2026. Features and access can change, so check what your own licence includes.

  1. Anthropic: Claude plans
  2. Anthropic: what is the Team plan?
  3. Anthropic: manage members on Team and Enterprise plans
  4. Anthropic: set up single sign-on
  5. Anthropic: claim and migrate accounts on your domain
  6. Anthropic: use connectors to extend Claude's capabilities
  7. Anthropic: set up the Microsoft 365 connector
  8. Anthropic: manage project visibility and sharing
  9. Anthropic: use skills in Claude
  10. Anthropic: chat search and memory
  11. Anthropic: share and unshare chats
  12. Anthropic: how long organisation data is stored
  13. Anthropic: custom data retention on Enterprise
  14. Anthropic: manage usage credits on Team plans

Editorial guidance informed by Acuity's work with teams. Examples are fictional and client materials stay private. To record who owns an AI use and when it is reviewed, see AI Register.