Connecting Your X Account

Connect your X account to TweetX so it can sync your real analytics and publish for you. Learn how the OAuth flow works and how your tokens are protected.

Quick answer

Connect X from Settings by authorizing TweetX through X's own OAuth screen. The connection lets TweetX sync your real analytics and publish on your behalf. Your access and refresh tokens are encrypted and stored server side, never in the browser.

Why connecting X matters

X is not an account login for TweetX. You sign into TweetX with Google or an email magic link. Connecting X is a separate step that grants TweetX permission to do two things for a single workspace: read your posts and metrics so the dashboard can show your real numbers, and publish posts you write.

One X account per workspace
A workspace holds one connected X account. If you run several accounts, create a workspace for each so drafts, schedules, and analytics stay separate.

Publishing fails closed. If no X account is connected, TweetX will not fake a post or queue a phantom draft. There is no mock publish, so this step is required before your first post goes live.

Connect your account

  1. 1
    Open Settings and find Accounts
    Go to Settings, then the Accounts area, and choose to connect X.
  2. 2
    Authorize on X
    You are sent to X's own authorization screen. Sign in there if needed and approve the requested permissions. TweetX never sees your X password.
  3. 3
    Return to TweetX
    X redirects you back and the connection is stored. The workspace now shows your handle and profile photo.
  4. 4
    Let the first sync run
    On the next app load TweetX pulls in your recent posts and metrics so the dashboard reflects real data.
You need the right role
Connecting or disconnecting X requires an owner or editor role in the workspace. Viewers cannot change the connection.

What TweetX can and cannot do

The connection uses OAuth 2.0 with PKCE and asks for a narrow set of scopes: read your profile, read posts, write posts, and keep the connection alive when you are offline. That is the full extent of the access. TweetX cannot read your direct messages or change your account settings.

  • Read your profile so it can show your handle and photo.
  • Read your posts and metrics to build the dashboard.
  • Write posts when you publish or schedule them.
  • Refresh its own access quietly so you are not asked to reconnect every hour.

How your tokens are protected

After you authorize, X issues an access token and a refresh token. TweetX encrypts both with AES-256-GCM and stores them in a service role only table that the app front end can never read. Tokens never reach a Client Component, a URL, or a log.

Disconnecting is instant
You can disconnect X from Settings at any time. That removes the stored tokens and stops all syncing and publishing for that workspace.

FAQ

No. You sign into TweetX with Google or a magic link. X is only connected for publishing and analytics, not for account login.