Key takeaways
- A connect-invite link lets a client self-serve account authorization via OAuth.
- No password is ever shared, and no screen-sharing call is needed.
- The client can revoke access later from their own platform settings, independent of you.
How a connect-invite link works
You send the client a single link. They open it, and for each platform they need to connect, they’re taken to that platform’s own official login page to authorize access — the same flow as any third-party app connection they’ve done before.
Why this beats a screen-share or password share
- No password is ever typed into your tool or shared with your team
- The client can complete it on their own time, without a scheduled call
- Access is scoped to what the connection grants — not full account control
- The client can revoke access later from their own account settings, at any time
What happens after they connect
Once connected, the account lands in a workspace scoped to that client, ready for the rest of onboarding — roles, approvals, and the first test post. See manage client access to social accounts for the broader access-management picture.
onboardingconnect inviteagency operationssecurity
FAQ
- Does a connect-invite link ever ask for a password?
- No. It directs the client to each platform’s own official login page, where they authorize access directly — you never see or handle a password.
- Can a client revoke access after connecting via an invite link?
- Yes, at any time, from their own platform account settings — this is independent of the tool you use, since the connection is a standard OAuth grant.
- Does the client need to be on a call to use a connect-invite link?
- No — it’s designed to be self-serve. The client can open the link and connect their accounts on their own time.