Shared channels (desks)

A desk turns a channel into a drop-box for the whole company — the canonical example is bug triage: anyone types a plain sentence, a session picks it up under the channel’s standing instruction and files a GitHub issue.

1. Admin, in the channel: /sparkyard share bugs You triage bug reports: ask for missing details, then file a GitHub issue in owner/repo with repro steps and severity. Reply with the link.
2. Admin, same channel — give the desk Claude, either way:
   • API key (recommended): /sparkyard secret ANTHROPIC_API_KEY with an organisation key from console.anthropic.com — metered, built for many users. Skippable if the workspace already has an org-wide key (/sparkyard org-key); desks fall back to it automatically.
   • Subscription account: /sparkyard connect in the channel signs a Claude account into the desk — the full sign-in ceremony, sealed desk-level, taking precedence over any org key.

Terms warning on the subscription route

A personal Claude subscription is licensed for one person, and a desk serves many — signing a personal account into a desk is account sharing under Anthropic’s terms. Use that route only with an account approved for shared or automation use; for everything else, the API-key route is the commercial, many-users path Anthropic’s terms are built for.

The desk’s GitHub identity needs no setup — it uses the deployment’s App automatically, and its installation is discovered per tenant from GitHub itself. Only when the App is installed in several orgs does the admin disambiguate with /sparkyard secret GITHUB_INSTALLATION_ID.

In a bound channel: every top-level message starts a task (no mention needed), anyone in the workspace may post — no per-person approval, because a desk carries only its own credentials — and replies from anyone continue the thread. New desks mint GitHub tokens scoped to issues only: they can file and comment on issues and cannot read or push code, enforced by GitHub itself.