Skip to main content
Open Settings → Community sign-in → Configure and select Website sign-in to manage keys. Keys authorize only that project’s website integration.

​
Create a key

Choose Generate server key, then copy the full key immediately. It is shown only once. Store it on your website’s backend as FEEDBACKLOOP_SSO_KEY. If you lose it, create a replacement and revoke the unused key.
Key changes take effect immediately. Cancelling the sign-in policy dialog does not undo a generated or revoked key. Never put a key in browser code, a public repository or a support message.

​
Rotate without interrupting users

You can have at most two active keys.
  1. Generate a replacement while the existing key remains active.
  2. Deploy the replacement to your website server.
  3. Verify a new website sign-in journey.
  4. Revoke the old key.
Revocation signs out community sessions created with that key. Deploy and verify the replacement before revoking. If both slots are occupied, identify the unused key before revoking anything.

​
After a downgrade

Saved keys remain. Free owners can view key metadata and revoke keys, but generating keys requires Pro. Website participation remains paused until Pro is restored or the policy changes to Feedback Loop account sign-in. If a key may have been exposed, revoke it, deploy a replacement and review your own server logs without copying credentials into support messages. See the website integration guide.