One read of Claude Documentationclaude-docs-20261022T180711Z
268 pages moved out of 279 read.
Pages moved
268
significant first
Pages read
279
in this capture
Captured
18:07 UTC
Corpus hash
510ab6f6a194
corpus-hash
What this read moved
176-200 of 268, page 8 of 11This capture is too large to show at once. Changes 176-200 of 268 are below, significant first; the rest are on the following screens.
government/tenant-admin/readiness Changed · +5 / -5 lines
from line 27
2727
2828* **Activate the tenant** appears on its own when Anthropic has not yet finished provisioning your tenant, or when the tenant has been deactivated. Nothing else can be configured until this clears, and only Anthropic can clear it, so the page shows a waiting state.
2929* **Fund the billing account** checks that at least one billing account linked to an active organization has a positive balance. This is advisory because the blocking state is shown on each organization's own readiness check. Funding is arranged with Anthropic.
30* **Configure the seat pool** checks that at least one billing account has a seat pool set. This is also advisory. Until a pool is set, the [Seats](/docs/government/tenant-admin/seats) page has no seats on Anthropic-managed tiers for you to distribute. Organizations can still give their users seats on any [self-managed seat tiers](/docs/government/org-admin/seat-tiers) they create themselves. The pool is configured by Anthropic as part of your contract.
31* **Register a domain** is required. Claude for Government routes users to your tenant by the domain of their email address, so until at least one domain is registered nobody can start a new sign-in. Use **Open Identity and access** to go to the [Identity and access](/docs/government/tenant-admin/identity-and-access) page and add one.
32* **Set up SCIM provisioning** is optional. SCIM lets your directory push users and groups into Claude for Government automatically. If you plan to use it, generate a provisioning token on the [Identity and access](/docs/government/tenant-admin/identity-and-access) page.
33* **Add a routing rule** is required. Routing rules decide which organization each user joins when they sign in. Until at least one rule points at an active organization, every new sign-in is turned away. Use **Open Identity and access** to add a rule. If your tenant has no active organizations yet, the button instead opens the [Organizations](/docs/government/tenant-admin/organizations) page so you can create one first.
30* **Configure the seat pool** checks that at least one billing account has a seat pool set. This is also advisory. Until a pool is set, the [Seats](/docs/government/tenant-admin/seats.md) page has no seats on Anthropic-managed tiers for you to distribute. Organizations can still give their users seats on any [self-managed seat tiers](/docs/government/org-admin/seat-tiers.md) they create themselves. The pool is configured by Anthropic as part of your contract.
31* **Register a domain** is required. Claude for Government routes users to your tenant by the domain of their email address, so until at least one domain is registered nobody can start a new sign-in. Use **Open Identity and access** to go to the [Identity and access](/docs/government/tenant-admin/identity-and-access.md) page and add one.
32* **Set up SCIM provisioning** is optional. SCIM lets your directory push users and groups into Claude for Government automatically. If you plan to use it, generate a provisioning token on the [Identity and access](/docs/government/tenant-admin/identity-and-access.md) page.
33* **Add a routing rule** is required. Routing rules decide which organization each user joins when they sign in. Until at least one rule points at an active organization, every new sign-in is turned away. Use **Open Identity and access** to add a rule. If your tenant has no active organizations yet, the button instead opens the [Organizations](/docs/government/tenant-admin/organizations.md) page so you can create one first.
3434* **Review sign-in failures** is an optional summary of people who tried to sign in and were turned away. The description tells you how many need a routing rule, how many need their email domain registered, and how many conflict with an existing account. Use **Open Identity and access** to resolve them.
3535
3636If your tenant has a single organization, that organization's own checks (credits, spend caps, seats, seat tiers, and products) appear directly in this card below the tenant-level items, so you can work through the whole deployment from one list.
from line 39
3939
4040When your tenant has more than one organization, a second card lists each one with a one-line summary: **Ready**, a named blocker with **(fix available)**, or a named blocker with who it is waiting on. The marker beside each row uses the same colors as the checklist above.
4141
42Expanding a row loads that organization's full checklist inline. The steps are the same ones described on the [organization Readiness page](/docs/government/org-admin/readiness), and any buttons you click here act on that organization, not the one you are currently viewing in the organization admin portal. This lets you clear an organization's blockers without switching context.
42Expanding a row loads that organization's full checklist inline. The steps are the same ones described on the [organization Readiness page](/docs/government/org-admin/readiness.md), and any buttons you click here act on that organization, not the one you are currently viewing in the organization admin portal. This lets you clear an organization's blockers without switching context.
4343
4444Deactivated organizations appear here with their reactivation status. An organization whose billing account is retired cannot be reactivated until the account has settled and Anthropic has assigned a new one, so those rows show a waiting state instead of a button.
4545
government/tenant-admin/setup-wizard Changed · +11 / -9 lines
from line 18
1818
1919<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-02-verify-your-domain-and-connect-single-sign-on.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=bf307a4d18d646cbce35d3c269be51b7" aria-label="Video walkthrough: Verify your domain and connect single sign-on" />
2020
21Video: Verify your domain and connect single sign-on (2 min 24 s). Narrated with an AI-generated voice, with on-screen captions.
22
2123> **Transcript**
2224>
2325> Before your members can sign in, your tenant needs a verified email domain and a connection to your identity provider.
from line 52
5052
5153If Anthropic already verified the domain you plan to use, you can move straight on to the next step. To add another domain, type it into the **Claim a domain** field and click **Claim**. You will be shown a DNS TXT record to publish on that domain. Once the record is live, click **Verify now** next to the pending claim and the domain becomes active. DNS changes can take anywhere from a few minutes to an hour to propagate, so try again shortly if verification does not succeed on the first attempt.
5254
53For more detail on how domains work and how to remove one later, see the [Domains section of the Identity and access page](/docs/government/tenant-admin/identity-and-access#domains).
55For more detail on how domains work and how to remove one later, see the [Domains section of the Identity and access page](/docs/government/tenant-admin/identity-and-access.md#domains).
5456
5557## Step 3: Single sign-on
5658
from line 68
6668
6769After you save a SAML connection, an **SP metadata URL** appears with the other values; most providers can import it to fill in the values automatically if you need to reconfigure.
6870
69Until single sign-on is connected, only owners who were invited directly by email can sign in. The full field reference for both protocols is on the [Identity and access](/docs/government/tenant-admin/identity-and-access#single-sign-on) page.
71Until single sign-on is connected, only owners who were invited directly by email can sign in. The full field reference for both protocols is on the [Identity and access](/docs/government/tenant-admin/identity-and-access.md#single-sign-on) page.
7072
7173Once single sign-on is connected, people sign in from Claude Desktop or the web portal, and Claude for Government sends them to your provider from there. Starting from the application's tile in your provider's app portal, or from a sign-in test in its admin console, is not supported.
7274
from line 80
7880
7981Copy the **Tenant URL** shown on this step into your identity provider's SCIM connector, then click **Generate token** and paste the token into the connector's secret token field. The token is shown only once, so copy it before closing the page. If you need to rotate it later, generate a new one and revoke the old one with the **Revoke** button.
8082
81You do not have to finish the provider-side setup before moving on. Once your provider has pushed at least one group, you can come back to the Routing step (or the [Identity and access](/docs/government/tenant-admin/identity-and-access#scim-provisioning) page) and add rules that place people by group membership.
83You do not have to finish the provider-side setup before moving on. Once your provider has pushed at least one group, you can come back to the Routing step (or the [Identity and access](/docs/government/tenant-admin/identity-and-access.md#scim-provisioning) page) and add rules that place people by group membership.
8284
8385## Step 5: Organizations
8486
from line 92
9092* **Primary Owner email** is the person who will manage this organization's members and seats. They will be invited by email and land in the organization admin view when they sign in.
9193* **Billing account** is the account this organization draws from for seats and billed usage. Several organizations can share one account if they should be funded from a single budget.
9294
93Click **Add** and the new organization appears in the list. You can create as many as you need now and add more later from the [Organizations](/docs/government/tenant-admin/organizations) page.
95Click **Add** and the new organization appears in the list. You can create as many as you need now and add more later from the [Organizations](/docs/government/tenant-admin/organizations.md) page.
9496
9597## Step 6: Seats and spend caps
9698
9799This step lets you give each organization seats and, optionally, a spend cap.
98100
99Seats control how many people in each organization can use Claude. The table shows each organization with a seat-count field for the first seat tier. Enter the number of seats each organization should have and save. Saving an organization's first seats also seats its Primary Owner, and anyone else already in it who has no seat tier, automatically. For per-tier control, use the full [Seats](/docs/government/tenant-admin/seats) page after setup.
101Seats control how many people in each organization can use Claude. The table shows each organization with a seat-count field for the first seat tier. Enter the number of seats each organization should have and save. Saving an organization's first seats also seats its Primary Owner, and anyone else already in it who has no seat tier, automatically. For per-tier control, use the full [Seats](/docs/government/tenant-admin/seats.md) page after setup.
100102
101Each organization's usage spends directly from its billing account's balance, and you can add a spend cap to limit how much any one organization can use in a rolling window. Caps are optional. If you leave them blank, the billing account's balance is the only limit. You can adjust both seats and caps later from the tenant [Seats](/docs/government/tenant-admin/seats) and [Billing](/docs/government/tenant-admin/credits) pages.
103Each organization's usage spends directly from its billing account's balance, and you can add a spend cap to limit how much any one organization can use in a rolling window. Caps are optional. If you leave them blank, the billing account's balance is the only limit. You can adjust both seats and caps later from the tenant [Seats](/docs/government/tenant-admin/seats.md) and [Billing](/docs/government/tenant-admin/credits.md) pages.
102104
103105## Step 7: Routing
104106
from line 113
111113* In the **Then place in** field, pick the organization.
112114* Click **Add rule**.
113115
114Rules run from top to bottom and the first match wins, so move more specific rules above broader ones. Rules that match directory groups pushed over SCIM are managed on the full [Identity and access](/docs/government/tenant-admin/identity-and-access#routing-rules) page, which also has a preview tool for testing where a specific email address would land.
116Rules run from top to bottom and the first match wins, so move more specific rules above broader ones. Rules that match directory groups pushed over SCIM are managed on the full [Identity and access](/docs/government/tenant-admin/identity-and-access.md#routing-rules) page, which also has a preview tool for testing where a specific email address would land.
115117
116118## Steps 8 and 9: Seat tiers and Products (single-organization tenants only)
117119
118If your tenant has exactly one organization, the wizard includes two extra steps so that you can finish the organization-level setup without switching portals. You will only see these two steps in the step list if your tenant has a single organization. Tenants with more than one organization skip straight to the Finish step, and each organization's owner completes these two steps in their own [organization setup wizard](/docs/government/org-admin/setup-wizard) instead.
120If your tenant has exactly one organization, the wizard includes two extra steps so that you can finish the organization-level setup without switching portals. You will only see these two steps in the step list if your tenant has a single organization. Tenants with more than one organization skip straight to the Finish step, and each organization's owner completes these two steps in their own [organization setup wizard](/docs/government/org-admin/setup-wizard.md) instead.
119121
120* **Seat tiers** lists the seat tiers available to the organization. A seat tier bundles together which Claude models a user may access and how much they may spend. Anthropic-managed tiers are set up for you during provisioning; if your organization is allowed to create self-managed tiers, you can add one here. See the organization [Seat tiers](/docs/government/org-admin/seat-tiers) page for the full editor.
122* **Seat tiers** lists the seat tiers available to the organization. A seat tier bundles together which Claude models a user may access and how much they may spend. Anthropic-managed tiers are set up for you during provisioning; if your organization is allowed to create self-managed tiers, you can add one here. See the organization [Seat tiers](/docs/government/org-admin/seat-tiers.md) page for the full editor.
121123* **Products** lets you choose which Claude products the organization's members can sign in to, for example Claude Desktop, Claude Code, and Claude for Microsoft 365. This is optional, and a product that is not available on your deployment is shown grayed out with a note to contact Anthropic.
122124
123125## Final step: Finish
government/video-walkthroughs Changed · +31 / -11 lines
from line 2
22
33> Watch short narrated walkthroughs of setting up and running Claude for Government for your agency.
44
5> **Who this is for:** Tenant administrators, organization owners, and IT administrators who set up and run Claude for Government. If you use Claude Desktop but don't administer it, see [Video walkthroughs for Claude Desktop](/docs/government/desktop/video-walkthroughs) instead.
5> **Who this is for:** Tenant administrators, organization owners, and IT administrators who set up and run Claude for Government. If you use Claude Desktop but don't administer it, see [Video walkthroughs for Claude Desktop](/docs/government/desktop/video-walkthroughs.md) instead.
66
77Each video is one to three minutes long and narrated, with on-screen captions.
88
from line 12
1212
1313### Finding your way around
1414
15How a tenant, its organizations, and their users fit together, how administrators sign in to the web portal, and how to move between the admin, tenant, and account views. Read more: [The three views](/docs/government/overview#the-three-views).
15How a tenant, its organizations, and their users fit together, how administrators sign in to the web portal, and how to move between the admin, tenant, and account views. Read more: [The three views](/docs/government/overview.md#the-three-views).
1616
1717<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-01-finding-your-way-around.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=e815e7d6b488de1c9629bfaa2f1354ab" aria-label="Video walkthrough: Finding your way around" />
1818
19Video: Finding your way around (2 min 23 s). Narrated with an AI-generated voice, with on-screen captions.
20
1921> **Transcript**
2022>
2123> Your tenant is your agency's deployment and holds its organizations. Each user belongs to one, run by Owners and Primary Owners. Tenant administrators manage the tenant.
from line 56
5456
5557### Verify your domain and connect single sign-on
5658
57Claiming and verifying your agency's email domain, then connecting your identity provider with OIDC or SAML in the setup wizard. Read more: [Step 2: Domains](/docs/government/tenant-admin/setup-wizard#step-2-domains) and [Single sign-on](/docs/government/tenant-admin/identity-and-access#single-sign-on).
59Claiming and verifying your agency's email domain, then connecting your identity provider with OIDC or SAML in the setup wizard. Read more: [Step 2: Domains](/docs/government/tenant-admin/setup-wizard.md#step-2-domains) and [Single sign-on](/docs/government/tenant-admin/identity-and-access.md#single-sign-on).
5860
5961<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-02-verify-your-domain-and-connect-single-sign-on.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=bf307a4d18d646cbce35d3c269be51b7" aria-label="Video walkthrough: Verify your domain and connect single sign-on" />
6062
63Video: Verify your domain and connect single sign-on (2 min 24 s). Narrated with an AI-generated voice, with on-screen captions.
64
6165> **Transcript**
6266>
6367> Before your members can sign in, your tenant needs a verified email domain and a connection to your identity provider.
from line 92
8892
8993### Organizations, seats, and routing rules
9094
91Adding a sign-in routing rule that places new people in the right organization, adding an organization, and giving it seats. Read more: [Routing rules](/docs/government/tenant-admin/identity-and-access#routing-rules).
95Adding a sign-in routing rule that places new people in the right organization, adding an organization, and giving it seats. Read more: [Routing rules](/docs/government/tenant-admin/identity-and-access.md#routing-rules).
9296
9397<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-03-organizations-seats-and-routing-rules.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=3b4fdf17a38f17ace0a31daff24dd678" aria-label="Video walkthrough: Organizations, seats, and routing rules" />
9498
99Video: Organizations, seats, and routing rules (2 min 14 s). Narrated with an AI-generated voice, with on-screen captions.
100
95101> **Transcript**
96102>
97103> Routing rules decide which organization each person lands in. Organizations hold users, seats, and settings, and their seats come from a billing account.
from line 124
118124
119125### Directory sync (SCIM) and group mappings
120126
121Connecting SCIM provisioning, routing directory groups to organizations, and mapping groups to seat tiers and roles. Read more: [SCIM provisioning](/docs/government/tenant-admin/identity-and-access#scim-provisioning) and [Group mappings](/docs/government/org-admin/provisioning).
127Connecting SCIM provisioning, routing directory groups to organizations, and mapping groups to seat tiers and roles. Read more: [SCIM provisioning](/docs/government/tenant-admin/identity-and-access.md#scim-provisioning) and [Group mappings](/docs/government/org-admin/provisioning.md).
122128
123129<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-04-directory-sync-scim-and-group-mappings.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=e254e02786c5f309b5c5c240c7752c4e" aria-label="Video walkthrough: Directory sync (SCIM) and group mappings" />
124130
131Video: Directory sync (SCIM) and group mappings (2 min 3 s). Narrated with an AI-generated voice, with on-screen captions.
132
125133> **Transcript**
126134>
127135> Directory sync is optional, and without it accounts are created at first sign-in. With it, your identity provider pushes users and groups, provisioning rules place them in organizations, and each organization maps groups to seat tiers and roles.
from line 154
146154
147155### Users, seat tiers, and Readiness for organization owners
148156
149Checking the **Readiness** page, assigning seat tiers and roles on the **Users** page, and reviewing the **Tiers** page. Read more: [Organization administration](/docs/government/org-admin/overview).
157Checking the **Readiness** page, assigning seat tiers and roles on the **Users** page, and reviewing the **Tiers** page. Read more: [Organization administration](/docs/government/org-admin/overview.md).
150158
151159<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-05-organization-owners-users-seat-tiers-and-readiness.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=d235ae566a0056c409a1b59b2a9623e7" aria-label="Video walkthrough: Organization owners: users, seat tiers, and Readiness" />
152160
161Video: Organization owners: users, seat tiers, and Readiness (1 min 48 s). Narrated with an AI-generated voice, with on-screen captions.
162
153163> **Transcript**
154164>
155165> In an organization, a member's role decides what they can manage, and their seat tier decides which models they can use and how much. Readiness shows what still blocks your members.
from line 180
170180
171181### Config essentials
172182
173Editing settings on the **Config** page for an organization or for one directory group, turning on web search, reviewing the session idle timeout, and locking a value for every organization from the tenant. Read more: [How Config works](/docs/government/config/overview).
183Editing settings on the **Config** page for an organization or for one directory group, turning on web search, reviewing the session idle timeout, and locking a value for every organization from the tenant. Read more: [How Config works](/docs/government/config/overview.md).
174184
175185<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-06-config-essentials.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=8624805f501e6ca7e01e12e6e94602ab" aria-label="Video walkthrough: Config essentials" />
176186
187Video: Config essentials (2 min 23 s). Narrated with an AI-generated voice, with on-screen captions.
188
177189> **Transcript**
178190>
179191> Config sets product behavior for the people you manage. The tenant and each organization share the same page, and each level starts from the one above it.
from line 208
196208
197209### Connectors and plugins
198210
199Setting up the Microsoft 365 connector, adding a connector of your own with a tool policy, and adding a plugin. Read more: [Connectors](/docs/government/connectors/overview) and [Manage plugins and connectors](/docs/government/config/plugins-and-connectors).
211Setting up the Microsoft 365 connector, adding a connector of your own with a tool policy, and adding a plugin. Read more: [Connectors](/docs/government/connectors/overview.md) and [Manage plugins and connectors](/docs/government/config/plugins-and-connectors.md).
200212
201213<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-07-connectors-and-plugins.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=43f78d15928eea46d27229f8dbc04db6" aria-label="Video walkthrough: Connectors and plugins" />
202214
215Video: Connectors and plugins (2 min 8 s). Narrated with an AI-generated voice, with on-screen captions.
216
203217> **Transcript**
204218>
205219> A connector lets Claude reach another service, such as Microsoft 365 or a system of your own. A plugin packages skills and commands for Claude Desktop.
from line 236
222236
223237### Pilot Claude Desktop on one machine
224238
225Connecting one copy of Claude Desktop to Claude for Government with the bootstrap address, signing in, and exporting the configuration for your fleet. Read more: [Configure a single machine](/docs/government/deploy-desktop/configure#configure-a-single-machine).
239Connecting one copy of Claude Desktop to Claude for Government with the bootstrap address, signing in, and exporting the configuration for your fleet. Read more: [Configure a single machine](/docs/government/deploy-desktop/configure.md#configure-a-single-machine).
226240
227241<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-08-pilot-claude-desktop-on-one-machine.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=753d21fb976775a19f3cca9521b738b3" aria-label="Video walkthrough: Pilot Claude Desktop on one machine" />
228242
243Video: Pilot Claude Desktop on one machine (1 min 34 s). Narrated with an AI-generated voice, with on-screen captions.
244
229245> **Transcript**
230246>
231247> A fresh install connects to claude.ai. One setting, the bootstrap address on your Claude for Government host, points it at Claude for Government. Everything else arrives at sign-in.
from line 262
246262
247263### Deploy to your fleet
248264
249Delivering the bootstrap address and the setting that hides the claude.ai sign-in option as device policy, installing the Windows package, enabling the **Virtual Machine Platform** feature that Cowork needs, allowing network access, and deciding on automatic updates. Read more: [Deploy to your fleet](/docs/government/deploy-desktop/configure#deploy-to-your-fleet).
265Delivering the bootstrap address and the setting that hides the claude.ai sign-in option as device policy, installing the Windows package, enabling the **Virtual Machine Platform** feature that Cowork needs, allowing network access, and deciding on automatic updates. Read more: [Deploy to your fleet](/docs/government/deploy-desktop/configure.md#deploy-to-your-fleet).
250266
251267<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-09-deploy-to-your-fleet.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=bde163c8a3661fd5393106756950713c" aria-label="Video walkthrough: Deploy to your fleet" />
252268
269Video: Deploy to your fleet (1 min 31 s). Narrated with an AI-generated voice, with on-screen captions.
270
253271> **Transcript**
254272>
255273> Push two values as device policy, the bootstrap address and the setting that hides the claude.ai sign-in option. On macOS they live in a configuration profile, on Windows in machine policy. Deliver them before the app, and note they carry no secrets.
from line 284
266284
267285### Verify a managed device and spot common failures
268286
269What a correctly managed device shows, and the usual causes of an empty model picker, a claude.ai sign-in screen, a repeated settings prompt, and an expired session. Read more: [Confirm it worked](/docs/government/deploy-desktop/configure#confirm-it-worked) and [Troubleshooting](/docs/government/deploy-desktop/configure#troubleshooting).
287What a correctly managed device shows, and the usual causes of an empty model picker, a claude.ai sign-in screen, a repeated settings prompt, and an expired session. Read more: [Confirm it worked](/docs/government/deploy-desktop/configure.md#confirm-it-worked) and [Troubleshooting](/docs/government/deploy-desktop/configure.md#troubleshooting).
270288
271289<video controls preload="metadata" playsInline src="https://mintcdn.com/claude-ai/gGFKuNSbKYs4JMmK/images/government/videos/admin-10-verify-a-managed-device-and-spot-common-failures.mp4?fit=max&auto=format&n=gGFKuNSbKYs4JMmK&q=85&s=3a725133f700322bdfcf0d684f9fd1c8" aria-label="Video walkthrough: Verify a managed device and spot common failures" />
290
291Video: Verify a managed device and spot common failures (1 min 40 s). Narrated with an AI-generated voice, with on-screen captions.
272292
273293> **Transcript**
274294>
office-agents/connectors-and-skills Changed · +5 / -5 lines
from line 12
1212> as Amazon Bedrock, Google Cloud Vertex AI, Azure AI Foundry, or an LLM
1313> gateway, these capabilities may not be available. See the feature
1414> comparison in
15> [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms)
15> [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms.md)
1616> for the current status by connection mode.
1717
1818## Connectors
from line 49
4949
5050See the per-app guides for setup and feature details.
5151
52* [Use Claude for Excel](/docs/office-agents/excel)
53* [Use Claude for PowerPoint](/docs/office-agents/powerpoint)
54* [Use Claude for Word](/docs/office-agents/word)
55* [Use Claude for Outlook](/docs/office-agents/outlook)
52* [Use Claude for Excel](/docs/office-agents/excel.md)
53* [Use Claude for PowerPoint](/docs/office-agents/powerpoint.md)
54* [Use Claude for Word](/docs/office-agents/word.md)
55* [Use Claude for Outlook](/docs/office-agents/outlook.md)
5656
office-agents/data-storage Changed · +8 / -8 lines
from line 127
127127
128128Signing out also asks Anthropic to revoke the Claude account sign-in that the
129129task pane holds, and a sign-in that
130[serves add-in settings from your Claude organization](/docs/office-agents/third-party-platforms#serve-add-in-settings-from-your-claude-organization),
130[serves add-in settings from your Claude organization](/docs/office-agents/third-party-platforms.md#serve-add-in-settings-from-your-claude-organization),
131131so that they cannot be used to get new access tokens. The add-in sends this
132132request once and does not try again if it fails. A separate Claude sign-in in
133133an Office app with its own storage is not revoked. Signing out does not revoke
from line 252
252252| Files that a user attaches, with a Claude account sign-in | Uploaded to Anthropic with the user's Claude sign-in when the user attaches them, before the message is sent. Each file expires 28 days after the add-in uploads it. If Anthropic does not accept an expiry for the user's organization, the add-in uploads the file with no expiry. The add-in does not delete files itself. Earlier versions of the add-in set no expiry on the files they uploaded. The add-in started setting an expiry on September 15, 2026 |
253253| Chat history, uploaded skills, and connector registrations | Not synced between devices and not backed up on any server. The add-in still sends their contents to the model endpoint when Claude uses them, as the rows above describe. Every chat request includes the name and description of each skill that is turned on. With a Claude account sign-in, it also includes the name and description of each plugin the user has turned on, with the names of its skills and connectors, and the organization's Claude settings can turn skills off, which stops both. When Claude uses a skill, the add-in also sends the skill's instructions and Markdown files. With a Claude account sign-in, files attached in a chat are also uploaded to Anthropic |
254254| Claude for Outlook writing style guide, draft preferences, and scratchpad | Not synced between devices and not backed up on any server. To build the style guide and the draft preferences, the add-in sends recent sent mail, with the first recipient's address of each message, and the user's edits to drafts to the model endpoint. After that, every Outlook chat request includes the style guide and the draft preferences, and every message the user sends in Outlook includes the scratchpad |
255| Sign-in credentials | To the services the sign-in is for, with two exceptions described last. A Bedrock sign-in sends the Entra ID token to AWS, which exchanges it for short-lived credentials. A Claude account token also goes to `claude.ai` with feature-flag requests. The exceptions: a credential that you put in the query string of the manifest URL also reaches Anthropic's server at `pivot.claude.ai` each time the add-in loads, and the server's request logs record it. A Vertex AI sign-in also returns Google's one-time authorization code to `pivot.claude.ai` in the query string, where request logs can record it. The code cannot be exchanged for a token without your OAuth client secret, so keep the client secret out of the manifest URL query string too. See [Keep credentials out of the manifest URL query string](/docs/office-agents/third-party-platforms#keep-credentials-out-of-the-manifest-url-query-string) |
255| Sign-in credentials | To the services the sign-in is for, with two exceptions described last. A Bedrock sign-in sends the Entra ID token to AWS, which exchanges it for short-lived credentials. A Claude account token also goes to `claude.ai` with feature-flag requests. The exceptions: a credential that you put in the query string of the manifest URL also reaches Anthropic's server at `pivot.claude.ai` each time the add-in loads, and the server's request logs record it. A Vertex AI sign-in also returns Google's one-time authorization code to `pivot.claude.ai` in the query string, where request logs can record it. The code cannot be exchanged for a token without your OAuth client secret, so keep the client secret out of the manifest URL query string too. See [Keep credentials out of the manifest URL query string](/docs/office-agents/third-party-platforms.md#keep-credentials-out-of-the-manifest-url-query-string) |
256256| Identifiers on model requests | Each request for a model response carries the name of the add-in, a random identifier for the device, and a session ID. For a chat message, the session ID is the conversation's ID. The add-in also sends helper requests to the same endpoint. In every Office app, they summarize a long conversation, write the status line shown while Claude thinks, and, when memory is on, check an entry before Claude saves it. In Word and PowerPoint, they check how the document or a slide looks after Claude edits it, and in Word they also check Claude's reasoning before it edits legal language. In Outlook, they rewrite a passage the user selects in a draft, and learn the user's writing style from recent sent mail and from the user's edits to drafts. Each helper request carries a session ID made from the kind of helper request, the device identifier, and the date in UTC, so helper requests of one kind from one device on one day share a session ID. With a Claude account sign-in, requests also carry the user's account ID. In third-party platform deployments, requests carry no account ID and no email address. That includes deployments whose settings Anthropic serves, where members sign in with a Claude account. The short test requests that the add-in sends to check which models and features your endpoint supports, such as web search and code execution, carry none of these values |
257257| Feature-flag requests | In every deployment, the add-in asks `claude.ai` which features to show. Each request includes the device identifier, the Office app, and, when the user is signed in to Office, the Entra ID tenant ID. With a Claude account sign-in, it also includes the user's email address, account ID, and organization ID. In every deployment, the add-in sends a usage event for each feature variant it showed. With a Claude account sign-in, the add-in also sends each variant it showed directly to Anthropic, with the organization ID |
258258| Usage events | Sent to Anthropic's server at `pivot.claude.ai`, which forwards them to Anthropic's event logging service. Each event has a name and properties such as counts, durations, the model, and the Office app and its version, with the device identifier and an ID for the task pane session. With a Claude account sign-in, events also carry the account and organization IDs. Before sending an event, the add-in removes the fields known to carry file names, file paths, error text, and the names of your connectors and their tools. The filter matches field names, so it does not remove such text from a field it does not name. Events that load an Excel workbook or a PowerPoint presentation carry an unsalted hash of the file's path or address. With a Claude account sign-in, a user can rate a response and add a comment. The comment reaches Anthropic's server, which forwards the comment's length but not its text. When a user types a job role that is not on the list, the server forwards that the user chose Other, but not the text |
from line 260
260260| Error reports sent to Sentry, with a Claude account sign-in | The user's account ID, the text of the error, the name of the tool that failed, and details about what failed, such as the name of a skill, a skill file, a memory entry, or a connector's host. The error text and these details can include conversation and document content. A report also lists the hosts the add-in contacted before the error |
261261| Error reports sent to Sentry, in third-party platform deployments | Once the add-in has loaded the user's sign-in, each report holds only the type of error, where in the code it happened, the add-in's version, the Office app with its platform and version, the sign-in type, and the name of the built-in tool that failed. Reports sent before that point, such as those from the sign-in page, also include the error text and the hosts the add-in contacted |
262262| Diagnostic traces, logs, and metrics sent to Anthropic | Counts, durations, error types, the model, request IDs, the names of built-in tools, and a session ID. With a Claude account sign-in, traces also carry the organization ID. Before sending traces and logs, the add-in removes every field that is not on an allowlist, so they exclude conversation text, document contents, file names, and the names of your connectors and their tools. Before sending metrics, the add-in removes a list of fields that includes file names and connector names |
263| Telemetry sent to a custom OpenTelemetry collector you configure | A collector set in the claude.ai admin console, in the manifest, in Entra ID claims, or by your bootstrap endpoint receives the full audit trail, including prompt content and tool inputs and outputs. That path skips the allowlist filter by design. A collector named in add-in settings that Anthropic serves from your Claude organization receives only the kinds of content those settings select, and no conversation or tool content if they select none. While a custom collector is set, traces and logs go only to that collector, and metrics still go to Anthropic. See [Audit and observability](/docs/office-agents/enterprise-readiness#audit-and-observability) |
263| Telemetry sent to a custom OpenTelemetry collector you configure | A collector set in the claude.ai admin console, in the manifest, in Entra ID claims, or by your bootstrap endpoint receives the full audit trail, including prompt content and tool inputs and outputs. That path skips the allowlist filter by design. A collector named in add-in settings that Anthropic serves from your Claude organization receives only the kinds of content those settings select, and no conversation or tool content if they select none. While a custom collector is set, traces and logs go only to that collector, and metrics still go to Anthropic. See [Audit and observability](/docs/office-agents/enterprise-readiness.md#audit-and-observability) |
264264
265265When Anthropic
266[serves your add-in settings from your Claude organization](/docs/office-agents/third-party-platforms#serve-add-in-settings-from-your-claude-organization),
266[serves your add-in settings from your Claude organization](/docs/office-agents/third-party-platforms.md#serve-add-in-settings-from-your-claude-organization),
267267members sign in with a Claude account. This option is in preview. Feature-flag
268268requests, usage events, and the session records that Sentry keeps, which count
269269sessions and crashes, then carry the identifiers described for a Claude account
from line 295
295295In third-party platform deployments, including those whose settings Anthropic
296296serves, no add-in setting stops usage events or error reports. You can block
297297the Sentry host listed in the
298[network allowlist](/docs/office-agents/third-party-platforms#network-allowlist).
298[network allowlist](/docs/office-agents/third-party-platforms.md#network-allowlist).
299299
300300## Export a user's data before a device is rebuilt
301301
from line 303
303303macOS and Windows. They read Office's storage and write only to the folder you
304304name, and running them with no arguments reports what was found without copying
305305anything. See
306[Deploy the add-in for your organization](/docs/office-agents/third-party-platforms#deploy-the-add-in-for-your-organization)
306[Deploy the add-in for your organization](/docs/office-agents/third-party-platforms.md#deploy-the-add-in-for-your-organization)
307307for installation, then run `/claude-for-msft-365-install:export-data`.
308308
309309Export before any of the following:
from line 320
320320The pages below cover the deployment and security topics that reference this
321321data.
322322
323* [Security, admin auditability, and analytics](/docs/office-agents/enterprise-readiness)
324* [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms)
323* [Security, admin auditability, and analytics](/docs/office-agents/enterprise-readiness.md)
324* [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms.md)
325325
office-agents/enterprise-readiness Changed · +8 / -8 lines
from line 22
2222 third-party architecture diagram is listed alongside the first-party
2323 one in the [Trust Center resources](https://trust.anthropic.com/resources?s=e3n7pvyjnxjyahmdmqujcx);
2424 filter for "Claude for Excel, PowerPoint, Word".
25 [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms)
26 has per-mode request-flow diagrams for the [LLM gateway](/docs/office-agents/third-party-platforms#llm-gateway)
27 and [Bedrock, Vertex AI, or Foundry direct](/docs/office-agents/third-party-platforms#bedrock-vertex-ai-or-foundry-direct)
25 [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms.md)
26 has per-mode request-flow diagrams for the [LLM gateway](/docs/office-agents/third-party-platforms.md#llm-gateway)
27 and [Bedrock, Vertex AI, or Foundry direct](/docs/office-agents/third-party-platforms.md#bedrock-vertex-ai-or-foundry-direct)
2828 paths, plus deployment guidance.
2929
3030## Audit and observability
from line 49
4949and `Access-Control-Allow-Headers` covering `Content-Type` plus any
5050headers you configure for the export, such as `Authorization`. It must
5151also return the same `Access-Control-Allow-Origin` header on the `POST`
52response. The [CORS requirements for an LLM gateway](/docs/office-agents/third-party-platforms#cors-requirements)
52response. The [CORS requirements for an LLM gateway](/docs/office-agents/third-party-platforms.md#cors-requirements)
5353describe the same browser behavior in more detail.
5454
5555Managed OTLP ingest endpoints such as Grafana Cloud are designed for
from line 62
6262appear in the export headers, which reach every signed-in user's
6363browser.
6464
65See [Configure a custom OpenTelemetry collector](/docs/office-agents/opentelemetry)
65See [Configure a custom OpenTelemetry collector](/docs/office-agents/opentelemetry.md)
6666for the configuration keys, endpoint requirements, and full span reference.
6767
6868> [!NOTE]
from line 97
9797The pages below cover deployment paths and plugins relevant to
9898enterprise admins.
9999
100* [Data storage and retention](/docs/office-agents/data-storage)
101* [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms)
102* [Install financial services plugins for Cowork](/docs/office-agents/fsi-plugins)
100* [Data storage and retention](/docs/office-agents/data-storage.md)
101* [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms.md)
102* [Install financial services plugins for Cowork](/docs/office-agents/fsi-plugins.md)
103103
office-agents/excel Changed · +6 / -6 lines
from line 95
9595deploy using the custom manifest XML file instead. Download the
9696[Excel manifest XML file](https://pivot.claude.ai/manifest-excel.xml),
9797then follow
98[Deploy with a custom manifest](/docs/office-agents/word#deploy-with-a-custom-manifest)
98[Deploy with a custom manifest](/docs/office-agents/word.md#deploy-with-a-custom-manifest)
9999for the upload steps. The flow is identical apart from which manifest
100100file you upload in Step 1.
101101
from line 104
104104If your organization routes AI traffic through Amazon Bedrock, Google Cloud
105105Vertex AI, Azure AI Foundry, or an LLM gateway, your admin can deploy
106106the add-in without individual Claude accounts. See
107[Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms).
107[Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms.md).
108108
109109## Key features
110110
from line 160
160160
161161Claude for Excel supports connectors for pulling external context into
162162your workbook, and Skills for applying reusable task recipes. See
163[Connectors and Skills](/docs/office-agents/connectors-and-skills) for
163[Connectors and Skills](/docs/office-agents/connectors-and-skills.md) for
164164details.
165165
166166## Set persistent instructions
from line 180
180180Claude for Excel shares context with Claude for PowerPoint, Word, and
181181Outlook, so a single conversation can span your open workbook,
182182presentation, document, and inbox. See
183[Work across M365 apps](/docs/office-agents/work-across-apps).
183[Work across M365 apps](/docs/office-agents/work-across-apps.md).
184184
185185## Context and session management
186186
from line 208
208208through Amazon Bedrock, Google Cloud Vertex AI, Azure AI Foundry, or an
209209LLM gateway, the available models come from that platform and your
210210admin's configuration instead of your Claude.ai model access settings.
211See [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms)
211See [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms.md)
212212for details.
213213
214214## Data handling
from line 223
223223Conversations are not stored on Anthropic's servers, are not synced
224224across devices, and can be cleared from Settings at any time.
225225Reinstalling the add-in or switching between Claude add-ins does not
226remove it. See [Data storage and retention](/docs/office-agents/data-storage)
226remove it. See [Data storage and retention](/docs/office-agents/data-storage.md)
227227for where it sits on disk and how long it is kept.
228228
229229Claude for Excel does not inherit custom data retention settings your
office-agents/outlook Changed · +11 / -9 lines
from line 180
180180
181181The redirect to `pivot.claude.ai` after consent carries only the consent
182182outcome, never a token or authorization code. See
183[Why sign-in redirects through pivot.claude.ai](/docs/office-agents/third-party-platforms#why-sign-in-redirects-through-pivot-claude-ai)
183[Why sign-in redirects through pivot.claude.ai](/docs/office-agents/third-party-platforms.md#why-sign-in-redirects-through-pivot-claude-ai)
184184for what each redirect carries and how to verify it in a network capture.
185185
186186#### Use your own Entra app instead
from line 234
234234your own application.
235235
236236If you deploy through a third-party platform and generate your manifests
237with the [setup wizard](/docs/office-agents/third-party-platforms#run-the-setup-wizard),
237with the [setup wizard](/docs/office-agents/third-party-platforms.md#run-the-setup-wizard),
238238provide the client ID to the wizard as `graph_client_id` instead of
239239editing the file. See
240[Deploy to Outlook](/docs/office-agents/third-party-platforms#deploy-to-outlook).
240[Deploy to Outlook](/docs/office-agents/third-party-platforms.md#deploy-to-outlook).
241241
242242### Deploy in a US Government or national cloud
243243
from line 275
275275by Claude Code.
276276
277277For setup instructions and gateway requirements, see
278[Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms).
278[Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms.md).
279279
280280## Triage your inbox
281281
from line 325
325325Claude reads `.docx` and `.xlsx` attachments on the open email without
326326you opening them. For `.pptx` attachments, open the deck in PowerPoint
327327with the thread loaded as context using
328[Work across M365 apps](/docs/office-agents/work-across-apps). PDF attachments
328[Work across M365 apps](/docs/office-agents/work-across-apps.md). PDF attachments
329329are not currently read inline; save the file and upload it through the
330330sidebar instead.
331331
from line 377
377377an email into an open Excel model, without copying between apps.
378378
379379For setup instructions, see
380[Work across M365 apps](/docs/office-agents/work-across-apps).
380[Work across M365 apps](/docs/office-agents/work-across-apps.md).
381381
382382## Model availability
383383
from line 400
400400
401401
402402
403Outlook mailbox access: the open item comes through Office.js, broader mailbox actions use Microsoft Graph, and the Graph token stays in the browser.
404
403405Where mailbox content goes after Claude reads it depends on how you sign
404406in.
405407
from line 422
420422described in
421423[Claude in Microsoft Foundry](https://platform.claude.com/docs/en/build-with-claude/claude-in-microsoft-foundry).
422424See
423[Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms)
425[Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms.md)
424426for configuration details. The add-in does not keep a server-side copy or
425427index of your mailbox.
426428
from line 436
434436your user ID, and your organization ID, so your Excel and Outlook
435437histories are separate. Reinstalling the add-in or switching between
436438Claude add-ins does not remove it. See
437[Data storage and retention](/docs/office-agents/data-storage) for where it
439[Data storage and retention](/docs/office-agents/data-storage.md) for where it
438440sits on disk and how long it is kept.
439441
440442## Data retention and audit
from line 448
446448Enterprise organizations can route full audit telemetry from Claude for
447449Outlook to their own OpenTelemetry collector for integration with a SIEM
448450or observability platform. See
449[Configure a custom OpenTelemetry collector](/docs/office-agents/enterprise-readiness)
451[Configure a custom OpenTelemetry collector](/docs/office-agents/enterprise-readiness.md)
450452for setup. On Pro, Max, and Team plans, observability and audit
451453export are not available. Claude for Outlook does not inherit custom
452454data retention settings your organization may have configured and is not
office-agents/overview Changed · +11 / -11 lines
from line 11
1111
1212The pages below cover each surface and the features that span them.
1313
14* [Claude for Excel](/docs/office-agents/excel): read and write cells,
14* [Claude for Excel](/docs/office-agents/excel.md): read and write cells,
1515 formulas, formatting, pivot tables, and charts.
16* [Claude for PowerPoint](/docs/office-agents/powerpoint): read, edit,
16* [Claude for PowerPoint](/docs/office-agents/powerpoint.md): read, edit,
1717 and generate slides using your existing templates.
18* [Claude for Word](/docs/office-agents/word): draft, redline, and
18* [Claude for Word](/docs/office-agents/word.md): draft, redline, and
1919 review documents with tracked changes and comment-driven editing.
20* [Claude for Outlook](/docs/office-agents/outlook): triage your inbox,
20* [Claude for Outlook](/docs/office-agents/outlook.md): triage your inbox,
2121 draft replies in your voice, summarize threads, and find meeting times.
2222 Admins must complete a one-time
23 [Microsoft Graph consent](/docs/office-agents/outlook#grant-microsoft-graph-consent)
23 [Microsoft Graph consent](/docs/office-agents/outlook.md#grant-microsoft-graph-consent)
2424 before deployment.
25* [Work across M365 apps](/docs/office-agents/work-across-apps):
25* [Work across M365 apps](/docs/office-agents/work-across-apps.md):
2626 Claude for Excel, PowerPoint, Word, and Outlook share conversation
2727 state, so actions in one app are informed by what happened in the
2828 others.
29* [Connectors and Skills](/docs/office-agents/connectors-and-skills):
29* [Connectors and Skills](/docs/office-agents/connectors-and-skills.md):
3030 extend Claude with external context and reusable task recipes.
31* [Dictation](/docs/office-agents/dictation): speak prompts instead
31* [Dictation](/docs/office-agents/dictation.md): speak prompts instead
3232 of typing them.
3333
3434## Deployment
from line 35
3535
3636These pages cover enterprise admin setup and observability.
3737
38* [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms):
38* [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms.md):
3939 connect through Amazon Bedrock, Google Cloud Vertex AI, Azure AI Foundry,
4040 or an LLM gateway.
41* [Security, admin auditability, and analytics](/docs/office-agents/enterprise-readiness):
41* [Security, admin auditability, and analytics](/docs/office-agents/enterprise-readiness.md):
4242 security architecture diagrams, OpenTelemetry audit, usage analytics,
4343 and spend tracking.
44* [Configure a custom OpenTelemetry collector](/docs/office-agents/opentelemetry):
44* [Configure a custom OpenTelemetry collector](/docs/office-agents/opentelemetry.md):
4545 route the full audit trail to a collector you operate, with the
4646 configuration keys and span reference.
4747
office-agents/powerpoint Changed · +5 / -5 lines
from line 135
135135If your organization routes AI traffic through Amazon Bedrock, Google Cloud
136136Vertex AI, Azure AI Foundry, or an LLM gateway, your admin can deploy
137137the add-in without individual Claude accounts. See
138[Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms).
138[Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms.md).
139139
140140## Key features
141141
from line 195
195195
196196Claude for PowerPoint supports connectors for pulling external context
197197into your deck, and Skills for applying reusable task recipes. See
198[Connectors and Skills](/docs/office-agents/connectors-and-skills) for
198[Connectors and Skills](/docs/office-agents/connectors-and-skills.md) for
199199details.
200200
201201## Set persistent instructions
from line 215
215215Claude for PowerPoint shares context with Claude for Excel, Word, and
216216Outlook, so a single conversation can span your open deck, workbook,
217217document, and inbox. See
218[Work across M365 apps](/docs/office-agents/work-across-apps).
218[Work across M365 apps](/docs/office-agents/work-across-apps.md).
219219
220220## Context and session management
221221
from line 241
241241through Amazon Bedrock, Google Cloud Vertex AI, Azure AI Foundry, or an
242242LLM gateway, the available models come from that platform and your
243243admin's configuration instead of your Claude.ai model access settings.
244See [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms)
244See [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms.md)
245245for details.
246246
247247## Data handling
from line 256
256256Conversations are not stored on Anthropic's servers, are not synced
257257across devices, and can be cleared from Settings at any time.
258258Reinstalling the add-in or switching between Claude add-ins does not
259remove it. See [Data storage and retention](/docs/office-agents/data-storage)
259remove it. See [Data storage and retention](/docs/office-agents/data-storage.md)
260260for where it sits on disk and how long it is kept.
261261
262262Claude for PowerPoint does not inherit custom data retention settings
office-agents/third-party-platforms Changed · +15 / -7 lines
from line 86
8686organization's Claude IP allowlist using the address they arrive from. If
8787your proxy sends traffic for that domain out through an address that is not
8888on that allowlist,
89[work across apps](/docs/office-agents/work-across-apps) stops while the rest of
89[work across apps](/docs/office-agents/work-across-apps.md) stops while the rest of
9090the add-in keeps working.
9191
9292### Third-party platforms (3P)
from line 198
198198| `/claude-for-msft-365-install:update-user-attrs` | Writes per-user configuration via Microsoft Graph extension attributes. |
199199| `/claude-for-msft-365-install:bootstrap` | Builds a bootstrap endpoint for per-user MCP servers, skills, and dynamic config. |
200200| `/claude-for-msft-365-install:debug` | Diagnoses deployment issues: stale config after a manifest update, connection failures, an add-in that does not appear, sign-in or admin-consent loops, and reading the add-in's error paste. |
201| `/claude-for-msft-365-install:export-data` | Makes a read-only copy of a user's chat history, skills, connector registrations, and settings before a device is rebuilt. See [Data storage and retention](/docs/office-agents/data-storage). |
201| `/claude-for-msft-365-install:export-data` | Makes a read-only copy of a user's chat history, skills, connector registrations, and settings before a device is rebuilt. See [Data storage and retention](/docs/office-agents/data-storage.md). |
202202
203203Run `/claude-for-msft-365-install:debug` whenever a connection or sign-in
204204does not behave as expected. It triages from the symptom, reads the "Copy
from line 233
233233
234234
235235
236Configuration resolution at add-in load: bootstrap, Entra ID attributes, then manifest parameters.
237
236238### Keep credentials out of the manifest URL query string
237239
238240Prefer a bootstrap endpoint (`bootstrap_url`) or Entra ID sign-in with
from line 302
300302Claude for Outlook reads mail and calendar data through Microsoft Graph,
301303which requires a one-time tenant-wide grant from a Global Administrator
302304regardless of which platform serves the model. Complete the
303[Microsoft Graph admin consent](/docs/office-agents/outlook#grant-microsoft-graph-consent)
305[Microsoft Graph admin consent](/docs/office-agents/outlook.md#grant-microsoft-graph-consent)
304306step before deployment so users are not prompted individually. The Graph
305307token stays in the user's Outlook client and is never sent to your
306308gateway or to Anthropic.
from line 311
309311multi-tenant application, register your own single-tenant Entra
310312application with the same delegated Graph permissions and provide its
311313client ID to the setup wizard as `graph_client_id`. See
312[Use your own Entra app instead](/docs/office-agents/outlook#use-your-own-entra-app-instead).
314[Use your own Entra app instead](/docs/office-agents/outlook.md#use-your-own-entra-app-instead).
313315
314316> [!NOTE]
315317>
from line 522
520522
521523
522524
525LLM gateway request flow: the add-in calls your gateway, which routes to your chosen provider.
526
523527### Bedrock, Vertex AI, or Foundry direct
524528
525529**1. Open the add-in**
from line 561
557561
558562
559563
564Bedrock direct flow: the add-in exchanges an Entra ID token for an AWS role, then calls Bedrock.
565
560566Vertex AI direct authenticates through Google OAuth, then calls Vertex
561567AI.
562568
563569
564570
571Vertex AI direct flow: the add-in authenticates with Google OAuth, then calls Vertex AI.
572
565573### Foundry direct without an API key
566574
567575Instead of a shared resource key, each user can authenticate to your
from line 587
5795871. In your Entra app registration, add the **Azure Cognitive Services**
580588 delegated permission `user_impersonation` and grant admin consent.
581589 Register the add-in's redirect URI as described in
582 [Use your own Entra app instead](/docs/office-agents/outlook#use-your-own-entra-app-instead).
590 [Use your own Entra app instead](/docs/office-agents/outlook.md#use-your-own-entra-app-instead).
5835912. Grant the users or groups who will sign in the **Cognitive Services
584592 User** role on the Foundry resource.
5855933. Put these parameters in the manifest URL (no `azure_api_key`):
from line 903
895903
896904To route a full audit trail, including prompts, tool inputs, tool
897905outputs, and document references, to your own infrastructure, see
898[Configure a custom OpenTelemetry collector](/docs/office-agents/opentelemetry).
906[Configure a custom OpenTelemetry collector](/docs/office-agents/opentelemetry.md).
899907That page covers the `otlp_endpoint`, `otlp_headers`, and
900908`otlp_attr_max_chars` configuration keys, the CORS requirements for the
901909collector endpoint, and the full span reference.
from line 974
966974### Microsoft admin-consent redirects
967975
968976The Microsoft Graph consent link in
969[Grant Microsoft Graph consent](/docs/office-agents/outlook#grant-microsoft-graph-consent)
977[Grant Microsoft Graph consent](/docs/office-agents/outlook.md#grant-microsoft-graph-consent)
970978uses Microsoft's
971979[admin-consent endpoint](https://learn.microsoft.com/en-us/entra/identity-platform/v2-admin-consent).
972980By Microsoft's specification, the redirect back to
office-agents/word Changed · +5 / -5 lines
from line 143
143143If your organization routes AI traffic through Amazon Bedrock, Google Cloud
144144Vertex AI, Azure AI Foundry, or an LLM gateway, your admin can deploy
145145the add-in without individual Claude accounts. See
146[Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms).
146[Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms.md).
147147
148148## Key features
149149
from line 245
245245
246246Claude for Word supports connectors for pulling external context into
247247your document, and Skills for applying reusable task recipes. See
248[Connectors and Skills](/docs/office-agents/connectors-and-skills) for
248[Connectors and Skills](/docs/office-agents/connectors-and-skills.md) for
249249details.
250250
251251## Set persistent instructions
from line 265
265265Claude for Word shares context with Claude for Excel, PowerPoint, and
266266Outlook, so a single conversation can span your open document,
267267workbook, deck, and inbox. See
268[Work across M365 apps](/docs/office-agents/work-across-apps).
268[Work across M365 apps](/docs/office-agents/work-across-apps.md).
269269
270270## Context and session management
271271
from line 291
291291through Amazon Bedrock, Google Cloud Vertex AI, Azure AI Foundry, or an
292292LLM gateway, the available models come from that platform and your
293293admin's configuration instead of your Claude.ai model access settings.
294See [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms)
294See [Use Claude for M365 with third-party platforms](/docs/office-agents/third-party-platforms.md)
295295for details.
296296
297297## Data handling
from line 306
306306Conversations are not stored on Anthropic's servers, are not synced
307307across devices, and can be cleared from Settings at any time.
308308Reinstalling the add-in or switching between Claude add-ins does not
309remove it. See [Data storage and retention](/docs/office-agents/data-storage)
309remove it. See [Data storage and retention](/docs/office-agents/data-storage.md)
310310for where it sits on disk and how long it is kept.
311311
312312Claude for Word does not inherit custom data retention settings your
office-agents/work-across-apps Changed · +4 / -4 lines
from line 19
1919on cross-app mode.
2020
2121* A paid Claude plan: Pro, Max, Team, or Enterprise.
22* [Claude for Excel](/docs/office-agents/excel) installed from the
22* [Claude for Excel](/docs/office-agents/excel.md) installed from the
2323 Microsoft AppSource.
24* [Claude for PowerPoint](/docs/office-agents/powerpoint) installed
24* [Claude for PowerPoint](/docs/office-agents/powerpoint.md) installed
2525 from the Microsoft AppSource.
26* [Claude for Word](/docs/office-agents/word) installed from the
26* [Claude for Word](/docs/office-agents/word.md) installed from the
2727 Microsoft AppSource.
28* [Claude for Outlook](/docs/office-agents/outlook) installed from the
28* [Claude for Outlook](/docs/office-agents/outlook.md) installed from the
2929 Microsoft AppSource.
3030
3131## Enable cross-app mode
plugins/admin Changed · +13 / -13 lines
from line 9
99> [!NOTE]
1010>
1111> * If you set plugin policy for the Claude Code command line, see [managed settings](https://code.claude.com/docs/en/plugins/org) in the Claude Code docs
12> * If you want one plugin to reach members in claude.ai and Cowork and developers in the Claude Code command line, and need to decide between this page and managed settings, or use the two together, see [Roll out a plugin to your whole organization](/docs/plugins/org-rollout)
13> * If you run Claude Desktop on your own model provider, see [MCP, plugins, skills, and hooks](/docs/third-party/claude-desktop/extensions)
12> * If you want one plugin to reach members in claude.ai and Cowork and developers in the Claude Code command line, and need to decide between this page and managed settings, or use the two together, see [Roll out a plugin to your whole organization](/docs/plugins/org-rollout.md)
13> * If you run Claude Desktop on your own model provider, see [MCP, plugins, skills, and hooks](/docs/third-party/claude-desktop/extensions.md)
1414
1515To start, go to [**Organization settings > Plugins & skills**](https://claude.ai/admin-settings/skills?tab=inventory). From there you can [review what your organization has](#review-your-organization%E2%80%99s-inventory), [set each plugin's availability](#set-availability), or [add your organization's own plugins](#add-your-own-plugins).
1616
from line 97
9797
9898Members then get that version, and **Current** moves to it. Reverting deletes nothing, so every version stays in the list. To go forward again, open a newer version's menu and select **Make this the current version**.
9999
100Reverting isn't available for an item synced from a repository. Fix the plugin in the repository and push to the default branch. Then select **Re-sync** on the marketplace in the [**Marketplaces**](https://claude.ai/admin-settings/skills?tab=marketplaces) tab, as [Update through organization settings](/docs/plugins/org-rollout#update-through-organization-settings) describes.
100Reverting isn't available for an item synced from a repository. Fix the plugin in the repository and push to the default branch. Then select **Re-sync** on the marketplace in the [**Marketplaces**](https://claude.ai/admin-settings/skills?tab=marketplaces) tab, as [Update through organization settings](/docs/plugins/org-rollout.md#update-through-organization-settings) describes.
101101
102102While the repository is being fixed, you can [set the plugin's availability](#set-availability) to **Not available**. Members stop seeing the plugin and Claude stops loading it for them, including members who had it installed. On Enterprise, a group's own **Group access…** setting replaces the organization-wide one for that group's members, as [Limit to user groups on Enterprise](#limit-to-user-groups-on-enterprise) explains. Set any group that has one for this plugin to **Not available** as well. Set the availability back when the fix has synced. Don't use **Delete source** on the marketplace for this, because it permanently deletes every plugin in that marketplace for every member.
103103
from line 140
140140
141141You can set availability for plugins your organization owns and for plugins from Anthropic's catalogs. An item a member created for themselves has no availability setting.
142142
143In Claude Code sessions that sync the member's account plugins, a required plugin stays on as well. [Choose a rollout route](/docs/plugins/org-rollout#choose-a-rollout-route) says which sessions sync, and [Control which synced plugins load](https://code.claude.com/docs/en/plugins/loading#control-which-synced-plugins-load) in the Claude Code docs covers what the member sees there.
143In Claude Code sessions that sync the member's account plugins, a required plugin stays on as well. [Choose a rollout route](/docs/plugins/org-rollout.md#choose-a-rollout-route) says which sessions sync, and [Control which synced plugins load](https://code.claude.com/docs/en/plugins/loading#control-which-synced-plugins-load) in the Claude Code docs covers what the member sees there.
144144
145145### Add your own plugins
146146
from line 162
162162
163163A marketplace you add appears on the **Marketplaces** tab, and its plugins appear on the **Inventory** tab. Adding plugins here doesn't publish them anywhere.
164164
165[Sync your organization's plugins from a repository](/docs/plugins/org-sync) covers the repository requirements for syncing, the GitLab setup, and how members receive the plugins without needing access to the repository themselves.
165[Sync your organization's plugins from a repository](/docs/plugins/org-sync.md) covers the repository requirements for syncing, the GitLab setup, and how members receive the plugins without needing access to the repository themselves.
166166
167167### Manage synced marketplaces
168168
from line 222
222222
223223### Let members share plugins with each other
224224
225Members can share a plugin they made with specific people without involving you. In [**Organization settings > Plugins & skills > Policy**](https://claude.ai/admin-settings/skills?tab=policy), **Skill sharing** controls whether members can share skills and plugins they made with specific people in your organization. On Enterprise, **Share with groups** lets them share with user groups as well. [Share a plugin with specific people](/docs/plugins/share#share-a-plugin-with-specific-people) covers what members and recipients see.
225Members can share a plugin they made with specific people without involving you. In [**Organization settings > Plugins & skills > Policy**](https://claude.ai/admin-settings/skills?tab=policy), **Skill sharing** controls whether members can share skills and plugins they made with specific people in your organization. On Enterprise, **Share with groups** lets them share with user groups as well. [Share a plugin with specific people](/docs/plugins/share.md#share-a-plugin-with-specific-people) covers what members and recipients see.
226226
227227### Stop sharing by a member who left
228228
from line 244
244244
245245### Review plugins that members publish
246246
247Members on Team and Enterprise plans can publish a plugin they made to your organization's library with **Publish to org** on the plugin's page. You decide whether that's allowed and whether each request waits for your approval. [Publish a plugin to your organization](/docs/plugins/share#publish-a-plugin-to-your-organization) covers the member's side.
247Members on Team and Enterprise plans can publish a plugin they made to your organization's library with **Publish to org** on the plugin's page. You decide whether that's allowed and whether each request waits for your approval. [Publish a plugin to your organization](/docs/plugins/share.md#publish-a-plugin-to-your-organization) covers the member's side.
248248
249249#### Set the publishing policy
250250
from line 314
314314* **Group over organization**: the setting you choose for a group replaces the organization-wide setting for that group's members, even when the group's setting is stricter. A member who is only in a group set to **Not available** doesn't get a plugin that's **Required** organization-wide. You can also set a group to **Installed by default** or **Required** for a plugin that's **Not available** organization-wide
315315* **Several groups**: when a member is in several groups with different settings for a plugin, the most permissive setting applies, in this order: **Required**, **Installed by default**, **Available to install**, **Not available**
316316
317On a Team plan, which has no group setting, you can pilot a plugin with a few people before everyone gets it: with [**User-created skills**](#control-what-members-add-themselves) on, upload the plugin to your own account from [**Customize > Plugins**](https://claude.ai/customize/plugins) with **Add > Upload plugin**, and [share it with specific people](/docs/plugins/share#share-a-plugin-with-specific-people). When the pilot is done, add it for the organization and set its availability.
317On a Team plan, which has no group setting, you can pilot a plugin with a few people before everyone gets it: with [**User-created skills**](#control-what-members-add-themselves) on, upload the plugin to your own account from [**Customize > Plugins**](https://claude.ai/customize/plugins) with **Add > Upload plugin**, and [share it with specific people](/docs/plugins/share.md#share-a-plugin-with-specific-people). When the pilot is done, add it for the organization and set its availability.
318318
319319## Track usage in your organization
320320
321Members on Team and Enterprise plans see usage figures on a plugin's or skill's own page, as [how a plugin is used in your organization](/docs/plugins/overview#track-plugin-usage-in-your-organization) describes. The [**Inventory**](https://claude.ai/admin-settings/skills?tab=inventory) tab adds one view across all of them. To find which items people use, read the **Users (30d)** column or sort by **Most users**:
321Members on Team and Enterprise plans see usage figures on a plugin's or skill's own page, as [how a plugin is used in your organization](/docs/plugins/overview.md#track-plugin-usage-in-your-organization) describes. The [**Inventory**](https://claude.ai/admin-settings/skills?tab=inventory) tab adds one view across all of them. To find which items people use, read the **Users (30d)** column or sort by **Most users**:
322322
323323* **Users (30d)**: the number of distinct people in your organization who used the item in the last 30 days. A dash means there's no data for the item, not that nobody used it
324324* **Most users**: a **Sort** option that puts the most-used items first
from line 331
331331
332332You control connectors, Claude Code policy, monitoring, and directory submissions separately from plugin availability, and directory review is described with the submission pages:
333333
334* [Roll out a plugin to your whole organization](/docs/plugins/org-rollout): reach members in claude.ai and Cowork and developers in the Claude Code command line with one plugin
334* [Roll out a plugin to your whole organization](/docs/plugins/org-rollout.md): reach members in claude.ai and Cowork and developers in the Claude Code command line with one plugin
335335* [Manage Claude Code plugins for your organization](https://code.claude.com/docs/en/plugins/org): allowlist marketplaces, force-install plugins, and turn account sync on or off for the command line with managed settings
336336* [**Organization settings > Connectors**](https://claude.ai/admin-settings/connectors): choose which connectors members can add, including a plugin's bundled connectors
337* [Monitoring](/docs/cowork/monitoring): export members' Cowork activity to your OpenTelemetry collector
338* [Prepare for review](/docs/directory/publish#prepare-for-review): how Anthropic checks plugins listed in the directory, with automated validation and a security scan on every version and a person reviewing each new listing, for when you're deciding whether to keep the directory as a source
339* [Publish to the directory](/docs/directory/publish): submit a plugin for a public listing through the developer portal, which the **Directory** item in organization settings opens for members with permission to submit
337* [Monitoring](/docs/cowork/monitoring.md): export members' Cowork activity to your OpenTelemetry collector
338* [Prepare for review](/docs/directory/publish.md#prepare-for-review): how Anthropic checks plugins listed in the directory, with automated validation and a security scan on every version and a person reviewing each new listing, for when you're deciding whether to keep the directory as a source
339* [Publish to the directory](/docs/directory/publish.md): submit a plugin for a public listing through the developer portal, which the **Directory** item in organization settings opens for members with permission to submit
340340
plugins/build Changed · +17 / -17 lines
from line 4
44
55A plugin is a folder that packages skills, MCP connectors, commands, and agents, in any combination, so that people add them together. This page is the reference for that folder: what each file is and contains, the manifest fields every app reads, how an MCP connector and its skill fit together, and how to test the plugin on claude.ai, in Cowork, and in Claude Code.
66
7[Build your first plugin](/docs/plugins/quickstart) walks you through making one end to end.
7[Build your first plugin](/docs/plugins/quickstart.md) walks you through making one end to end.
88
99> [!NOTE]
1010>
11> * If you want a plugin for your own use without writing files, see [Create a plugin with Claude](/docs/plugins/create-with-claude), which makes one from a conversation
11> * If you want a plugin for your own use without writing files, see [Create a plugin with Claude](/docs/plugins/create-with-claude.md), which makes one from a conversation
1212> * If you're building for Claude Code only, see its [plugin authoring docs](https://code.claude.com/docs/en/plugins/create). Claude Code supports more component types than the other surfaces, and those docs are the full reference for anything Claude Code-only
13> * If you're deciding which pieces your plugin needs, see [Decide what to include in your plugin](/docs/connectors/building/what-to-build)
13> * If you're deciding which pieces your plugin needs, see [Decide what to include in your plugin](/docs/connectors/building/what-to-build.md)
1414
1515## Lay out the plugin folder
1616
from line 32
3232
3333Selected file
3434
35The manifest identifies the plugin to every app and to Anthropic's directory. Without any `plugin.json`, the directory accepts only a folder whose `skills/` directory holds at least one `<name>/SKILL.md`, and lists that plugin for Claude Code only, not for claude.ai or Cowork. To publish the plugin in Anthropic's directory you also need [a README and a license](/docs/plugins/pre-submission-checklist#readme-and-license); select those files in the tree to see what each needs.
35The manifest identifies the plugin to every app and to Anthropic's directory. Without any `plugin.json`, the directory accepts only a folder whose `skills/` directory holds at least one `<name>/SKILL.md`, and lists that plugin for Claude Code only, not for claude.ai or Cowork. To publish the plugin in Anthropic's directory you also need [a README and a license](/docs/plugins/pre-submission-checklist.md#readme-and-license); select those files in the tree to see what each needs.
3636
3737Its `name` is the plugin's permanent identity: people install and refer to the plugin by this value, so make it specific to your product and never change it after release. Change `displayName` when you want a different label.
3838
from line 66
66663. Reply with the report number and its approval status.
6767```
6868
69A skill folder can hold [supporting files](/docs/skills/how-to#add-resources) that are too detailed for `SKILL.md`:
69A skill folder can hold [supporting files](/docs/skills/how-to.md#add-resources) that are too detailed for `SKILL.md`:
7070
7171<ul>
7272 <li>`references/` for documentation Claude reads when needed</li>
from line 88
8888
8989A skill can include scripts in a `scripts/` folder next to `SKILL.md`.
9090
91In `SKILL.md`, refer to a script by its path under `${CLAUDE_SKILL_DIR}`, for example `python3 ${CLAUDE_SKILL_DIR}/scripts/total.py receipts.csv`. [Add scripts](/docs/skills/how-to#add-scripts) explains how each app resolves that path.
91In `SKILL.md`, refer to a script by its path under `${CLAUDE_SKILL_DIR}`, for example `python3 ${CLAUDE_SKILL_DIR}/scripts/total.py receipts.csv`. [Add scripts](/docs/skills/how-to.md#add-scripts) explains how each app resolves that path.
9292
9393This script totals the amounts in a CSV file of receipts:
9494
from line 130
130130}
131131```
132132
133A plugin loads without a README, but you need one to publish it: Anthropic's directory shows the README as the listing's description, and [validation](/docs/plugins/pre-submission-checklist#readme-and-license) blocks a submission that has none.
133A plugin loads without a README, but you need one to publish it: Anthropic's directory shows the README as the listing's description, and [validation](/docs/plugins/pre-submission-checklist.md#readme-and-license) blocks a submission that has none.
134134
135135Write at least 40 words, not counting words inside code blocks, and say what the plugin does, how to use it, and what data it sends.
136136
from line 154
154154account through mcp.example.com. It stores nothing itself.
155155```
156156
157A plugin loads without a license, but you need one to publish it: Anthropic's directory doesn't list a plugin until it has a license, and [validation](/docs/plugins/pre-submission-checklist#readme-and-license) blocks a submission that has neither a `LICENSE` file nor a `license` field.
157A plugin loads without a license, but you need one to publish it: Anthropic's directory doesn't list a plugin until it has a license, and [validation](/docs/plugins/pre-submission-checklist.md#readme-and-license) blocks a submission that has neither a `LICENSE` file nor a `license` field.
158158
159159Add a `LICENSE` file to the plugin folder, or set `license` in `plugin.json`.
160160
from line 172
172172* **A local MCP server**, one the app starts as a command, loads in Claude Code and in Cowork sessions that run on the person's computer; chat ignores it
173173* **A top-level `bin/` directory** stops claude.ai and Cowork from installing the plugin at all
174174
175[Plugin support by app](/docs/plugins/platform-support#compare-component-support-by-app) has the full table, including LSP servers, output styles, and `${user_config.*}` references, and compares where installs are stored and what an organization controls on each app.
175[Plugin support by app](/docs/plugins/platform-support.md#compare-component-support-by-app) has the full table, including LSP servers, output styles, and `${user_config.*}` references, and compares where installs are stored and what an organization controls on each app.
176176
177177### Start from an example
178178
from line 182
182182
183183## Write the plugin
184184
185The examples in this section build a plugin named `expense-reports` for a fictional finance product whose MCP server is at `mcp.example.com`. If you plan to submit the plugin to Anthropic's directory, keep the [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist) open while you write: the developer portal validates the manifest, README, license, and scripts when you submit, and building with those checks in mind means validation passes the first time.
185The examples in this section build a plugin named `expense-reports` for a fictional finance product whose MCP server is at `mcp.example.com`. If you plan to submit the plugin to Anthropic's directory, keep the [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist.md) open while you write: the developer portal validates the manifest, README, license, and scripts when you submit, and building with those checks in mind means validation passes the first time.
186186
187187### Write the manifest
188188
from line 223
223223}
224224```
225225
226On claude.ai and in Cowork, that entry is listed on the plugin's **Connectors** tab, where the user [adds or connects it](/docs/plugins/overview#bundled-connectors) and signs in through your server's OAuth flow. On Team and Enterprise plans, an Owner adds the connector for the organization, and members then connect with their own account.
226On claude.ai and in Cowork, that entry is listed on the plugin's **Connectors** tab, where the user [adds or connects it](/docs/plugins/overview.md#bundled-connectors) and signs in through your server's OAuth flow. On Team and Enterprise plans, an Owner adds the connector for the organization, and members then connect with their own account.
227227
228228Don't put API keys or other secrets in this file, because every person who installs the plugin receives its files. If your server is already listed in the directory, use the same URL here, so that someone who has both your connector and your plugin sees one set of tools rather than two.
229229
from line 243
2432434. Reply with the report number and its approval status. Don't paste the full API response.
244244```
245245
246Claude decides when to load the skill from the `description` line, so write it as the situations a user would be in, not as a summary of the file. [Create custom skills](/docs/skills/how-to) covers the frontmatter fields, resource files, scripts, and testing.
246Claude decides when to load the skill from the `description` line, so write it as the situations a user would be in, not as a summary of the file. [Create custom skills](/docs/skills/how-to.md) covers the frontmatter fields, resource files, scripts, and testing.
247247
248248## Test the plugin on each surface
249249
from line 258
258258 5. If your plugin has agents, start a Cowork task to confirm they load.
259259* **A team testing together**: push the folder to a Git repository set up as a [marketplace](https://code.claude.com/docs/en/plugins/create-marketplace), and have each tester add it from **Customize > Plugins > Add > Add marketplace** with the repository URL instead, so everyone installs the same copy
260260
261Loading the plugin shows that its parts appear. To measure whether its skills improve Claude's output, write eval cases and run [`claude plugin eval`](https://code.claude.com/docs/en/plugin-evals) in Claude Code, which grades the results and compares them against a run without the plugin. To test one skill by itself on any surface, see [Measure whether the skill improves the output](/docs/skills/how-to#measure-whether-the-skill-improves-the-output).
261Loading the plugin shows that its parts appear. To measure whether its skills improve Claude's output, write eval cases and run [`claude plugin eval`](https://code.claude.com/docs/en/plugin-evals) in Claude Code, which grades the results and compares them against a run without the plugin. To test one skill by itself on any surface, see [Measure whether the skill improves the output](/docs/skills/how-to.md#measure-whether-the-skill-improves-the-output).
262262
263Before you submit the plugin to the directory, run `claude plugin validate ./expense-reports`, then select **Validate** in the [developer portal](https://claude.ai/directory/manage). The portal runs every validation check, and [Run the checks before you submit](/docs/plugins/pre-submission-checklist#run-the-checks-before-you-submit) explains each result.
263Before you submit the plugin to the directory, run `claude plugin validate ./expense-reports`, then select **Validate** in the [developer portal](https://claude.ai/directory/manage). The portal runs every validation check, and [Run the checks before you submit](/docs/plugins/pre-submission-checklist.md#run-the-checks-before-you-submit) explains each result.
264264
265265When something is missing on one surface and present on another, check it against [Check what each app loads](#check-what-each-app-loads) before debugging. An agent that never appears in chat, or a local server that chat doesn't start, is the surface behaving as designed.
266266
from line 272
272272
273273Once the plugin works, you can distribute it through your organization, your own marketplace, or the directory:
274274
275* [Manage plugins for your organization](/docs/plugins/admin): on Team and Enterprise plans, an Owner can make the plugin available or installed by default for members
275* [Manage plugins for your organization](/docs/plugins/admin.md): on Team and Enterprise plans, an Owner can make the plugin available or installed by default for members
276276* [Create a marketplace](https://code.claude.com/docs/en/plugins/create-marketplace): list the plugin in a Git repository's `marketplace.json`, which anyone you give the URL to can add from **Customize > Plugins** or the Claude Code command line
277* [Publish to the directory](/docs/directory/publish): submit the plugin from the [developer portal](https://claude.ai/directory/manage) so people on Pro, Max, Team, and Enterprise plans can find and add it on claude.ai and in Cowork, and use it in Claude Code. Anyone on a paid plan can submit without applying to a partner program first; on Team and Enterprise, an Owner submits
277* [Publish to the directory](/docs/directory/publish.md): submit the plugin from the [developer portal](https://claude.ai/directory/manage) so people on Pro, Max, Team, and Enterprise plans can find and add it on claude.ai and in Cowork, and use it in Claude Code. Anyone on a paid plan can submit without applying to a partner program first; on Team and Enterprise, an Owner submits
278278
plugins/create-with-claude Changed · +11 / -11 lines
from line 2
22
33> Make a plugin for your own workflow from claude.ai or the desktop app without writing files: choose Create with Claude and answer Claude's questions.
44
5A [plugin](/docs/plugins/overview) packages skills, commands, and connectors. You can make one for yourself in claude.ai or the Claude desktop app without writing files: from [**Customize > Plugins**](https://claude.ai/customize/plugins), select **Add > Create with Claude**, describe what you need, and save the plugin Claude produces to your account.
5A [plugin](/docs/plugins/overview.md) packages skills, commands, and connectors. You can make one for yourself in claude.ai or the Claude desktop app without writing files: from [**Customize > Plugins**](https://claude.ai/customize/plugins), select **Add > Create with Claude**, describe what you need, and save the plugin Claude produces to your account.
66
7A plugin you create this way is for you. It lives on your account, and on a Team or Enterprise plan you can [share it](/docs/plugins/share) with specific people or your whole organization from its page in Customize. It isn't a directory listing; if you later want that, see [Submit a plugin you created with Claude](#submit-a-plugin-you-created-with-claude) at the end of this page.
7A plugin you create this way is for you. It lives on your account, and on a Team or Enterprise plan you can [share it](/docs/plugins/share.md) with specific people or your whole organization from its page in Customize. It isn't a directory listing; if you later want that, see [Submit a plugin you created with Claude](#submit-a-plugin-you-created-with-claude) at the end of this page.
88
99> [!NOTE]
1010>
11> * If you'd rather write the files yourself, see [Plugin structure and testing](/docs/plugins/build)
12> * If you want to make a plugin available to everyone in your organization, see [Publish a plugin to your organization](/docs/plugins/share#publish-a-plugin-to-your-organization)
11> * If you'd rather write the files yourself, see [Plugin structure and testing](/docs/plugins/build.md)
12> * If you want to make a plugin available to everyone in your organization, see [Publish a plugin to your organization](/docs/plugins/share.md#publish-a-plugin-to-your-organization)
1313
1414To begin, [start a new plugin from the Add menu](#start-from-the-add-menu), [describe it to Claude and save it](#describe-and-save-the-plugin), then [review the plugin Claude made](#review-what-claude-made).
1515
from line 32
3232* **Create with Claude**: start a new conversation, or a new Cowork task in the desktop app, with a request to create a plugin already filled in for you to send. Choose this when you can describe the task you want the plugin to handle but don't want to write skill files
3333* **Create a plugin**: fill in a form with the plugin's name and what it helps with, then write its skills, commands, and connectors in an editor. Choose this when you already know what each piece should say
3434
35If neither item appears in the **Add** menu, plugin creation isn't available on your account. Your organization can turn it off, and so can your IT department's configuration of the desktop app. [Manage plugins for your organization](/docs/plugins/admin#control-what-members-add-themselves) covers the organization setting.
35If neither item appears in the **Add** menu, plugin creation isn't available on your account. Your organization can turn it off, and so can your IT department's configuration of the desktop app. [Manage plugins for your organization](/docs/plugins/admin.md#control-what-members-add-themselves) covers the organization setting.
3636
3737### Describe and save the plugin
3838
from line 79
7979* **Disable it**: turn off the plugin's toggle
8080* **Remove it**: open its menu and select **Remove** to delete it from your account
8181
82To give the plugin to other people in your organization, see [Share a plugin with teammates](/docs/plugins/share). It covers sharing with specific people and publishing to your organization's library, both on Team and Enterprise plans.
82To give the plugin to other people in your organization, see [Share a plugin with teammates](/docs/plugins/share.md). It covers sharing with specific people and publishing to your organization's library, both on Team and Enterprise plans.
8383
8484## Submit a plugin you created with Claude
8585
from line 91
9191
9292**2. Check the manifest and README**
9393
94Unzip the folder and compare `plugin.json` with [Write the manifest](/docs/plugins/build#write-the-manifest). Claude may include fields the manifest doesn't use and leaves placeholders such as your name for you to fill in. If you have Claude Code installed, run `claude plugin validate` on the folder, as [Check the plugin on your machine](/docs/plugins/pre-submission-checklist#check-the-plugin-on-your-machine-optional) describes.
94Unzip the folder and compare `plugin.json` with [Write the manifest](/docs/plugins/build.md#write-the-manifest). Claude may include fields the manifest doesn't use and leaves placeholders such as your name for you to fill in. If you have Claude Code installed, run `claude plugin validate` on the folder, as [Check the plugin on your machine](/docs/plugins/pre-submission-checklist.md#check-the-plugin-on-your-machine-optional) describes.
9595
9696**3. Push and submit**
9797
98Push the folder to a public GitHub repository, then follow [Submit a plugin](/docs/plugins/submit).
98Push the folder to a public GitHub repository, then follow [Submit a plugin](/docs/plugins/submit.md).
9999
100100## Next steps
101101
102* [Plugins](/docs/plugins/overview#manage-installed-plugins): turn off, remove, or update plugins on your account
103* [Plugin feature support across platforms](/docs/plugins/platform-support): check which of the plugin's components work in chat, Cowork, and Claude Code
104* [Share a plugin with teammates](/docs/plugins/share): give the plugin to specific people or your organization
102* [Plugins](/docs/plugins/overview.md#manage-installed-plugins): turn off, remove, or update plugins on your account
103* [Plugin feature support across platforms](/docs/plugins/platform-support.md): check which of the plugin's components work in chat, Cowork, and Claude Code
104* [Share a plugin with teammates](/docs/plugins/share.md): give the plugin to specific people or your organization
105105
plugins/org-rollout Changed · +9 / -9 lines
from line 11
1111
1212> [!NOTE]
1313>
14> * If you want to list a plugin publicly, see [Publish to the directory](/docs/directory/publish)
15> * If you haven't built the plugin yet, see [Build your first plugin](/docs/plugins/quickstart) and [Plugin structure and testing](/docs/plugins/build)
14> * If you want to list a plugin publicly, see [Publish to the directory](/docs/directory/publish.md)
15> * If you haven't built the plugin yet, see [Build your first plugin](/docs/plugins/quickstart.md) and [Plugin structure and testing](/docs/plugins/build.md)
1616
1717## Choose a rollout route
1818
from line 24
2424| Where you set it up | [**Organization settings > Plugins & skills**](https://claude.ai/admin-settings/skills?tab=inventory) | Server-managed settings, an MDM policy, or a `managed-settings.json` file |
2525| What you set | An availability for each plugin, such as **Installed by default** or **Required** | `extraKnownMarketplaces` to register your marketplace and `enabledPlugins` to install plugins from it |
2626| Access to your repository | Members need none. Organization sync reads the repository through your organization's GitHub or GitLab connection. | Each machine fetches the marketplace itself. For a private Git repository, it uses the Git credentials already on that machine. |
27| Which components load | Depends on the surface. See [Plugin feature support across platforms](/docs/plugins/platform-support). | Every component |
28| Full setup steps | [Manage plugins for your organization](/docs/plugins/admin) | [Manage Claude Code plugins for your organization](https://code.claude.com/docs/en/plugins/org) in the Claude Code docs |
27| Which components load | Depends on the surface. See [Plugin feature support across platforms](/docs/plugins/platform-support.md). | Every component |
28| Full setup steps | [Manage plugins for your organization](/docs/plugins/admin.md) | [Manage Claude Code plugins for your organization](https://code.claude.com/docs/en/plugins/org) in the Claude Code docs |
2929
3030A plugin on a member's account reaches Claude Code as a synced plugin in Cowork and in terminal sessions where the member signs in with their claude.ai account on Claude Code v2.1.273 or later. [Plugins synced from claude.ai](https://code.claude.com/docs/en/plugins/loading#synced-plugins) has the sign-in and timing rules. For developers whose terminal sessions don't sync from a claude.ai account, use managed settings.
3131
from line 39
3939
4040**2. Check the repository against the organization sync rules**
4141
42Organization sync is stricter than Claude Code about the repository's visibility and about which plugin source types it accepts, and it rejects a plugin with a top-level `bin/` directory. Check [the plugin sources that organization sync accepts](/docs/plugins/org-sync#plugin-sources-that-organization-sync-accepts) before you continue.
42Organization sync is stricter than Claude Code about the repository's visibility and about which plugin source types it accepts, and it rejects a plugin with a top-level `bin/` directory. Check [the plugin sources that organization sync accepts](/docs/plugins/org-sync.md#plugin-sources-that-organization-sync-accepts) before you continue.
4343
4444**3. Sync the repository from organization settings**
4545
46In [**Organization settings > Plugins & skills**](https://claude.ai/admin-settings/skills?tab=inventory), add the repository as [Add your own plugins](/docs/plugins/admin#add-your-own-plugins) describes, then [set each plugin's availability](/docs/plugins/admin#set-availability).
46In [**Organization settings > Plugins & skills**](https://claude.ai/admin-settings/skills?tab=inventory), add the repository as [Add your own plugins](/docs/plugins/admin.md#add-your-own-plugins) describes, then [set each plugin's availability](/docs/plugins/admin.md#set-availability).
4747
4848**4. Register the same marketplace in managed settings**
4949
from line 60
6060
6161## Build one repository for both audiences
6262
63One plugin folder can serve both audiences, because each surface skips the components it doesn't load. Hooks and agents load in Cowork and Claude Code and not in chat, and a local MCP server doesn't run in chat. Check each component you include against [Plugin feature support across platforms](/docs/plugins/platform-support) before you promise a behavior to people who only use chat.
63One plugin folder can serve both audiences, because each surface skips the components it doesn't load. Hooks and agents load in Cowork and Claude Code and not in chat, and a local MCP server doesn't run in chat. Check each component you include against [Plugin feature support across platforms](/docs/plugins/platform-support.md) before you promise a behavior to people who only use chat.
6464
6565## Update a plugin you've rolled out
6666
from line 92
9292
9393## Next steps
9494
95* [Sync your organization's plugins from a repository](/docs/plugins/org-sync): check your repository and plugin sources against the rules organization sync enforces
96* [Manage plugins for your organization](/docs/plugins/admin): set availability for everyone or for user groups, and control what members can add themselves
95* [Sync your organization's plugins from a repository](/docs/plugins/org-sync.md): check your repository and plugin sources against the rules organization sync enforces
96* [Manage plugins for your organization](/docs/plugins/admin.md): set availability for everyone or for user groups, and control what members can add themselves
9797* [Manage Claude Code plugins for your organization](https://code.claude.com/docs/en/plugins/org): set the managed-settings keys and deliver them to developers' machines
9898
plugins/org-sync Changed · +4 / -4 lines
from line 8
88
99> [!NOTE]
1010>
11> * If you're choosing who gets each plugin once the repository syncs, see [Manage plugins for your organization](/docs/plugins/admin#set-availability)
11> * If you're choosing who gets each plugin once the repository syncs, see [Manage plugins for your organization](/docs/plugins/admin.md#set-availability)
1212> * If you're writing the `marketplace.json` file, see [Create a marketplace](https://code.claude.com/docs/en/plugins/create-marketplace) in the Claude Code docs
1313
1414To get started, check [how organization sync gets access to your repository](#give-organization-sync-access-to-your-repository) for your Git host, then check your `marketplace.json` against [the plugin sources that organization sync accepts](#plugin-sources-that-organization-sync-accepts).
from line 71
7171
7272**2. Sync from GitLab**
7373
74In [**Organization settings > Plugins & skills**](https://claude.ai/admin-settings/skills?tab=inventory), select **Add**, then **Sync from GitLab**, as [Add your own plugins](/docs/plugins/admin#add-your-own-plugins) describes. When you add it, enter the project's HTTPS URL, such as `https://gitlab.example.com/platform/claude-plugins`.
74In [**Organization settings > Plugins & skills**](https://claude.ai/admin-settings/skills?tab=inventory), select **Add**, then **Sync from GitLab**, as [Add your own plugins](/docs/plugins/admin.md#add-your-own-plugins) describes. When you add it, enter the project's HTTPS URL, such as `https://gitlab.example.com/platform/claude-plugins`.
7575
7676Organization sync reads the project's default branch. If you turn on **Sync automatically**, only pushes to the default branch start a sync.
7777
from line 104
104104
105105## Next steps
106106
107* [Manage plugins for your organization](/docs/plugins/admin#set-availability): set each synced plugin to available, installed by default, or required
108* [Roll out a plugin to your whole organization](/docs/plugins/org-rollout): reach members in claude.ai and Cowork and developers in the Claude Code command line with one plugin
107* [Manage plugins for your organization](/docs/plugins/admin.md#set-availability): set each synced plugin to available, installed by default, or required
108* [Roll out a plugin to your whole organization](/docs/plugins/org-rollout.md): reach members in claude.ai and Cowork and developers in the Claude Code command line with one plugin
109109* [Create a marketplace](https://code.claude.com/docs/en/plugins/create-marketplace) in the Claude Code docs: write the `marketplace.json` file that lists your plugins
110110
plugins/overview Changed · +18 / -18 lines
from line 2
22
33> Add plugins to Claude: what a plugin adds, where to find and install one, and where it's available across chat, Cowork, and Claude Code.
44
5A plugin packages [skills](/docs/skills/overview), [MCP connectors](/docs/connectors/getting-started), and [commands and agents](#compare-what-each-plugin-component-adds) so you can add them to Claude as one unit. You add plugins from [**Customize > Plugins**](https://claude.ai/customize/plugins) in claude.ai or the Claude desktop app; **Customize** is the page that holds your connectors, skills, and plugins. Each plugin is saved to your account, so it's also available in Cowork and Claude Code without installing it again.
5A plugin packages [skills](/docs/skills/overview.md), [MCP connectors](/docs/connectors/getting-started.md), and [commands and agents](#compare-what-each-plugin-component-adds) so you can add them to Claude as one unit. You add plugins from [**Customize > Plugins**](https://claude.ai/customize/plugins) in claude.ai or the Claude desktop app; **Customize** is the page that holds your connectors, skills, and plugins. Each plugin is saved to your account, so it's also available in Cowork and Claude Code without installing it again.
66
77This page is for people using plugins in claude.ai, the Claude desktop app, and Cowork.
88
99> [!NOTE]
1010>
11> * If you want to build a plugin or submit one to the directory, see [Plugin structure and testing](/docs/plugins/build) and [Publish to the directory](/docs/directory/publish)
11> * If you want to build a plugin or submit one to the directory, see [Plugin structure and testing](/docs/plugins/build.md) and [Publish to the directory](/docs/directory/publish.md)
1212> * If you install and manage plugins from the Claude Code command line, see [Install plugins](https://code.claude.com/docs/en/plugins/install) in the Claude Code docs
13> * If you have a `.mcpb` file to install into the Claude desktop app, see [Install a local connector in the desktop app](/docs/connectors/custom/add-unlisted#install-a-local-connector-in-the-desktop-app)
13> * If you have a `.mcpb` file to install into the Claude desktop app, see [Install a local connector in the desktop app](/docs/connectors/custom/add-unlisted.md#install-a-local-connector-in-the-desktop-app)
1414
1515To get started, [find and add a plugin](#find-and-add-a-plugin), then see [how to use it in each app](#use-a-plugin) and [where it becomes available on your account](#find-the-plugin-in-each-app).
1616
from line 26
2626* **A connector marked Runs in each session**: runs a program on your computer
2727* **A mod**, in Claude Code only: code that runs inside Claude Code and can change what it does and shows. See [Decide whether to trust a mod](https://code.claude.com/docs/en/plugins/mods/overview#decide-whether-to-trust-a-mod)
2828
29Anthropic reviews plugins listed in the directory: every version gets automated validation and a security scan, and a person reviews a new listing before it goes live, as [Prepare for review](/docs/directory/publish#prepare-for-review) describes. That review doesn't cover a plugin you add from a marketplace URL or upload yourself, so add those only from sources you trust.
29Anthropic reviews plugins listed in the directory: every version gets automated validation and a security scan, and a person reviews a new listing before it goes live, as [Prepare for review](/docs/directory/publish.md#prepare-for-review) describes. That review doesn't cover a plugin you add from a marketplace URL or upload yourself, so add those only from sources you trust.
3030
31On Team and Enterprise plans, an Owner controls which sources members see and whether they can add their own, as [Manage plugins for your organization](/docs/plugins/admin) covers.
31On Team and Enterprise plans, an Owner controls which sources members see and whether they can add their own, as [Manage plugins for your organization](/docs/plugins/admin.md) covers.
3232
3333### Find and add a plugin
3434
from line 35
3535On the **Plugins** page, you add a plugin from **Discover**, **Add > Add marketplace**, or **Add > Upload plugin**:
3636
3737* **Discover**: see the plugins available to you. These are the ones in Anthropic's default marketplaces, the directory, and any your organization provides. Select one to read what it contains, then select **Add**. The directory's plugins appear on Pro, Max, Team, and Enterprise plans. On Team and Enterprise plans, an Owner chooses which Anthropic sources the organization includes, so you see the directory only if your organization keeps it
38* **Add > Add marketplace**: add a [plugin marketplace](https://code.claude.com/docs/en/plugins/create-marketplace), a Git repository that contains plugins, so its plugins appear alongside the others. Enter a repository URL such as `https://github.com/your-org/your-plugins` or the `owner/repo` shorthand for GitHub. For a marketplace you add yourself, GitHub and GitHub Enterprise repositories work, and so do public GitLab and Bitbucket repositories. To add a private GitHub repository, connect your GitHub account when the dialog asks and give the Claude GitHub App access to the repository. If access is missing, the dialog says so and shows **Connect GitHub** or **Install the Claude GitHub App**. Plugins your organization distributes from its own repositories come through [organization settings](/docs/plugins/admin#add-your-own-plugins) instead
38* **Add > Add marketplace**: add a [plugin marketplace](https://code.claude.com/docs/en/plugins/create-marketplace), a Git repository that contains plugins, so its plugins appear alongside the others. Enter a repository URL such as `https://github.com/your-org/your-plugins` or the `owner/repo` shorthand for GitHub. For a marketplace you add yourself, GitHub and GitHub Enterprise repositories work, and so do public GitLab and Bitbucket repositories. To add a private GitHub repository, connect your GitHub account when the dialog asks and give the Claude GitHub App access to the repository. If access is missing, the dialog says so and shows **Connect GitHub** or **Install the Claude GitHub App**. Plugins your organization distributes from its own repositories come through [organization settings](/docs/plugins/admin.md#add-your-own-plugins) instead
3939* **Add > Upload plugin**: upload a plugin you have as a folder on your computer, as a `.zip` or `.plugin` file. Zip either the plugin folder itself or its contents; both work as long as the archive holds one `.claude-plugin/plugin.json`
4040
41[Plugin feature support across platforms](/docs/plugins/platform-support#compare-installation-sync-and-admin-controls) lists the size and count limits.
41[Plugin feature support across platforms](/docs/plugins/platform-support.md#compare-installation-sync-and-admin-controls) lists the size and count limits.
4242
4343### Find the plugin in each app
4444
from line 69
6969* **Installed by default**: the plugin is already in your list under **Customize > Plugins** without you adding it, and you can turn it off
7070* **Required**: the plugin is installed and always on. It's marked **This plugin is required by your organization**, and you can't turn it off or remove it
7171
72[Manage plugins for your organization](/docs/plugins/admin) covers those controls.
72[Manage plugins for your organization](/docs/plugins/admin.md) covers those controls.
7373
7474## Use a plugin
7575
from line 102
102102| MCP connectors | Access to an external tool or data source. You add or connect each one from the plugin's **Connectors** tab. | Chat, Cowork, Claude Code |
103103| Agents | Specialists Claude can delegate part of a task to | Cowork, Claude Code |
104104
105[Plugin feature support across platforms](/docs/plugins/platform-support) lists every component by app.
105[Plugin feature support across platforms](/docs/plugins/platform-support.md) lists every component by app.
106106
107107## Manage installed plugins
108108
from line 114
114114 2. Open its menu.
115115 3. Select **Remove**.
116116* **Disconnect a bundled connector**: open the plugin's **Connectors** tab, or **Customize > Connectors**, and disconnect it. The plugin stays installed
117* **Use a plugin someone shared with you**: a plugin that another member of your organization shares with you appears under **Shared with you** on the **Your plugins** tab, turned off. Open it and turn on its toggle to use it. It stays in your list for as long as that person shares it. To share one of your own, see [Share a plugin with specific people](/docs/plugins/share#share-a-plugin-with-specific-people)
118* **Get updates**: plugins from a marketplace or the directory update from their source. After a new version syncs from the source, you get it on your account automatically, with nothing to accept. Claude Code's own marketplaces have a separate auto-update setting. To pull the latest from a marketplace you added, select **Check for updates**. For a marketplace you added yourself from github.com, you can also turn on **Sync automatically**. Marketplaces your organization syncs have their own setting, which [Sync your organization's plugins from a repository](/docs/plugins/org-sync) covers
117* **Use a plugin someone shared with you**: a plugin that another member of your organization shares with you appears under **Shared with you** on the **Your plugins** tab, turned off. Open it and turn on its toggle to use it. It stays in your list for as long as that person shares it. To share one of your own, see [Share a plugin with specific people](/docs/plugins/share.md#share-a-plugin-with-specific-people)
118* **Get updates**: plugins from a marketplace or the directory update from their source. After a new version syncs from the source, you get it on your account automatically, with nothing to accept. Claude Code's own marketplaces have a separate auto-update setting. To pull the latest from a marketplace you added, select **Check for updates**. For a marketplace you added yourself from github.com, you can also turn on **Sync automatically**. Marketplaces your organization syncs have their own setting, which [Sync your organization's plugins from a repository](/docs/plugins/org-sync.md) covers
119119
120If a plugin you added doesn't appear where you expect it, [Install plugins in Cowork](/docs/cowork/guide/plugins) covers how the desktop app loads and updates plugins, and [Synced plugins](https://code.claude.com/docs/en/plugins/loading#synced-plugins) covers Claude Code.
120If a plugin you added doesn't appear where you expect it, [Install plugins in Cowork](/docs/cowork/guide/plugins.md) covers how the desktop app loads and updates plugins, and [Synced plugins](https://code.claude.com/docs/en/plugins/loading#synced-plugins) covers Claude Code.
121121
122122## Track plugin usage in your organization
123123
from line 129
129129
130130The plugin's **Skills** tab shows runs in the last 30 days for each skill. A skill's page in **Customize > Skills** shows the same three figures for that skill.
131131
132A plugin you made or that someone shared with you shows the organization figures only when a published copy of it is live in your organization. [Publish a plugin to your organization](/docs/plugins/share#publish-a-plugin-to-your-organization) covers publishing.
132A plugin you made or that someone shared with you shows the organization figures only when a published copy of it is live in your organization. [Publish a plugin to your organization](/docs/plugins/share.md#publish-a-plugin-to-your-organization) covers publishing.
133133
134134## Create your own plugin
135135
from line 138
138138* **Create with Claude**: start a conversation where Claude builds the plugin with you
139139* **Create a plugin**: open an editor and write its files directly
140140
141[Create a plugin with Claude](/docs/plugins/create-with-claude) covers both, and [Plugin structure and testing](/docs/plugins/build) covers building one as a folder for other people to install. On Team and Enterprise plans, you can then [share the plugin with specific people](/docs/plugins/share#share-a-plugin-with-specific-people) or [publish it to your organization](/docs/plugins/share#publish-a-plugin-to-your-organization).
141[Create a plugin with Claude](/docs/plugins/create-with-claude.md) covers both, and [Plugin structure and testing](/docs/plugins/build.md) covers building one as a folder for other people to install. On Team and Enterprise plans, you can then [share the plugin with specific people](/docs/plugins/share.md#share-a-plugin-with-specific-people) or [publish it to your organization](/docs/plugins/share.md#publish-a-plugin-to-your-organization).
142142
143You can also submit a plugin you build to Anthropic's directory, where, once it passes review, people on Pro, Max, Team, and Enterprise plans can find and add it. [Build your first plugin](/docs/plugins/quickstart) builds and tests an example plugin, and [Publish to the directory](/docs/directory/publish) covers who can submit and what review involves.
143You can also submit a plugin you build to Anthropic's directory, where, once it passes review, people on Pro, Max, Team, and Enterprise plans can find and add it. [Build your first plugin](/docs/plugins/quickstart.md) builds and tests an example plugin, and [Publish to the directory](/docs/directory/publish.md) covers who can submit and what review involves.
144144
145145## Next steps
146146
147* [Plugin feature support across platforms](/docs/plugins/platform-support): check which of a plugin's components work in chat, Cowork, the desktop app, and Claude Code
148* [Manage plugins for your organization](/docs/plugins/admin): make plugins available, installed by default, or required for members
147* [Plugin feature support across platforms](/docs/plugins/platform-support.md): check which of a plugin's components work in chat, Cowork, the desktop app, and Claude Code
148* [Manage plugins for your organization](/docs/plugins/admin.md): make plugins available, installed by default, or required for members
149149* [Install plugins](https://code.claude.com/docs/en/plugins/install) in the Claude Code docs: install and manage plugins from the command line, including the ones synced from your account
150* [Publish to the directory](/docs/directory/publish): submit a plugin to the directory, where Anthropic reviews it before it's listed
150* [Publish to the directory](/docs/directory/publish.md): submit a plugin to the directory, where Anthropic reviews it before it's listed
151151
plugins/platform-support Changed · +13 / -13 lines
from line 8
88
99> [!NOTE]
1010>
11> * If you want to install and manage plugins, see [Plugins](/docs/plugins/overview)
12> * If you're building a plugin, see [Plugin structure and testing](/docs/plugins/build)
13> * If you run Claude Desktop on your own model provider, see its [Feature matrix](/docs/third-party/claude-desktop/feature-matrix) for feature availability
14> * If you want to know where MCP Apps render, see [Add interactive UI with MCP Apps](/docs/connectors/building/mcp-apps/getting-started)
11> * If you want to install and manage plugins, see [Plugins](/docs/plugins/overview.md)
12> * If you're building a plugin, see [Plugin structure and testing](/docs/plugins/build.md)
13> * If you run Claude Desktop on your own model provider, see its [Feature matrix](/docs/third-party/claude-desktop/feature-matrix.md) for feature availability
14> * If you want to know where MCP Apps render, see [Add interactive UI with MCP Apps](/docs/connectors/building/mcp-apps/getting-started.md)
1515
1616## Compare component support by app
1717
from line 25
2525
2626| Component | Chat | Cowork | Claude Code | Notes |
2727| :- | :- | :- | :- | :- |
28| Skills (`skills/<name>/SKILL.md`) | Loads | Loads | Loads | [Create custom skills](/docs/skills/how-to) |
28| Skills (`skills/<name>/SKILL.md`) | Loads | Loads | Loads | [Create custom skills](/docs/skills/how-to.md) |
2929| Commands (`commands/*.md`) | Loads as a skill; Claude applies it when it fits | Loads; you run it by typing `/plugin-name:command` | Loads | |
3030| Agents (`agents/*.md`) | Ignored | Loads | Loads | |
3131| Hooks (`hooks/hooks.json`) | Ignored | Loads | Loads | [Hooks](https://code.claude.com/docs/en/plugins/components#hooks) in the Claude Code docs |
32| Remote MCP server, `http` or `sse` with a fixed URL | Listed on the plugin's **Connectors** tab; works once you add or connect it there | Loads; connect it from the plugin's **Connectors** tab | Loads | [Bundle a connector with its skill](/docs/plugins/build#bundle-an-mcp-connector-with-its-skill) |
32| Remote MCP server, `http` or `sse` with a fixed URL | Listed on the plugin's **Connectors** tab; works once you add or connect it there | Loads; connect it from the plugin's **Connectors** tab | Loads | [Bundle a connector with its skill](/docs/plugins/build.md#bundle-an-mcp-connector-with-its-skill) |
3333| Local MCP server, a command the app starts, including `.mcpb` bundles | Ignored | Loads when the Cowork session runs on your computer | Loads | On the web, the plugin's **Connectors** tab marks it **Runs in each session** |
3434| MCP server that references `${user_config.*}` values | Ignored when the URL contains the reference | Ignored when a referenced option has no default; Cowork doesn't prompt for values | Loads; prompts you for the values | [User configuration](https://code.claude.com/docs/en/plugins/components#user-configuration) |
3535| Executables in a top-level `bin/` directory | Can't be installed | Can't be installed | Loads | |
from line 43
4343
4444| | Chat and Cowork | Claude Code | Notes |
4545| :- | :- | :- | :- |
46| Where you add plugins | [**Customize > Plugins**](https://claude.ai/customize/plugins) in claude.ai or the desktop app | `/plugin` in a session, or `claude plugin install` | [Plugins](/docs/plugins/overview), [Install plugins](https://code.claude.com/docs/en/plugins/install) |
46| Where you add plugins | [**Customize > Plugins**](https://claude.ai/customize/plugins) in claude.ai or the desktop app | `/plugin` in a session, or `claude plugin install` | [Plugins](/docs/plugins/overview.md), [Install plugins](https://code.claude.com/docs/en/plugins/install) |
4747| What an install is attached to | Your account, for the organization you're in | The machine, at user, project, or local scope | |
4848| Which way installs travel | A plugin you install on your account also appears in Claude Code as a synced plugin at the next session start | A plugin you install from the command line stays on that machine and isn't added to your account | [Synced plugins](https://code.claude.com/docs/en/plugins/loading#synced-plugins) |
49| Hosts for a marketplace you add yourself | GitHub and GitHub Enterprise repositories, and public GitLab and Bitbucket repositories | Any Git repository, GitHub shorthand, URL, or local path | Repositories your organization syncs to distribute plugins follow [different rules](/docs/plugins/org-sync#plugin-sources-that-organization-sync-accepts) |
49| Hosts for a marketplace you add yourself | GitHub and GitHub Enterprise repositories, and public GitLab and Bitbucket repositories | Any Git repository, GitHub shorthand, URL, or local path | Repositories your organization syncs to distribute plugins follow [different rules](/docs/plugins/org-sync.md#plugin-sources-that-organization-sync-accepts) |
5050| Marketplace and plugin limits | Up to 25 marketplaces that you add yourself, counted for your account in each organization. Each plugin can contain up to 5,000 files and 200 MB, and 200 MB is also the largest file that **Upload plugin** accepts. | No account limits apply; installs are per machine | |
51| Install from a file | **Add > Upload plugin** with a zip of the folder | `claude --plugin-dir <path>` for one session | [Plugin structure and testing](/docs/plugins/build#test-the-plugin-on-each-surface) |
52| Browse the directory | **Discover** in **Customize > Plugins**, on Pro, Max, Team, and Enterprise plans. On Team and Enterprise plans, an Owner can [remove the directory as a source](/docs/plugins/admin#manage-synced-marketplaces) for the organization. | `/plugin directory`, in Claude Code v2.1.287 and later. A plugin added from the directory on claude.ai also reaches Claude Code as a synced plugin. | [Publish to the directory](/docs/directory/publish) |
53| Organization controls | An Owner sets each plugin to **Not available**, **Available to install**, **Installed by default**, or **Required** | In managed settings, an admin allowlists or blocks marketplaces and force-installs plugins | [Manage plugins for your organization](/docs/plugins/admin), and the [Claude Code equivalent](https://code.claude.com/docs/en/plugins/org) |
51| Install from a file | **Add > Upload plugin** with a zip of the folder | `claude --plugin-dir <path>` for one session | [Plugin structure and testing](/docs/plugins/build.md#test-the-plugin-on-each-surface) |
52| Browse the directory | **Discover** in **Customize > Plugins**, on Pro, Max, Team, and Enterprise plans. On Team and Enterprise plans, an Owner can [remove the directory as a source](/docs/plugins/admin.md#manage-synced-marketplaces) for the organization. | `/plugin directory`, in Claude Code v2.1.287 and later. A plugin added from the directory on claude.ai also reaches Claude Code as a synced plugin. | [Publish to the directory](/docs/directory/publish.md) |
53| Organization controls | An Owner sets each plugin to **Not available**, **Available to install**, **Installed by default**, or **Required** | In managed settings, an admin allowlists or blocks marketplaces and force-installs plugins | [Manage plugins for your organization](/docs/plugins/admin.md), and the [Claude Code equivalent](https://code.claude.com/docs/en/plugins/org) |
5454
5555## Related resources
5656
57* [Plugin structure and testing](/docs/plugins/build): lay out the plugin folder and write the manifest that all three surfaces load
57* [Plugin structure and testing](/docs/plugins/build.md): lay out the plugin folder and write the manifest that all three surfaces load
5858* [Plugin components](https://code.claude.com/docs/en/plugins/components) in the Claude Code docs: look up every component type, including the Claude Code-only ones
59* [Manage plugins for your organization](/docs/plugins/admin): as an Owner, set each plugin's availability for members
59* [Manage plugins for your organization](/docs/plugins/admin.md): as an Owner, set each plugin's availability for members
6060
plugins/pre-submission-checklist Changed · +10 / -10 lines
from line 2
22
33> Fix every finding before you submit a plugin to the Claude plugin directory: what the developer portal's validation and scan check, and what each result means.
44
5Before the [Claude plugin directory](/docs/directory/publish) lists your plugin, the developer portal checks the plugin's files at two points. Validation runs in the plugin submission form at [claude.ai/directory/manage](https://claude.ai/directory/manage) when you select the **Validate** button. A scan runs after you submit, on each new commit that the directory picks up from the branch or tag that it follows. The scan checks the plugin's files again and runs a security scan.
5Before the [Claude plugin directory](/docs/directory/publish.md) lists your plugin, the developer portal checks the plugin's files at two points. Validation runs in the plugin submission form at [claude.ai/directory/manage](https://claude.ai/directory/manage) when you select the **Validate** button. A scan runs after you submit, on each new commit that the directory picks up from the branch or tag that it follows. The scan checks the plugin's files again and runs a security scan.
66
7Use this checklist to fix problems before you [submit your plugin](/docs/plugins/submit) from the developer portal on claude.ai. The checklist covers the automated checks only, and every plugin in the directory also has to follow the [Anthropic Software Directory Policy](https://support.claude.com/en/articles/13145358-anthropic-software-directory-policy). Start by [running the checks](#run-the-checks-before-you-submit) and [reading a validation result](#read-a-validation-result). Then use the tables in [what validation and the scan check](#review-what-validation-and-the-scan-check) to fix each finding, and [prepare for the security scan](#prepare-for-the-security-scan) that runs after you submit.
7Use this checklist to fix problems before you [submit your plugin](/docs/plugins/submit.md) from the developer portal on claude.ai. The checklist covers the automated checks only, and every plugin in the directory also has to follow the [Anthropic Software Directory Policy](https://support.claude.com/en/articles/13145358-anthropic-software-directory-policy). Start by [running the checks](#run-the-checks-before-you-submit) and [reading a validation result](#read-a-validation-result). Then use the tables in [what validation and the scan check](#review-what-validation-and-the-scan-check) to fix each finding, and [prepare for the security scan](#prepare-for-the-security-scan) that runs after you submit.
88
99## Run the checks before you submit
1010
from line 14
14142. [Validate in the developer portal](#validate-in-the-developer-portal), which runs every directory check in the tables on this page
15153. [Read the result](#read-a-validation-result), fix every finding that the report marks **Blocking**, and then submit
1616
17The portal is open to the people who [can submit](/docs/directory/publish#confirm-you-can-submit-to-the-directory). If you can't submit, ask someone who can to run **Validate**.
17The portal is open to the people who [can submit](/docs/directory/publish.md#confirm-you-can-submit-to-the-directory). If you can't submit, ask someone who can to run **Validate**.
1818
1919### Check the plugin on your machine (optional)
2020
from line 42
4242
4343**3. Enter the repository**
4444
45On the **Source** step, enter the repository. [Submit your plugin](/docs/plugins/submit#submit-a-plugin) describes each field.
45On the **Source** step, enter the repository. [Submit your plugin](/docs/plugins/submit.md#submit-a-plugin) describes each field.
4646
4747**4. Validate**
4848
from line 63
6363
6464Some problems with the repository stop validation before there is a report. The submission form then shows one error, such as **Couldn’t validate that repository**, and no findings. The tables in [what validation and the scan check](#review-what-validation-and-the-scan-check) mark those checks as "Validation stops".
6565
66[Submit your plugin](/docs/plugins/submit#after-you-submit-a-plugin) explains how review and publishing proceed after you submit.
66[Submit your plugin](/docs/plugins/submit.md#after-you-submit-a-plugin) explains how review and publishing proceed after you submit.
6767
6868## Review what validation and the scan check
6969
from line 168
168168
169169The security scan looks for behavior that a plugin doesn't disclose, such as sending data elsewhere, running hidden code, or changing Claude's permission settings.
170170
171A first submission that fails the security scan is rejected, and a later version that fails can't go live. A new version that the scan flags can be held for a reviewer. The **Versions** tab on the plugin's page in the developer portal shows **Didn’t pass the security scan**, or the category of the finding, such as **Sends data to an undisclosed destination**. [Submit your plugin](/docs/plugins/submit#fix-a-failed-version) explains what to do when a version doesn't pass.
171A first submission that fails the security scan is rejected, and a later version that fails can't go live. A new version that the scan flags can be held for a reviewer. The **Versions** tab on the plugin's page in the developer portal shows **Didn’t pass the security scan**, or the category of the finding, such as **Sends data to an undisclosed destination**. [Submit your plugin](/docs/plugins/submit.md#fix-a-failed-version) explains what to do when a version doesn't pass.
172172
173173To prepare, make the plugin's behavior visible in its README and its source:
174174
from line 181
181181
182182**1. Compare output with and without the plugin**
183183
184Run the plugin's skills on real prompts and compare the output with what Claude produces without the plugin. [`claude plugin eval`](https://code.claude.com/docs/en/plugin-evals) runs that comparison for the whole plugin in Claude Code, and [Measure whether the skill improves the output](/docs/skills/how-to#measure-whether-the-skill-improves-the-output) covers one skill at a time.
184Run the plugin's skills on real prompts and compare the output with what Claude produces without the plugin. [`claude plugin eval`](https://code.claude.com/docs/en/plugin-evals) runs that comparison for the whole plugin in Claude Code, and [Measure whether the skill improves the output](/docs/skills/how-to.md#measure-whether-the-skill-improves-the-output) covers one skill at a time.
185185
186186**2. Load the plugin on each surface**
187187
188Load the plugin on each surface your users will use, as [Test the plugin on each surface](/docs/plugins/build#test-the-plugin-on-each-surface) describes.
188Load the plugin on each surface your users will use, as [Test the plugin on each surface](/docs/plugins/build.md#test-the-plugin-on-each-surface) describes.
189189
190190## Next steps
191191
192* [Submit your plugin](/docs/plugins/submit): enter the repository in the developer portal, follow the review, and publish
193* [Publish to the directory](/docs/directory/publish): confirm your plan and role can submit, and see what Anthropic's review involves
192* [Submit your plugin](/docs/plugins/submit.md): enter the repository in the developer portal, follow the review, and publish
193* [Publish to the directory](/docs/directory/publish.md): confirm your plan and role can submit, and see what Anthropic's review involves
194194
plugins/quickstart Changed · +16 / -16 lines
from line 2
22
33> Build a plugin with one skill and an optional MCP connector, test it in Claude Code, validate it, and push it to GitHub, ready to submit your own.
44
5By the end of this quickstart, you have a working example plugin with one skill and, optionally, one remote MCP connector, tested in Claude Code, validated, and pushed to GitHub, which is everything a plugin needs before you submit it to [Anthropic's directory](/docs/directory/publish). A plugin is a folder that packages skills, MCP connectors, commands, and agents, in any combination, so that people add them together.
5By the end of this quickstart, you have a working example plugin with one skill and, optionally, one remote MCP connector, tested in Claude Code, validated, and pushed to GitHub, which is everything a plugin needs before you submit it to [Anthropic's directory](/docs/directory/publish.md). A plugin is a folder that packages skills, MCP connectors, commands, and agents, in any combination, so that people add them together.
66
77This quickstart is for developers who have Claude Code installed and want to learn the plugin format by building one. You can follow it with a product that has a remote MCP server, or with only a skill.
88
99> [!NOTE]
1010>
11> * If you want to make a plugin from a conversation without writing files, see [Create a plugin with Claude](/docs/plugins/create-with-claude)
12> * If you want to distribute a plugin only inside your own organization, see [Roll out a plugin to your whole organization](/docs/plugins/org-rollout)
13> * If you want to look up the folder layout, the manifest fields, or what each surface loads, see [Plugin structure and testing](/docs/plugins/build)
11> * If you want to make a plugin from a conversation without writing files, see [Create a plugin with Claude](/docs/plugins/create-with-claude.md)
12> * If you want to distribute a plugin only inside your own organization, see [Roll out a plugin to your whole organization](/docs/plugins/org-rollout.md)
13> * If you want to look up the folder layout, the manifest fields, or what each surface loads, see [Plugin structure and testing](/docs/plugins/build.md)
1414
1515## Before you create the plugin
1616
from line 40
4040}
4141```
4242
43People install and refer to the plugin by its `name`. Use lowercase words joined by hyphens, make the name specific to your product, and never change it after release. [Manifest and plugin name](/docs/plugins/pre-submission-checklist#manifest-and-plugin-name) lists the directory's checks on the name.
43People install and refer to the plugin by its `name`. Use lowercase words joined by hyphens, make the name specific to your product, and never change it after release. [Manifest and plugin name](/docs/plugins/pre-submission-checklist.md#manifest-and-plugin-name) lists the directory's checks on the name.
4444
4545**2. Add a skill**
4646
from line 60
60604. Reply with the report number and its approval status. Don't paste the full API response.
6161```
6262
63Claude decides when to load the skill from the `description` line, so write it as the situations a user would be in. [Create custom skills](/docs/skills/how-to) covers the frontmatter fields, resource files, scripts, and testing.
63Claude decides when to load the skill from the `description` line, so write it as the situations a user would be in. [Create custom skills](/docs/skills/how-to.md) covers the frontmatter fields, resource files, scripts, and testing.
6464
6565**3. Add an MCP connector**
6666
from line 79
7979
8080There is no server at `mcp.example.com`, so this example connector fails to connect when you test the plugin. Replace the URL with your own server's, or leave `.mcp.json` out.
8181
82Don't put API keys or other secrets in this file, because every person who installs the plugin receives its files. On claude.ai and in Cowork, the entry is listed on the plugin's **Connectors** tab, where the user [adds or connects it](/docs/plugins/overview#bundled-connectors) and signs in through your server's OAuth flow. On Team and Enterprise plans, an Owner adds the connector for the organization, and members then connect with their own account.
82Don't put API keys or other secrets in this file, because every person who installs the plugin receives its files. On claude.ai and in Cowork, the entry is listed on the plugin's **Connectors** tab, where the user [adds or connects it](/docs/plugins/overview.md#bundled-connectors) and signs in through your server's OAuth flow. On Team and Enterprise plans, an Owner adds the connector for the organization, and members then connect with their own account.
8383
8484**4. Write the README**
8585
86Create `README.md` in the plugin folder with at least 40 words. Words inside code blocks don't count. Say what the plugin does, how to use it, and what data it sends. The directory shows your README as the listing's description, and [README and license](/docs/plugins/pre-submission-checklist#readme-and-license) lists what validation checks.
86Create `README.md` in the plugin folder with at least 40 words. Words inside code blocks don't count. Say what the plugin does, how to use it, and what data it sends. The directory shows your README as the listing's description, and [README and license](/docs/plugins/pre-submission-checklist.md#readme-and-license) lists what validation checks.
8787
8888This README covers those three points for the example plugin:
8989
from line 121
121121
122122To try the skill, describe one of the situations that its `description` line names, such as a receipt you want reimbursed. Claude decides when to load the skill from that line.
123123
124To test the plugin on claude.ai and in Cowork as well, see [Test the plugin on each surface](/docs/plugins/build#test-the-plugin-on-each-surface).
124To test the plugin on claude.ai and in Cowork as well, see [Test the plugin on each surface](/docs/plugins/build.md#test-the-plugin-on-each-surface).
125125
126126## Validate the plugin
127127
from line 139
139139* **Validate in the developer portal**: the **Validate** button in the [developer portal](https://claude.ai/directory/manage) runs every validation check. The directory's own checks, such as the README, license, and name checks, run there and not in the command
140140* **The scan after you submit**: checks the plugin's files again and runs a security scan
141141
142The [Plugin pre-submission checklist](/docs/plugins/pre-submission-checklist) lists every check and what each result means.
142The [Plugin pre-submission checklist](/docs/plugins/pre-submission-checklist.md) lists every check and what each result means.
143143
144144## Push the plugin to GitHub
145145
from line 171
171171
172172The `expense-reports` plugin you built on this page is a small demonstration of the format, so there's no reason to submit it: the directory is for plugins other people will use, and it refuses a name another organization has already listed. Use the same steps to build your own plugin, with its own name, skills, and connector.
173173
174When your plugin validates and is pushed to a public GitHub repository, submit it from the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage): select **Submit new**, choose **Plugin bundle**, and follow [Submit a plugin](/docs/plugins/submit#submit-a-plugin) for each field and for what happens after you submit. If your plugin points at a remote MCP server you run, [submit that server as a connector too](/docs/directory/publish#submit-your-plugin-and-your-mcp-server-as-a-connector). [Who can submit to the directory](/docs/directory/publish#confirm-you-can-submit-to-the-directory) has the plan and role requirements.
174When your plugin validates and is pushed to a public GitHub repository, submit it from the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage): select **Submit new**, choose **Plugin bundle**, and follow [Submit a plugin](/docs/plugins/submit.md#submit-a-plugin) for each field and for what happens after you submit. If your plugin points at a remote MCP server you run, [submit that server as a connector too](/docs/directory/publish.md#submit-your-plugin-and-your-mcp-server-as-a-connector). [Who can submit to the directory](/docs/directory/publish.md#confirm-you-can-submit-to-the-directory) has the plan and role requirements.
175175
176176## Next steps
177177
178* [Plugin structure and testing](/docs/plugins/build): look up the folder layout and manifest fields, and test on claude.ai and in Cowork
179* [Plugin pre-submission checklist](/docs/plugins/pre-submission-checklist): fix each validation and scan finding before you submit
180* [Submit a plugin](/docs/plugins/submit): fill in each portal field, then publish and update the listed plugin
181* [Track your submission](/docs/directory/submission-status): check what your submission's status means and who acts next
182* [Plugin feature support across platforms](/docs/plugins/platform-support): check which of the plugin's components load in chat, Cowork, and Claude Code
178* [Plugin structure and testing](/docs/plugins/build.md): look up the folder layout and manifest fields, and test on claude.ai and in Cowork
179* [Plugin pre-submission checklist](/docs/plugins/pre-submission-checklist.md): fix each validation and scan finding before you submit
180* [Submit a plugin](/docs/plugins/submit.md): fill in each portal field, then publish and update the listed plugin
181* [Track your submission](/docs/directory/submission-status.md): check what your submission's status means and who acts next
182* [Plugin feature support across platforms](/docs/plugins/platform-support.md): check which of the plugin's components load in chat, Cowork, and Claude Code
183183* [`claude plugin eval`](https://code.claude.com/docs/en/plugin-evals): write eval cases and compare the plugin's results against a run without the plugin
184184
plugins/share Changed · +10 / -10 lines
from line 2
22
33> Share a plugin you made with specific people in your Team or Enterprise organization, or publish it to your organization's library.
44
5On a Team or Enterprise plan, you can get a [plugin](/docs/plugins/overview) you made to other people in your organization. You share it with specific people yourself, or you publish it to your organization's library, where an Owner decides who can find and install it.
5On a Team or Enterprise plan, you can get a [plugin](/docs/plugins/overview.md) you made to other people in your organization. You share it with specific people yourself, or you publish it to your organization's library, where an Owner decides who can find and install it.
66
7This page is for someone on a Team or Enterprise plan who created or uploaded a plugin, for example with [Create a plugin with Claude](/docs/plugins/create-with-claude).
7This page is for someone on a Team or Enterprise plan who created or uploaded a plugin, for example with [Create a plugin with Claude](/docs/plugins/create-with-claude.md).
88
99> [!NOTE]
1010>
11> * If you're an Owner reviewing what members publish, see [Manage plugins for your organization](/docs/plugins/admin)
12> * If you want a wider audience than your organization, see [Plugin structure and testing](/docs/plugins/build) and [Publish to the directory](/docs/directory/publish)
11> * If you're an Owner reviewing what members publish, see [Manage plugins for your organization](/docs/plugins/admin.md)
12> * If you want a wider audience than your organization, see [Plugin structure and testing](/docs/plugins/build.md) and [Publish to the directory](/docs/directory/publish.md)
1313
1414To give the plugin to people you name, go to [Share a plugin with specific people](#share-a-plugin-with-specific-people). To reach the whole organization, go to [Publish a plugin to your organization](#publish-a-plugin-to-your-organization).
1515
from line 24
2424* **Share**: specific people in your organization get the plugin from you directly
2525* **Publish to org**: the plugin goes to your organization's library, where an Owner decides who can find and install it. See [Publish a plugin to your organization](#publish-a-plugin-to-your-organization)
2626* **The plugin file**: someone in another organization or on a personal plan adds the `.plugin` file or a zip of the plugin with **Add > Upload plugin**. It becomes a separate plugin on their account
27* **A marketplace or the directory**: for a wider audience, put the plugin in a Git repository as a folder, as [Plugin structure and testing](/docs/plugins/build) describes, then share it through [your own marketplace](https://code.claude.com/docs/en/plugins/create-marketplace) or [the directory](/docs/directory/publish)
27* **A marketplace or the directory**: for a wider audience, put the plugin in a Git repository as a folder, as [Plugin structure and testing](/docs/plugins/build.md) describes, then share it through [your own marketplace](https://code.claude.com/docs/en/plugins/create-marketplace) or [the directory](/docs/directory/publish.md)
2828
2929### Share the plugin
3030
from line 47
4747* **What they do**: open the plugin and turn on its toggle. When the plugin includes something that runs on their computer, such as a local MCP server or a hook, Claude asks them to confirm first
4848* **What they can change**: nothing in the plugin. They can view it, turn it on or off, and use it. It stays in their list for as long as you share it
4949* **Your later edits**: people who turned the plugin on get your new version wherever they use Claude, including chat on the web
50* **Connectors**: your connector sign-ins aren't shared. Each person adds or connects the plugin's connectors with their own account, as [Bundled connectors](/docs/plugins/overview#bundled-connectors) describes
50* **Connectors**: your connector sign-ins aren't shared. Each person adds or connects the plugin's connectors with their own account, as [Bundled connectors](/docs/plugins/overview.md#bundled-connectors) describes
5151* **The link**: **Copy link** in the share dialog copies a link to the plugin's page. Only people you've shared the plugin with can open it
5252
5353### Stop sharing a plugin
from line 75
7575* **Open**: the plugin is published without review. Where your organization scans what members publish, it goes live after the security scan passes
7676* **Off**: your organization doesn't accept plugins from members, and **Publish to org** doesn't appear on your plugin
7777
78On a Team plan, the **Publishing** setting is **Open** unless an Owner has changed it. [Review plugins that members publish](/docs/plugins/admin#review-plugins-that-members-publish) lists the default for each plan.
78On a Team plan, the **Publishing** setting is **Open** unless an Owner has changed it. [Review plugins that members publish](/docs/plugins/admin.md#review-plugins-that-members-publish) lists the default for each plan.
7979
8080You see the result on the plugin's own page, which shows whether the submission is waiting for review, denied, or published:
8181
from line 85
8585
8686## Next steps
8787
88* [Create a plugin with Claude](/docs/plugins/create-with-claude): make a plugin in claude.ai or the desktop app with Claude's help
89* [Manage plugins for your organization](/docs/plugins/admin): if you're an Owner, turn sharing and publishing on or off for members
90* [Plugin structure and testing](/docs/plugins/build): write the plugin as a folder for a marketplace or the directory
88* [Create a plugin with Claude](/docs/plugins/create-with-claude.md): make a plugin in claude.ai or the desktop app with Claude's help
89* [Manage plugins for your organization](/docs/plugins/admin.md): if you're an Owner, turn sharing and publishing on or off for members
90* [Plugin structure and testing](/docs/plugins/build.md): write the plugin as a folder for a marketplace or the directory
9191
plugins/submit Changed · +19 / -19 lines
from line 2
22
33> Submit a plugin from a GitHub repository to Anthropic's directory through the developer portal, follow its review, publish it, and release updates.
44
5To list a plugin in [Anthropic's directory](/docs/directory/publish), you submit it from a GitHub repository through the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage). Anthropic checks each version before it can go live, and people can then add the plugin from claude.ai and use it in chat, Cowork, and Claude Code.
5To list a plugin in [Anthropic's directory](/docs/directory/publish.md), you submit it from a GitHub repository through the developer portal at [claude.ai/directory/manage](https://claude.ai/directory/manage). Anthropic checks each version before it can go live, and people can then add the plugin from claude.ai and use it in chat, Cowork, and Claude Code.
66
7Use this page if your plugin is already in a GitHub repository and you want it listed. If the plugin references a remote MCP server you run, submit that server as an MCP connector too, as [Submit your plugin, and your MCP server as a connector](/docs/directory/publish#submit-your-plugin-and-your-mcp-server-as-a-connector) explains.
7Use this page if your plugin is already in a GitHub repository and you want it listed. If the plugin references a remote MCP server you run, submit that server as an MCP connector too, as [Submit your plugin, and your MCP server as a connector](/docs/directory/publish.md#submit-your-plugin-and-your-mcp-server-as-a-connector) explains.
88
99> [!NOTE]
1010>
11> * To build the plugin first, see [Plugin structure and testing](/docs/plugins/build)
12> * To share it without a public listing, see [Share a plugin with teammates](/docs/plugins/share) or [Roll out a plugin to your whole organization](/docs/plugins/org-rollout)
13> * If you submitted through the earlier Claude Console form, see [Move an earlier submission to the developer portal](/docs/directory/publish#move-an-earlier-submission-to-the-developer-portal)
11> * To build the plugin first, see [Plugin structure and testing](/docs/plugins/build.md)
12> * To share it without a public listing, see [Share a plugin with teammates](/docs/plugins/share.md) or [Roll out a plugin to your whole organization](/docs/plugins/org-rollout.md)
13> * If you submitted through the earlier Claude Console form, see [Move an earlier submission to the developer portal](/docs/directory/publish.md#move-an-earlier-submission-to-the-developer-portal)
1414
1515## Before you submit a plugin
1616
from line 17
1717You need the following to submit from the developer portal on claude.ai:
1818
1919* **A GitHub repository that holds the plugin, and your GitHub account connected on claude.ai.** The directory reads plugins from repositories on github.com. The portal checks that your connected GitHub account can push to the repository, so [connect it first](#connect-your-github-account). The repository can stay private while you validate and submit, and must be public before the listing goes live. See [Submit from a private repository](#submit-from-a-private-repository)
20* **A plan and role that can submit.** See [who can submit to the directory](/docs/directory/publish#confirm-you-can-submit-to-the-directory)
20* **A plan and role that can submit.** See [who can submit to the directory](/docs/directory/publish.md#confirm-you-can-submit-to-the-directory)
2121
2222Every plugin in the directory must comply with the [Anthropic Software Directory Terms](https://support.claude.com/en/articles/13145338-anthropic-software-directory-terms) and the [Anthropic Software Directory Policy](https://support.claude.com/en/articles/13145358-anthropic-software-directory-policy).
2323
24Before you open the portal, work through the [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist). It covers what the directory's checks look for in `plugin.json`, the README, the license, and the rest of the plugin folder. In your terminal, from the folder that contains the plugin folder, run `claude plugin validate ./<plugin-folder>` first to catch formatting and structure problems. The portal's **Validate** step runs more checks than the command does.
24Before you open the portal, work through the [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist.md). It covers what the directory's checks look for in `plugin.json`, the README, the license, and the rest of the plugin folder. In your terminal, from the folder that contains the plugin folder, run `claude plugin validate ./<plugin-folder>` first to catch formatting and structure problems. The portal's **Validate** step runs more checks than the command does.
2525
2626## Submit a plugin
2727
from line 34
3434
3535> [!NOTE]
3636>
37> The other option, **MCP connector**, submits one remote MCP server as its own connector listing. If your plugin references an MCP server you built and you haven't submitted that server yet, submit it separately with **MCP connector** by following [Submit your connector](/docs/connectors/building/submission). [Submit your plugin, and your MCP server as a connector](/docs/directory/publish#submit-your-plugin-and-your-mcp-server-as-a-connector) explains why you submit both.
37> The other option, **MCP connector**, submits one remote MCP server as its own connector listing. If your plugin references an MCP server you built and you haven't submitted that server yet, submit it separately with **MCP connector** by following [Submit your connector](/docs/connectors/building/submission.md). [Submit your plugin, and your MCP server as a connector](/docs/directory/publish.md#submit-your-plugin-and-your-mcp-server-as-a-connector) explains why you submit both.
3838
3939**2. Enter the source and validate**
4040
from line 50
50502. If a finding blocks submission, fix it in the repository and push the fix.
51513. Validate again.
5252
53The [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist) explains what each kind of finding means.
53The [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist.md) explains what each kind of finding means.
5454
5555A validation result applies to one commit. If you push to the branch after validating, validate again before you continue.
5656
from line 87
8787
8888Your organization can have one submission for each repository and folder. To continue an existing submission, open it from **Submissions** in the developer portal instead of creating a second one.
8989
90If another organization has already submitted the same repository and folder, the portal refuses **Submit for review** with **Already submitted by another organization**. If your organization owns the repository, email `[email protected]`. If the earlier submission is one you made through the Claude Console form, see [Move an earlier submission to the developer portal](/docs/directory/publish#move-an-earlier-submission-to-the-developer-portal).
90If another organization has already submitted the same repository and folder, the portal refuses **Submit for review** with **Already submitted by another organization**. If your organization owns the repository, email `[email protected]`. If the earlier submission is one you made through the Claude Console form, see [Move an earlier submission to the developer portal](/docs/directory/publish.md#move-an-earlier-submission-to-the-developer-portal).
9191
9292### Connect your GitHub account
9393
from line 114
114114
115115## After you submit a plugin
116116
117When you select **Submit for review**, the directory scans the newest commit on the tracked branch or tag. Each scan validates the plugin against the directory's rules again and runs a security scan. [Prepare for the security scan](/docs/plugins/pre-submission-checklist#prepare-for-the-security-scan) describes what the security scan looks for.
117When you select **Submit for review**, the directory scans the newest commit on the tracked branch or tag. Each scan validates the plugin against the directory's rules again and runs a security scan. [Prepare for the security scan](/docs/plugins/pre-submission-checklist.md#prepare-for-the-security-scan) describes what the security scan looks for.
118118
119To follow the submission, open the plugin from **Submissions** in the [developer portal](https://claude.ai/directory/manage). The **Versions** tab on the plugin's page lists each scanned commit with the result of its checks. When the newest version isn't live, the plugin's page says why. [Track your directory submission](/docs/directory/submission-status#plugin-bundle-statuses) explains what each status in the portal means and who acts next.
119To follow the submission, open the plugin from **Submissions** in the [developer portal](https://claude.ai/directory/manage). The **Versions** tab on the plugin's page lists each scanned commit with the result of its checks. When the newest version isn't live, the plugin's page says why. [Track your directory submission](/docs/directory/submission-status.md#plugin-bundle-statuses) explains what each status in the portal means and who acts next.
120120
121121A finished scan leaves the version in one of these states:
122122
123123* **Passes every check:** the version can be published, as described in [Publish a passing version](#publish-a-passing-version)
124* **Held for a reviewer:** an Anthropic reviewer reads the version, and it can go live only after the reviewer clears it. The [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist) lists the findings that hold a version
124* **Held for a reviewer:** an Anthropic reviewer reads the version, and it can go live only after the reviewer clears it. The [plugin pre-submission checklist](/docs/plugins/pre-submission-checklist.md) lists the findings that hold a version
125125* **Doesn't pass:** the portal lists the rules that the version breaks. For a failed security scan, the portal shows the category of the finding when the scan recorded one, such as **Sends data to an undisclosed destination**
126126
127127If the directory can't fetch a commit, or a scan ends without a result, the plugin's page says whether the directory retries on its own or whether something in the repository needs fixing. After any fix, select **Check for new commits** on the plugin's page to run the scan again.
from line 148
148148
149149You set auto-publish with the **Auto-publish passing versions** toggle on the **Review and submit** step. After you submit, change it with the **Publish new versions automatically** toggle on the plugin's **Settings** tab. Auto-publish doesn't apply while a reviewer publishes each version.
150150
151If a submission is stuck, [Contact Anthropic about a submission](/docs/directory/submission-status#contact-anthropic-about-a-submission) gives the channel for a plugin.
151If a submission is stuck, [Contact Anthropic about a submission](/docs/directory/submission-status.md#contact-anthropic-about-a-submission) gives the channel for a plugin.
152152
153153## Update a published plugin
154154
from line 185
185185
186186## Next steps
187187
188* [Track your submission](/docs/directory/submission-status#plugin-bundle-statuses): check what the status next to your plugin's name means and who acts next
189* [Plugin pre-submission checklist](/docs/plugins/pre-submission-checklist): fix each validation and scan finding
190* [After publishing](/docs/connectors/building/after-publishing): update your plugin and listing, and delist
191* [Track published plugin usage](/docs/connectors/building/after-publishing#track-published-plugin-usage): see installs, versions, runs, and error rates on the plugin's **Usage** tab
192* [Manage your directory listing](/docs/connectors/building/managing-your-listing): for an MCP connector, check health and usage metrics and edit the listing
188* [Track your submission](/docs/directory/submission-status.md#plugin-bundle-statuses): check what the status next to your plugin's name means and who acts next
189* [Plugin pre-submission checklist](/docs/plugins/pre-submission-checklist.md): fix each validation and scan finding
190* [After publishing](/docs/connectors/building/after-publishing.md): update your plugin and listing, and delist
191* [Track published plugin usage](/docs/connectors/building/after-publishing.md#track-published-plugin-usage): see installs, versions, runs, and error rates on the plugin's **Usage** tab
192* [Manage your directory listing](/docs/connectors/building/managing-your-listing.md): for an MCP connector, check health and usage metrics and edit the listing
193193
skills/how-to Changed · +6 / -6 lines
from line 17
1717A skill isn't the right tool for everything:
1818
1919* **A one-off task**: describe what you want in the conversation instead
20* **Live data from another service**: that's what an [MCP connector](/docs/connectors/getting-started) provides. A skill can tell Claude how to use a connector, but it can't reach the service itself
20* **Live data from another service**: that's what an [MCP connector](/docs/connectors/getting-started.md) provides. A skill can tell Claude how to use a connector, but it can't reach the service itself
2121* **Instructions for every conversation**: put those in your [personal preferences or project instructions](https://support.claude.com/en/articles/10185728-understanding-claude-s-personalization-features) rather than a skill, which loads only when a task matches
2222
2323To start, write down the task in one sentence and what a good result looks like. That sentence becomes the skill's `description`, and the rest becomes the instructions. If you'd rather have Claude draft the skill with you, ask it to use the [skill-creator skill](#measure-whether-the-skill-improves-the-output), then edit what it produces.
from line 199
199199
200200In Claude Code, running a script is a Bash tool call, so it needs your permission. When you test with [`claude -p`](https://code.claude.com/docs/en/headless), which can't stop to ask, allow the script on the command line, for example `--allowedTools "Bash(python3 /path/to/my-plugin/skills/render-chart/scripts/render.py *)"`, using the script's absolute path. Claude runs the script by its absolute path, and `Bash()` rules match the whole command line, so a rule that names the exact path approves only that script; a wildcard before the path would approve more than you intend.
201201
202Don't put API keys, passwords, or other credentials in a script or anywhere else in the skill: everyone you share the skill with receives its files. When a script needs to reach an outside service, have Claude use a [connector](/docs/connectors/getting-started) for that service instead, so each person signs in with their own account.
202Don't put API keys, passwords, or other credentials in a script or anywhere else in the skill: everyone you share the skill with receives its files. When a script needs to reach an outside service, have Claude use a [connector](/docs/connectors/getting-started.md) for that service instead, so each person signs in with their own account.
203203
204204## Package your skill
205205
from line 328
328328
329329After your skill works, you can give it to other people on its own or as part of a plugin. People you share it with should be able to read what it does, so keep the instructions and scripts plain enough to review.
330330
331* **Share or publish one skill**: on Team and Enterprise plans, open the skill from **Customize > Skills** and use the same **Share** and **Publish to org** controls that a plugin has. They work the way [sharing a plugin with specific people](/docs/plugins/share#share-a-plugin-with-specific-people) and [publishing a plugin to your organization](/docs/plugins/share#publish-a-plugin-to-your-organization) describe
332* **Package skills and connectors together**: when you want several skills, or a skill plus the connector it uses, installed together, [build a plugin](/docs/plugins/build) that contains them
331* **Share or publish one skill**: on Team and Enterprise plans, open the skill from **Customize > Skills** and use the same **Share** and **Publish to org** controls that a plugin has. They work the way [sharing a plugin with specific people](/docs/plugins/share.md#share-a-plugin-with-specific-people) and [publishing a plugin to your organization](/docs/plugins/share.md#publish-a-plugin-to-your-organization) describe
332* **Package skills and connectors together**: when you want several skills, or a skill plus the connector it uses, installed together, [build a plugin](/docs/plugins/build.md) that contains them
333333
334334## Next steps
335335
336336* [Skills in Claude Code](https://code.claude.com/docs/en/skills): create and test skills from the Claude Code CLI, including the `/skills` manager
337* [Plugin structure and testing](/docs/plugins/build): package your skill as a plugin so other people can install it
338* [Submit your plugin](/docs/plugins/submit): submit the plugin to the directory, where Anthropic reviews it before it's listed
337* [Plugin structure and testing](/docs/plugins/build.md): package your skill as a plugin so other people can install it
338* [Submit your plugin](/docs/plugins/submit.md): submit the plugin to the directory, where Anthropic reviews it before it's listed
339339