Skip to main content

Account & Sign-in

Subscriberbot uses your Burdenoff Workspaces identity. Same email, same SSO, same MFA.

What you'll learn​

  • How to sign in to the web app
  • How the CLI signs in
  • How the browser extension signs in
  • How the VS Code extension signs in
  • Where to manage your profile / MFA / sessions

Web app sign-in​

Go to app.subscriberbot.com → sign in with your Burdenoff Workspaces credentials (email + password, SSO, or magic link if your tenant allows).

CLI sign-in (subscriberbot)​

subscriberbot auth login            # OAuth2 device-code flow (interactive)
subscriberbot auth status           # show current token + workspace
subscriberbot auth token            # print platform access token
subscriberbot auth token --workspace  # print workspace-scoped token
subscriberbot auth logout           # clear local credentials

For service-to-service automation:

subscriberbot auth login --client-credentials \
  --client-id <id> --client-secret <secret>

Tokens are stored at ~/.config/subscriberbot-cli/auth.json (mode 0600). Platform tokens auto-refresh; workspace tokens are re-issued on workspace switch.

Browser extension sign-in​

Click Sign In in the popup. The extension runs the OAuth2 device-code flow with client id burdenoff_cli_subscriberbot. After approval, select a workspace. The extension stores tokens in chrome.storage.local.

VS Code extension sign-in​

Run Subscriber Bot: Login from the command palette. The extension uses the OAuth2 device-code flow with client id burdenoff_vscode_subscriberbot. Tokens are stored in VS Code SecretStorage.

Manage profile, MFA, sessions, SSO​

These are platform-level — managed through Burdenoff Workspaces:

Next steps​