Start Identity Sign In

Open our headed browser on linkedin.com for the member to sign in.

EDIT, like every identity claim: the claim puts a live browser on the workspace's one headed display and ends with a session sealed into the workspace, so a viewer must not open it. The claim is journalled like the generic identity route's, with the direct egress named.

The workspace's linkedin identity is created or re-opened (a re-login is in place), its egress is set to DIRECT, and consent is stamped, which is what opens the window. Direct on purpose: the workspace egress is a proxy pool for the workspace's integrations and refuses linkedin.com (IPRoyal answers 403 for it), and the LinkedIn proxy of the account is a Voyager matter, not the browser's. Done here rather than from the form because changing an identity's egress is an ADMIN action and connecting a channel is not.