docs: clarify connector vs. SSO sign-in

[mindymo]

Summary

Adds a note to the top of the connector doc distinguishing this connector (identity governance sync/provisioning for C1) from signing in to C1 via this provider's SSO. Customers have been conflating the two.

Context

The connector doc and the C1 tenant sign-in flow both involve the same identity provider, but they're unrelated setups (separate app registrations/OAuth clients in most cases). This note links to the specific SSO setup section for this provider so readers land in the right place.

[github-actions]

Connector PR Review: docs: clarify connector vs. SSO sign-in

Blocking Issues: 0 | Suggestions: 0 | Threads Resolved: 0
Criteria: Criteria status: loaded .claude/skills/ci-review.md from trusted base f6252f885525.
Review mode: full
View review run

Review Summary

Scanned the full PR diff for security and correctness: this is a documentation-only change adding a four-line <Note> callout at the top of docs/connector.mdx that distinguishes the JumpCloud connector from JumpCloud SSO sign-in to C1. No Go source, go.mod, go.sum, or config files changed, so the connector implementation, provisioning, pagination, and dependency criteria do not apply. The MDX is well-formed, and the capabilities table, credential steps, and configuration fields on the page are unaffected by the insertion; the docs link target (/product/how-to/qs-set-up-c1#authenticate-with-jumpcloud) lives outside this repository and could not be resolved from here, but nothing in the diff indicates it is wrong. No prior review findings existed and no new issues were found.

Security Issues

None found.

Correctness Issues

None found.

Suggestions

None.

[github-actions]

No blocking issues found.