Platform notes · Claude
Setting up Claude for a business team.
Claude suits teams that work from substantial reference documents and want each person’s working chats to stay private while sharing the same project knowledge. Here is what is specific to Claude — including one current limitation that shapes how we set it up. The setup is our standard AI Workspace Setup at $2,500 one-time.
01The plan
Team for most small companies; Enterprise for more controls.
Team
Anthropic’s Team plan needs at least two members and supports up to 150 seats, with project sharing, connectors and admin controls. Older pages call Team and Enterprise “Claude for Work”.
Enterprise
Adds controls such as audit logs, SCIM provisioning and custom data-retention settings. Its seat fee covers access, with usage billed separately at API rates — a different cost shape worth planning for.
Training on your data
Per Anthropic’s published policy, inputs and outputs from its commercial plans are not used for training by default. The exception is feedback a user chooses to submit, such as a thumbs up or down; owners can turn that rating option off.
02Projects
Project knowledge, instructions and private chats.
- Knowledge
- Documents uploaded to a project’s knowledge are used across every chat in that project. Each file can be up to 30 MB; the total has to fit Claude’s working context.
- Larger knowledge
- On paid plans, Claude switches automatically to searching the project’s documents when knowledge grows large. Clear, descriptive file names help — and we test that specific facts are actually found.
- Instructions
- Project instructions set tone, role and limits for every chat in the project.
- Sharing
- On Team and Enterprise, projects can be private (invited members only) or public to the organization, with “can view” and “can edit” roles. Members can see the project’s knowledge and instructions.
- Chats
- Even in a shared project, each person’s chats stay private unless they choose to share them — unlike a shared ChatGPT project.
What this means in practice: private chats make people comfortable experimenting, but the team learns less from each other by default. We agree how good examples get shared — usually by turning them into project instructions or a short usage guide.
03Connectors
Connections, and the limit that shapes the setup.
Admin first
Owners enable each connector
On Team and Enterprise, an Owner must enable a connector before anyone can use it, and each person still signs in individually. Owners can also limit what a connector may do across the organization.
Permissions
Inherited from the source
Claude inherits each person’s permissions in the connected service, so people only reach what they could already see. A connector set up with one shared credential is the exception to watch for.
Current limitation
Connectors live in private projects
Anthropic’s documentation states that connectors are only available in private projects, that the Google Drive option is disabled for shared projects, and that chats with synced content can’t be shared.
How we set it up: the team’s shared project uses a curated set of uploaded, approved documents with a named owner. Where live connections help, individuals use them in private projects. We re-check this before every engagement, because it may change.
04Realistic tasks
Where Claude setups tend to earn their keep.
- Answering from longer reference material. Procedures, service agreements and policies a team consults often, with answers that name the source.
- Careful drafting. Proposals, customer letters and summaries in your tone, reviewed before they are used.
- Searching across the organization. On Team and Enterprise, Anthropic’s enterprise search can query connected sources with each person’s permissions — once an owner has set it up.
What we check before promising a feature
- Your plan, seats and which owner controls connectors
- Whether the source you need is supported, and in which kind of project
- Project visibility (private or organization-wide) for each document set
- Whether the knowledge set is small enough to load whole, or will be searched
- Rating and retention settings your owner wants on or off
Checked against official documentation on . Vendors change plans and features often; we re-check before any engagement.
- Claude Help Center — What are projects?
- Claude Help Center — Manage project visibility and sharing
- Claude Help Center — Retrieval augmented generation (RAG) for projects
- Claude Help Center — Upload files to Claude
- Claude Help Center — What is the Team plan?
- Claude Help Center — What is the Enterprise plan?
- Claude Help Center — Use connectors to extend Claude’s capabilities
- Claude Help Center — Use Google Workspace connectors
- Claude Help Center — Use enterprise search
- Anthropic Privacy Center — Is my data used for model training?
Next step
Thinking about Claude for your team?
An Automation Assessment is a first conversation about fit: what your team does repeatedly, which tool you already use, and whether a workspace setup or a single workflow is the sensible first step. If neither fits, we will say so.