docs(sendgrid): correct capability matrix — add teammate + teammate_invitation resource types#30
Conversation
…nvitation The published capability table listed Accounts/Scopes/Subusers, but baton_capabilities.json declares four resource types: scope, subuser, teammate, teammate_invitation. Replace the ambiguous 'Accounts' row with explicit 'Teammates' and 'Teammate invitations' rows so the table matches the connector's actual synced resource types. Found during CXH-1896 containerization QA validation. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Connector PR Review: docs(sendgrid): correct capability matrix — add teammate + teammate_invitation resource typesBlocking Issues: 0 | Suggestions: 0 | Threads Resolved: 0 Review SummaryThis is a docs-only change to Security IssuesNone found. Correctness IssuesNone found. SuggestionsNone. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Closing as superseded. c1-dev-bot mirrored this fix into the central docs repo as ConductorOne/docs#374, which is the source that publishes to conductorone.com/docs and refines this change (Provision column kept for Scopes only; account provisioning moved to an 'Additional functionality' section). Tracking the docs fix via CXH-1986 / ConductorOne/docs#374. |
1 participant
Summary
The published capability table in
docs/connector.mdxlists Accounts / Scopes / Subusers, butbaton_capabilities.jsondeclares four resource types:scope,subuser,teammate,teammate_invitation. Theteammateandteammate_invitationtypes were not represented — the ambiguous Accounts row conflated them.This PR replaces the Accounts row with explicit Teammates and Teammate invitations rows so the table matches the connector's actual synced resource types:
Where it was found
Found during
baton-sendgridcontainerization QA validation (CXH-1896). Pre-existing documentation gap, not introduced by containerization.🤖 Generated with Claude Code