Claude Team Owner Guide

Claude Team Owner Guide

Overview

This guide is for people who own or administer a WSU Claude Team for a department, college, or lab. It assumes ITS approved your unit's request through the process in Getting Started with Anthropic Claude at WSU, and it follows the life of a Claude Team from creation through configuration, membership, billing, and offboarding.

A Claude Team is an organization inside Anthropic's Claude service that your unit pays for and manages. ITS runs the WSU access process (training and the WSU Information Stewardship Agreement and AI Services Access Request form), manages sign-in for WSU Claude accounts through WSU Okta single sign-on (SSO), and keeps a registry of Teams and their owners. Your unit administers its Team and billing using a departmental P-card, and ITS does not have visibility into Team content.

WSU does not require a particular Team setup. This page explains each option and its effects so you and your members know what to expect. Two requirements apply to every Team: Claude Team is approved for WSU Public and Internal data as defined in UPPM 87.53: Data Protection and Classification Policy; Confidential and Regulated data are not approved. and every member joins through the WSU request process before you invite them.

Roles in a Claude Team

Anthropic defines four roles on the Team plan. The table summarizes what each role can do and what that means for your unit. If this page and Anthropic's roles and permissions article differ, Anthropic's article takes precedence.

Table 1. Team plan roles, their permissions, and the practical consequences for a WSU unit.

Role

What the role can do

What that means for your unit

Primary Owner

Everything an Owner can do, plus request the organization data export and transfer Primary Ownership. Each Team has one Primary Owner, who occupies a seat.

The only person who can export the Team's data or transfer the Team to someone else. If this person leaves WSU without transferring the role, your unit will need to work with Anthropic Support to resolve ownership.

Owner

Invite and remove members, purchase and assign seats, change roles, view and pay invoices, add or change billing methods, enable integrations and connectors, and view usage analytics.

WSU asks for at least two Owners per Team so the Team always has an administrator if one Owner leaves.

Admin

Invite and remove members and cancel invitations. On Team plans, Admins cannot see billing, change roles, or view usage analytics.

Useful for an office manager or lab coordinator who handles day-to-day invitations without managing billing.

Member

Uses Claude, including chats, projects, and uploads, with no administrative permissions.

Every member's conversations belong to the Team, and the Primary Owner can export them. Let members know this when they join.

Owners and Primary Owners can both invite members and add seats. Anthropic's seat management article explains how to purchase and reassign seats.

Create Your Team

Wait to create the Team until ITS confirms in your request ticket that you can proceed. WSU manages the creation of new Claude organizations on WSU email addresses, and ITS enables creation for your unit once it approves your request. When ITS gives the go-ahead, have these ready:

  • Team Name: A name that starts with "WSU" and your unit's name, such as "WSU College of Veterinary Medicine" or "WSU Seed Lab," helps ITS and your members recognize it.

  • Starting Seat Count: The minimum is two, and you can add seats later.

  • Payment Card and Billing Email Address: Arrange the P-card through your unit's fiscal office. Review the Billing section below before you decide on either.

    • Note: Personal payment with reimbursement is not permitted.

Then:

  1. Sign in to Claude with your WSU email address. Follow the onboarding prompts and select the Team plan. Anthropic's Team plan article shows the process.

  2. Enter the Team name, choose monthly or annual billing, set the seat count, and provide the P-card and billing email. You become the Primary Owner.

  3. Invite your second Owner from Organization settings > Members, then set their role to Owner using the Role dropdown.

  4. Review the settings in the next section while the Team is still empty. Defaults are easier to change before members arrive.

  5. Reply in your ITS ticket with the final Team name and both Owners' email addresses so ITS can record the Team in the WSU registry.

Settings to Review

The table below lists the organization-level settings an Owner controls on a Team plan, along with each setting's default and what it means. WSU does not require any of these settings. Anthropic's What is the Team plan? article and the linked articles below provide current details.

Table 2. Organization-level settings on the Team plan: where to find each, its default, and what to consider.

Setting

Where

Default, what it does, and what to consider

Rate chats (feedback)

Organization settings > Data and Privacy

Controls whether members can give thumbs-up or thumbs-down feedback on responses. When a member rates a conversation, Anthropic may use that conversation to improve its models and keeps it for up to five years. This is the one way Team content can reach Anthropic's training. Owners and Primary Owners can turn it off for the whole Team.

Cowork

Organization settings > Cowork

Default: on. Cowork lets members use Claude with files and folders on their own computers through the desktop app. The same WSU data rule applies to any folder a member selects. Owners can turn Cowork off for the whole Team. A related setting, Allow "Always allow" for connector tools, is off by default and controls whether members can skip per-task approval for tools that write to connected services.

Claude Science

Organization settings > Claude Science

Default: off, except on Anthropic's Claude Team plan for scientists, where it is on. That plan is discounted pricing for research groups. Claude Science itself is a separate desktop app for scientific research, in beta for macOS, Windows, and Linux, and any Team can turn it on. It writes and runs code on the member's computer, reads folders the member selects, queries scientific databases, and can send jobs to a computing cluster or to Modal. Only an Owner or Primary Owner can turn it on, and every member then gets access. Before you turn it on, note three differences from regular Claude:

  • Claude Science work is stored on each member's computer, not in the Team, so it is not in the organization data export and stays with the member when they leave.

  • Modal bills the member's own account with no spend limit in Claude Science, and WSU does not permit personal payment.

  • Usage counts against the same allowance as Claude Code and Cowork.

Custom connectors and Modal are on by default within Claude Science's own controls, so review them when you turn it on. The WSU data rule applies to every folder, cluster, and connector a member uses with it. See Get started with Claude Science and Claude Science admin controls.

Connectors

Organization settings > Connectors

Default: none enabled. Members cannot connect an outside service (Google Drive, Microsoft 365, Slack, GitHub, and others) until an Owner enables that connector for the Team. Microsoft 365 also requires consent from a WSU Microsoft Entra Global Administrator, so a unit cannot enable it independently. WSU has not approved any connector for use with university data. If you enable one, the Public and Internal data rule applies to everything the connector can reach.

Usage credits and spend limits

Organization settings > Usage

Each seat includes a weekly usage allowance that resets on a set day. Usage credits let members continue working past their allowance, billed at Anthropic's API rates against credits you pre-purchase with the Team's card. Auto-reload can top up the balance up automatically. Owners can set an organization-wide monthly limit and per-member limits; when a member reaches a limit, their credit use pauses until the next month. If you enable credits, set these limits thoughtfully. If you do not purchase credits, members can resume once their allowance resets.

Usage analytics

User Profile Menu > Analytics

Owners and Primary Owners can see aggregate activity, such as weekly active members, adoption, and connector use, and export a spend report as a CSV file. Analytics show activity, not conversation content.

Organization data export

Organization settings > Data and privacy > Export Data

Primary Owner only. Produces the Team's conversation data and user data. A download link arrives by email and expires after 24 hours. The export does not include deleted messages, files, or projects.

Sources: Find and join a Team or Enterprise organization; Manage members on Team and Enterprise plans; Manage user feedback settings; Use Claude Cowork on Team and Enterprise plans; Microsoft 365 connector security guide; Manage usage credits; View usage analytics; Export your organization's data.

Membership

Inviting Members

Every member joins through the WSU request process. When someone submits the request form naming your Team, ITS adds you to their ticket, verifies their training and Information Stewardship Agreement, and tells you in the ticket when to invite them. Send an invitation only after ITS confirms the person in the ticket. If someone asks you for a seat directly, refer them to Getting Started with Anthropic Claude at WSU.

To invite a member, go to Organization settings > Members, enter the person's WSU email address, choose the seat type (Standard or Premium) and role, and click Add members. The invitation expires after 21 days. Anthropic prorates seats added mid-cycle and charges them to your card immediately. Members must use their WSU email address, since WSU Okta SSO manages sign-in for WSU Claude accounts.

Students and other affiliates can become members if your unit sponsors them, and they follow the same request process. Assign the Admin role to whoever will handle day-to-day invitations, and please keep at least two Owners at all times.

Bringing Someone Over from WSU Claude

Some people already use WSU Claude, the ITS-managed catch-all Team for users whose unit does not yet have its own, while they wait for a departmental Team. Invite them the same way. Anything they created in WSU Claude stays with that Team, so ask them to save what they need before they move to their departmental Team. Once they confirm they are working in your Team, let ITS know in a ticket so ITS can release their WSU Claude seat.

Keeping the Roster Current

Review your member list on a schedule that fits your unit, such as each semester or quarter. Remove people who have left the unit; their access ends immediately and the seat becomes available for someone else. If you add the same email address again later, Anthropic restores that person's account history.

Billing

Seats and Prices

Standard seats cost $25 per member per month billed monthly or $20 per member per month billed annually. Premium seats, which include higher usage limits, cost $125 monthly or $100 annually. You can mix seat types and reassign a member between Standard and Premium within the seats you own. Teams require a minimum of two seats and allow up to 150. Current figures are in What is the Claude Team plan? and Purchase and manage seats on Team plans.

Paying Anthropic

Arrange payment through your unit's fiscal office for the P-card. Anthropic accepts credit, debit, and prepaid cards only, not ACH payments or invoicing. WSU does not permit personal payment with reimbursement. Anthropic charges applicable sales tax; direct tax questions to your fiscal office.

Anthropic emails receipts to the account's billing address with the subject "Your receipt from Anthropic," and Owners can download invoices from Organization settings > Billing. Changing the billing email later requires Owner authorization and a request to Anthropic Support, so decide at creation whether to use a personal inbox or a shared unit mailbox.

How the Cycle Works

Anthropic charges at the start of each billing cycle for the seats you hold, and it prorates seats added mid-cycle and charges them immediately. Removing a member frees the seat but does not refund it. To lower the bill, reduce the total seat count; the reduction takes effect at your next renewal. For details, see Team plan billing FAQs and How is my Team plan bill calculated?

Annual or Monthly

Annual billing costs less per seat and commits your unit for the year, with seat reductions taking effect at the annual renewal. Monthly billing costs more per seat and lets you adjust your seat count at each monthly renewal, which suits a roster that is still changing. You can switch from monthly to annual at any time from Organization settings > Billing. The annual plan starts immediately, and Anthropic credits the unused part of the monthly period (Change your Team plan from monthly to annual billing). Your unit decides which option fits best.

Usage Credits

Usage credits are optional and are the only way a Team's cost can exceed its seat price. If your unit enables them, set an organization-wide monthly limit and per-member limits deliberately, decide whether auto-reload is appropriate, and check the spend report in Analytics. See Anthropic's Manage usage credits article.

Offboarding and Changes

When a Member Leaves Your Unit

Remove them from Organization settings > Members. Their access ends immediately, the seat becomes available for reassignment, and their conversations and projects remain with the Team. If they are moving to another WSU Team, give them time to save anything they need first, since their access to Team content ends as soon as you remove them.

When an Owner Leaves

Make sure at least two Owners remain on the Team. If the departing Owner is the Primary Owner, they must transfer the role before their last day. To transfer it, go to Organization settings > Members, open the Role dropdown next to the new Primary Owner, select Primary Owner, and confirm using the email Anthropic sends to the new Primary Owner. Each Team can have only one Primary Owner. If a Primary Owner leaves without transferring the role, the Team keeps running on the card on file, but no one in your unit can export its data or reassign ownership until Anthropic Support resolves the issue. Report Owner changes and Team renames to ITS through the AI section of the Crimson Service Desk portal so the WSU registry stays accurate.

Closing a Team

Before closing a Team, arrange a new Team for any members who still need Claude, either another WSU Team or, temporarily, WSU Claude, through an ITS ticket. An Owner or Primary Owner can then cancel from Organization settings > Billing. Access continues through the end of the current billing cycle, and after cancellation you can no longer remove members yourself (Cancel your organization's Team plan subscription). Let ITS know in the same ticket so ITS can retire the Team from the registry.

Know the Limits

Getting Started with Anthropic Claude at WSU lists Anthropic's commitments for Claude Team. Owners should also understand what the plan does not provide, since these limitations explain why Confidential and Regulated data stay out of Claude Team, and members often ask about them.

  • No Business Associate Agreement (BAA) on the Team plan. Anthropic offers a BAA only for Claude Enterprise and its first-party API, so protected health information is not permitted in a Team under any setting (Business Associate Agreements for Commercial Customers).

  • The Data Processing Addendum is Anthropic's standard click-through document, incorporated by reference in the Commercial Terms of Service, not an agreement WSU negotiated. Nothing in it authorizes FERPA-covered education records; that determination is WSU's, and WSU has not made it for Claude.

  • Rated conversations can be used for training. With Rate chats on, Anthropic may use a conversation a member rates to improve its models and keeps it for up to five years (Is my data used for model training?). This is the only such path, and Owners control the setting.

  • Anthropic's retention schedule. Anthropic removes deleted chats from its systems within 30 days, but it keeps content flagged for a usage policy review for up to two years and the related safety scores for up to seven years. Custom retention windows are available only on Enterprise plans (How long do you store my organization's data?; custom data retention controls for Enterprise).

  • The Primary Owner can see everything. The organization export includes every member's conversations and uploads (Who owns and manages the data of my team?). Share this with members when they join; Getting Started with Anthropic Claude at WSU also notes it.

  • Shared or departmental mailboxes. A Claude account on a shared WSU mailbox, such as a lab or office address, is not compatible with WSU Okta SSO and will no longer be accessible after enforcement, even with Team membership. ITS is contacting these account holders directly. If you hold one on of these accounts and have not heard from ITS, open a request in the AI section of the Crimson Service Desk portal.

Where to Get Help

  • Security concerns: If you or a member has a security concern about Claude, including information entered that should not have been, contact the Office of Information Security and Assurance (OISA) its.oisa@wsu.edu and describe it as a security report. WSU's Information Security team will advise on next steps.

  • WSU process: For member clearance, registry updates, sign-in issues related to WSU Okta SSO, and questions about this guide, use the AI section of the Crimson Service Desk portal or contact Crimson Service Desk.

  • Anthropic product and billing: For feature questions, outages, invoice problems, and questions about how Claude works, visit the Anthropic Help Center. Never include passwords or Confidential data in a support request to either WSU or Anthropic.

Related Pages