Skip to content
This repository was archived by the owner on Oct 19, 2026. It is now read-only.

docs: document workload identity in the Access Hub and connecting Claude Tag channels - #113

Open
aa-wong wants to merge 2 commits into
speakeasy-api:mainfrom
aa-wong:docs/workload-identity-claude-tag
Open

aa-wong wants to merge 2 commits into
speakeasy-api:mainfrom
aa-wong:docs/workload-identity-claude-tag

Conversation

@aa-wong

@aa-wong aa-wong commented Oct 19, 2026

Copy link
Copy Markdown

Summary

  • New guide: Connect Claude Tag channels with workload identity (docs/ai-control-plane/guides/claude-tag-workload-identity.mdx). Walks through the Claude Tag guided setup in the Access Hub, the values to enter in Claude's Connect an authorization server and Add authorization server to a bundle dialogs, testing from a channel thread, troubleshooting, and revoking access.
  • Workload identity rewritten (docs/ai-control-plane/identity/agents/workload-identity.mdx) to match the Access Hub: trusted platforms and access rules, the Catalog and Custom tabs, the register and allow-access forms, wildcard rules, and exchanging a platform token at a shared authorization server.
  • Cross-links. The Claude Tag gateway endpoint guide now points to the new guide for channels that act as a shared agent. Two lines on Authorizing agents now refer to Access Hub access rules instead of claim matchers.

Motivation

The Workload identity page described trust as claim matchers set in the agent creation wizard. In the product, trust is configured in the Access Hub: a trusted platform plus access rules matched on the token subject, each assigned to an agent. Claude Tag now has a catalog entry with a guided setup, and nothing documented it.

The existing Claude Tag guide covers per-person connectors through a gateway endpoint. The new guide covers the other model, where every channel signs in as one Speakeasy agent through Claude Tag federated access, with no stored secret.

@aa-wong
aa-wong requested a review from a team as a code owner October 19, 2026 19:53
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant