Skip to content

Update "How to get started" on the secure linking update - #1880

Merged
Rachel-Codat merged 3 commits into
mainfrom
update/secure-linking-getting-started
Aug 13, 2026
Merged

Update "How to get started" on the secure linking update#1880
Rachel-Codat merged 3 commits into
mainfrom
update/secure-linking-getting-started

Conversation

@Rachel-Codat

@Rachel-Codat Rachel-Codat commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Refreshes the How to get started section of updates/250110-secure-linking.

Why

Two things were out of date:

  • Enabling one-time Link URLs no longer requires contacting an account manager - there is a self-serve One-time Link URLs toggle in the Portal under Settings > Auth flow > Link > Onboarding.
  • The Link SDK path was missing the CORS step. Without registering the domain via Set CORS settings, the access token cannot be used from the customer site.

What changed

  • Section restructured into numbered steps, matching the format used in the manage connections / reconnect update.
  • Step 1 points at the Portal toggle and its exact settings tab.
  • The Link SDK subsection now spells out three steps in setup order: register the domain via Set CORS settings, get a company access token, then pass it via the accessToken prop. CORS comes first because it is a prerequisite for the token to work.
  • Hosted Link and build-your-own caveats are unchanged.

Out of scope

docs/auth-flow/authorize-hosted-link.md (lines 88 and 127) still says "contact your account manager" for the same feature. Worth a follow-up, but left alone here to keep this PR to the page that was asked about.

🤖 Generated with Claude Code

Rachel-Codat and others added 2 commits August 13, 2026 09:53
One-time Link URLs are now self-serve via the Portal toggle rather than
an account manager request, and the Link SDK path needs CORS settings.
Restructures the section into numbered steps to match the format used by
the manage connections / reconnect update.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Registering the domain is a prerequisite for the access token to work,
so it reads better before the token steps rather than after.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Aug 13, 2026

Copy link
Copy Markdown
PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-08-13 09:33 UTC

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Link check results:

[]

@Rachel-Codat
Rachel-Codat marked this pull request as ready for review August 13, 2026 09:06
@Rachel-Codat
Rachel-Codat enabled auto-merge August 13, 2026 09:27
@Rachel-Codat
Rachel-Codat merged commit 2a3483b into main Aug 13, 2026
8 of 10 checks passed
@Rachel-Codat
Rachel-Codat deleted the update/secure-linking-getting-started branch August 13, 2026 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants