Skip to main content
Linked accounts let Blocks identify which workspace user started a session from an external tool such as GitHub, GitLab, or Bitbucket. If you use Blocks in more than one workspace, or you use a dedicated bot account in one workspace and a personal account in another, each workspace user should link the external account they will actually use with that workspace.

​
Why this matters

When a session is created from an external tool, Blocks needs to map that event back to the correct Blocks workspace user. Linking your account ensures Blocks can:
  • Map sessions started from GitHub, GitLab, Bitbucket, and other supported tools to the correct workspace user
  • Load your user-specific settings for that session
  • Apply settings such as your custom git commit email correctly
Without a linked account, Blocks may not be able to determine which workspace user should own the session.
  1. Go to Settings → Connected Accounts
  2. Connect the external account you will use with this workspace
  3. Go to the corresponding workspace integration settings page under Settings → Integrations
  4. Click Link Account
Repeat this for each external platform you use with Blocks in that workspace. Review your linked accounts when:
  • You join a new workspace
  • You switch to a different external user account
  • Your workspace uses a dedicated bot identity for a platform integration
  • A session from GitHub, GitLab, or Bitbucket is showing up under the wrong user or missing your personal settings