top of page

10 Claude Security Settings for SMBs to Finish in 30 Minutes, Before You Invite Your Team

2 days ago
10 min read

Before you invite anyone, spend 30 minutes in the Admin console aligning Claude Team's defaults with your company's standards. Many options are already switched on when you first open Claude Team: the "Automatically approve" mode, in which Claude proceeds without asking; Cowork running in the cloud; and the built-in browser. On Enterprise plans, some of these start switched off.

The 10 steps below are written for the person at a 20–150-person company who handles IT on top of another job. A checklist and a connector approval form are at the end of the article for reference.

Setting

Team default

Enterprise default

Recommended for security

Use Cowork

ON

ON

Only for departments that need it

Run Cowork in the cloud

ON

OFF

ON only when needed

Built-in browser (Cowork)

ON

Not confirmed in the docs

Only for departments that need it

Start new tasks in "Automatically approve" mode

ON

OFF

OFF

Allow "Always allow" for connector tools

OFF

OFF

Keep OFF

Sources: Claude Help Center – Use Claude Cowork on Team and Enterprise plans, Get started with Claude Cowork (checked November 2026). Claude's settings change often, so check the actual Admin console once more before applying.


What to Prepare Before You Start

You need three permissions.

  • Owner or Primary Owner role in your Claude organization

  • DNS admin rights for your company domain (to add a TXT record for domain verification)

  • Google Workspace or Microsoft Entra admin rights (for SSO and connector consent)

Grant read access broadly, but have a person approve writes such as sending email or editing files. Start with a small scope for what Claude does on its own, then widen it. How to find AI tools that employees use without permission is covered in our earlier article, 8 Shadow AI Checks. This article is about how to configure the Claude your company has adopted.


The 10 Settings, in Order

Apart from waiting for DNS to propagate, this takes about 30 minutes. The steps are grouped into five blocks, and the screenshots show the recommended values applied. The orange boxes mark what to change.

A. Who Gets In (accounts, domain, SSO)


1. Trim Owners to 2–4 named accounts (3 min) Open the Owner list under Organization settings > Members. Remove shared accounts such as it@ or admin@ from Owner and keep named individuals only. If you have just one Owner, no one can change settings while that person is on vacation.

Why it matters: Owners can change every setting in this article. Shared accounts have unclear accountability, and their passwords leak easily.


2. Verify your company domain (5 min + DNS propagation) Under Organization & access > Domains, click "Add or edit domain" and register the TXT record shown on screen in your DNS. If the status shows "Failed," click "Verify" again after DNS has propagated. If you have several mail domains, register all of them. One organization's domains must be tied to a single IdP.

Why it matters: Only a verified domain lets you turn on SSO and the organization-creation restriction. Claude also uses the domain to decide which accounts belong to your company.

Organization & access > Domains. Register with "Add or edit domain," and if the status is "Failed," click "Verify" again after DNS propagates.


3. Block personal organizations on your company domain (1 min) Turn on "Restrict organization creation" under Organization & access > Security. You can turn it on only after domain verification is complete. From then on, employees can no longer use their work email to create a personal Claude account or a separate organization. Personal accounts already created stay as they are. The claim/migrate feature for moving such accounts into the company organization is Enterprise-only, so on Team you have to ask employees to clean them up themselves.

Why it matters: Conversations in a personal account sit outside your admin settings, sharing policy and offboarding process. When an employee leaves, that work history leaves with them.

Restrict organization creation turned on
Organization & access > Security > Restrict organization creation: ON.

4. Connect SSO, then enforce it (10 min) Connect SSO to Google Workspace or Microsoft Entra. After two people finish a login test, turn on Require SSO for Claude. The moment you do, some employees may be locked out of their existing personal accounts, so announce it a day or two ahead. Anthropic's documentation recommends the same order.

Why it matters: When you deactivate a departed employee in the IdP, their Claude access is cut off too. Password policy and MFA are also managed in one place.


5. Make invitations approval-based (2 min) Set "New member approval" under Organization & access to "Admin approval required." People who join through the invite link on the same screen are approved automatically, so turn the link off if you don't use it. After connecting SSO, it is easier to manage by switching user provisioning to just-in-time (JIT) and letting in only the groups you assign the Claude app to in your IdP.

Why it matters: Every member costs a seat and can reach the connectors linked to the organization. Approval-based invites stop a contractor whose contract has ended, or a departed employee, from coming back through an old link.

New member approval setting
Organization & access > New member approval: Admin approval required.

B. What the AI Can Touch (connectors)


6. Use an allowlist for connectors (3 min) On Team, employees can use only the connectors added on the admin settings' "Connectors" screen. Start with just the two or three the work truly requires. Turn on "Allow members to request connectors" on the same screen only when someone is assigned to review requests. A connector uses the permissions of the employee who connected it. With the Google Drive connector, Claude can read every file that employee can open, including files shared with them years ago and forgotten. Before turning one on, check it against the toolkit's "3 questions before connecting."

Why it matters: Turning on one connector widens what Claude can read to that entire service. The more connectors without an owner, the less anyone knows who connected what.

Connector management screen
Connectors > Connector requests: OFF if there is no reviewer.

7. Require approval for write tools every time (1 min) Turn off Allow "Always allow" for connector tools under Capabilities > Tool approval. This used to be on the Cowork screen, but it has moved to "Capabilities." With it off, any tool that changes something, such as sending email or creating a file, asks for the employee's approval each time it runs. The screen's own description warns that turning this setting on raises prompt-injection risk. Since July 2026, you can also send email through the Microsoft 365 connector. Most custom connectors built in-house don't mark their tools as read-only, so even lookup-only tools ask for approval. Tell employees in advance so they don't mistake it for an error.

Why it matters: If "Always allow" is permitted, content arriving from a connected app can make Claude send email or change files with no one's approval.

Capabilities > Tool approval section
Capabilities > Tool approval. Turn "Start new tasks in Automatically approve mode," "Allow Skip all approvals mode," and "Allow 'Always allow' for connector tools" all OFF.

C. How Independently the AI Acts (agent permissions)


8. Turn off "Automatically approve" and "Skip all approvals" (2 min) Check three items in the same Capabilities > Tool approval section. "Start new tasks in 'Automatically approve' mode" is ON by default on Team. Turn it off and new tasks start in manual approval mode, where Claude checks with the employee before acting. To block auto mode entirely, also turn off "Allow 'Automatically approve' mode." "Allow 'Skip all approvals' mode" lets Claude edit files and browse websites without approval; the screen itself says it can put organization data at risk, so turn it off. Also look at "Enable Dispatch" on the Cowork screen. When it's on, Cowork runs in the background on the employee's PC and can reach that PC's files and apps without direct supervision.

Auto mode is vulnerable to prompt injection. Security firm PromptArmor published a demonstration in which a single instruction hidden in white text inside a document made Cowork send a user's files outside (HN discussion). For work involving documents or email received from outside, keep a step where a person checks once.

Why it matters: Automatically approve and Skip all approvals remove the human checkpoint. For work involving external documents or email, that checkpoint is the only thing that can stop Claude's actions.

Cowork admin settings screen
Cowork > Enable Dispatch: OFF if no employee needs it.

D. What the AI Clicks (browser and web)


9. Reduce browser and web access (3 min) On the admin settings' "Claude in Chrome" screen, turn off "Enable for team," or change "Default for all sites" from "Allow all sites" and open only the sites you need. Put banking, payroll and accounting sites in "Blocked sites." These site permissions also apply to the built-in browser in the desktop app. Anthropic also advises using a browser profile separate from the one used for work. Turning the built-in browser and web search on or off is under Capabilities > Data sources. Network egress settings do not apply to MCP, including web search, web fetch and Claude in Chrome, so configure each separately.

Why it matters: A browser agent uses the sessions employees are already logged into. One malicious page could let the agent perform actions on a logged-in bank or payroll site.

Claude in Chrome admin settings
Claude in Chrome. Change "Allow all sites," and use "Add website" to put banking, payroll and accounting sites on the blocklist.

Capabilities > Data sources: web search and built-in browser
Capabilities > Data sources. Turn on web search and the built-in browser only where needed.

E. Where Data Stays (sharing, visibility, offboarding)


10. Sharing settings, logs, offboarding (1 min + separate work) Start with the settings under Data & privacy > Sharing that let conversations leave the organization, such as "Share chats externally." Turn them off if you don't need them. If you already use a logging tool, put its OTLP endpoint under Monitoring on the same screen to connect Cowork OpenTelemetry. Anthropic notes, though, that OpenTelemetry is not a substitute for a compliance audit log. Finally, write the offboarding procedure down. Removing a user from the organization doesn't delete their account or data, and the connector OAuth tokens left at Google or Microsoft must be revoked separately.

Why it matters: Conversations often contain customer information and pricing. One external sharing link can send them straight out, and without logs you can't tell afterward what an agent did once an incident has occurred.

Data & privacy > Sharing
Data & privacy > Sharing > Share chats externally: OFF.

Data & privacy > Monitoring
Data & privacy > Monitoring. Enter an OTLP endpoint and Cowork events go to your logging tool.

The screenshots are of the English-language Claude Team Admin console, November 2026. Menu names and locations change often, so they may differ slightly from your Admin console. The recommendation on the number of Owners in step 1 comes from practical guides, not from Anthropic documentation.


4 Cases Where Team Isn't Enough

Decide whether to move to Enterprise by the features you need, not by seat count. If even one of the questions below applies, consider Enterprise.

Question

Required feature (Enterprise only)

Do your customers or auditors require a record of "who did what"?

Audit log, Compliance API

Do you need departed employees' accounts revoked automatically from your IdP?

SCIM

Do you need to stop employees from connecting company Gmail/M365 to a personal Claude account?

Restrict verified-domain connectors, claim of existing personal accounts

Do you need to set a data retention period, or need a HIPAA BAA?

Custom data retention, HIPAA-ready plan

Per-tool connector permissions based on IP allowlisting, Tenant Restrictions and custom roles are also available on Enterprise. Sources: Claude Help Center – Security and compliance, Restrict verified-domain connectors, Claim and migrate accounts.


After 30 Minutes: A 15-Minute Check Every Quarter

New features are sometimes added already switched on. In 2026 alone, Cowork cloud execution, email sending from the Microsoft 365 connector, and connector permission settings were all new. Set aside 15 minutes each quarter and check the following four things.

  1. Check the Claude Release notes for new settings and defaults.

  2. Compare the list of enabled connectors with their owners. Turn off any connector that has no owner.

  3. Compare the Owner list and member list with the HR roster.

  4. Update the "Date checked" column in the toolkit checklist.


Toolkit: Claude Team Security Starter Kit

You can copy and use the three items below as they are.


1) 30-Minute Setup Checklist

#

Item

Where to set it

Team default

Recommended

Done

Date checked

Owner

1

Clean up Owners

Members

—

2–4 named people, no shared accounts

 

 

 

2

Domain verification

Organization & access > Domains

Unverified

Verify all mail domains

 

 

 

3

Block personal organizations

Organization & access > Security > Restrict organization creation

OFF

ON

 

 

 

4

Enforce SSO

Organization & access > Authentication > Single sign-on

Not set

Enforce after testing and notice

 

 

 

5

Approval-based invites

Organization & access > New member approval / Invite link

Check on screen

Admin approval required, invite link OFF

 

 

 

6

Connector allowlist

Connectors

Only those the admin added

2–3 approved; request feature only if a reviewer exists

 

 

 

7

Approve write tools each time

Capabilities > Tool approval > Allow "Always allow" for connector tools

OFF

OFF

 

 

 

8

Auto-approve and skip-approvals

Capabilities > Tool approval / Cowork > Dispatch

Auto-approve start ON

Auto-approve start OFF, Skip all approvals OFF, Dispatch only when needed

 

 

 

9

Browser and web

Claude in Chrome / Capabilities > Data sources

Built-in browser ON

Chrome OFF or only needed sites

 

 

 

10

Sharing, logs, offboarding

Data & privacy > Sharing / Monitoring

—

Review external sharing, connect OTel, document offboarding

 

 

 

"—" means not applicable, and "Check on screen" marks items whose default we could not confirm in the official documentation.


2) Connector Approval Form: 3 Questions Before Connecting

Question

What to check

Pass criterion

1. Is it read-only, or does it write too?

The connector's tool list (search, read, send, create, delete)

The require-approval-every-time setting for write tools (step 7) is on

2. Have you narrowed what the connected account can see?

That employee's Drive/mailbox sharing scope

Material the AI will see is separated into a dedicated folder or Shared Drive

3. Does outside content get mixed in?

External email, shared documents, web pages

If so, use it only in manual approval mode

Approval record: connector name / requester / business purpose / owner / approval date / next review date

3) Connector Permissions Matrix (example)

Connector

Always allow

Approve each time

Block

Gmail / Outlook

Search, read

Draft, send

Delete, auto-forward

Google Drive / SharePoint

Search, read

Create, edit files

Delete, external sharing

Calendar

View events

Create, change events

Delete events

In-house custom connector

Only tools marked read-only

All other tools

Changing payment or HR data

On Team, this table is a company operating policy, not a setting. Enforcing permissions per tool in the system requires Enterprise custom roles.


Wrapping Up

TecAce is a Select partner in the Claude Partner Network. Drawing on our 24x365 cloud operations experience, we work with you on initial setup, connector design and quarterly reviews. If you need a settings review, contact CONTACT@TecAce.com.

Coming next: A Runbook for Revoking Claude Access from Departing Employees and Contractors


Sources

Verified: November 2026. Menu names and defaults may change.

Comments


bottom of page
AI Voice Agent
Talk to Our AI Voice Agent
Ask anything about AI transformation
CALL