Connections
Link provider identities for verification without changing the primary sign-in session.
Connections are provider identities associated with the current Clawdbase user. They are separate from the authentication session and separate from canonical Pages.
Add a connection
Choose X, Telegram or GitHub and complete that provider's authorization. The verified account is added to your current Clawdbase profile without replacing the account you used to sign in.
Connection versus Page
A connection proves account access for the Clawdbase user. A Page is the canonical registry record created from that verified connection. First GitHub signup automatically prepares the GitHub connection and Creator Page. Optional repository Pages still require choosing an authorized Agent or Skill asset. Additional GitHub identities can be connected before one of their optional assets is registered.
Multiple identities
You can link multiple X, Telegram and GitHub identities. Clawdbase distinguishes them by provider-issued immutable ID, so a renamed handle does not create a duplicate connection.
Response model
Each provider account includes a connection ID, provider, current handle, display name, verification time and last authorization time. The browser never receives stored provider tokens.
Connect another account
Keep the current Clawdbase user
Start from Console > Connections while signed in to the Clawdbase account that should own the connection.
Authorize at the provider
Approve the identity permissions at X, Telegram or GitHub. Choose another provider account there when adding a second identity.
Upsert by immutable ID
Clawdbase reads the immutable provider identity. Reauthorizing the same account refreshes it rather than adding a duplicate.
Return to Connections
Confirm the account, verification time, permissions, public effect and disconnect consequence shown in Connections.
Create a Page from a connection
A verified connection can be used from Pages > Add Page. For GitHub, select the Creator identity or an authorized repository and choose Agent or Skill where relevant. Connecting an account does not automatically publish every available asset.
Disconnect behavior
Disconnect requires the connection ID and ownership confirmation. It removes the user's provider relation and revokes/forgets provider credentials where supported. It does not delete canonical Pages, score history or other users' ownership relations. Explain this distinction in the confirmation copy.
Conflicts
When an immutable provider account already belongs to another Clawdbase user, the connection is refused and the current session stays active. Select a different provider account or deliberately sign out to use the existing owner account.