Bring your audience in with auto login and SSO

When you finish, people who are already signed in to your site or app are signed in to Genuin too, so they can follow, post, buy, and be recognized across every placement without a second login. Your part takes about 30 minutes of developer time.

Before you begin

• A live hub (see Launch your first community: your owned-and-operated space); if you embedded a feed on your own site, the loader from that snippet.
• A server that can sign a short-lived token.

How it works

Your server mints a signed token for the signed-in user; the SDK exchanges it for a Genuin session. Genuin never sees your password or your user table, and the token carries only the fields you choose to share. This is the same mechanism that builds a unified identity across onsite and offsite later (see Unified identity: auto login, SSO, and the ID graph), and it is designed so that viewing history stays under your control (see Privacy and VPPA: the two-channel data flow).

What Octo does

1. Octo detects your sign-in system from the crawl and the SDK (your own session, Auth0, Okta, Firebase, Shopify, or a custom provider) and proposes the auto login setup: the provider, the claims to pass (a hashed email for the ID graph where you allow it), and the consent behaviour.
2. Octo generates the signing key, writes the token-exchange snippet for your stack, and, where your repository is connected, opens the change for review with a test that exercises it in sandbox.
3. Octo proposes which communities become member-only once sign-in works.

What you approve

• The provider and the claims. Remove any claim you do not want to share.
• The code change (your Developer approves the pull request; nothing deploys without it).
• Choose Approve auto login. Signed-in viewers are recognized on every placement with no change to the embed snippet.

Make Octo smarter

• Tell Octo how your sessions work ("we use a cookie named x on web and a JWT in the app") under Brand → Context → Technical notes; it writes the exchange against your real setup.

Need help? Octo is available 24/7 in BCC and on every page of these docs. Ask it in plain language; when the answer needs a person, Octo brings the right account manager, developer, or Ops engineer into the same thread and stays on it until it is solved. Every Business Account owner has this, on every plan (see 24/7 Octo-enabled support: how Octo brings in account managers, developers, and Ops).

What you get

• Signed-in viewers on every placement, with no change to the embed snippet.
• Member-only communities (see Upload your videos or connect your social profile) that now work.
• The foundation of your ID graph for commerce and attribution (see Audience segments: onsite, offsite, and offline signals and Attribution: closed-loop commerce and conversion forecasts).