Troubleshooting: User Cannot Link WorkerB Account

In some cases, a user may be unable to link their account to WorkerB. This article explains the most common cause and how to resolve it.

Issue

A user attempts to connect their WorkerB account via Slack or Microsoft Teams but does not see any data or is unable to complete the connection process.

Cause

WorkerB can only link accounts for contributors—users who have authored at least one commit in a connected Git repository recognized by LinearB. If no commits have been made by the user, WorkerB cannot associate the user with their Git activity, and the link will fail.

This typically affects:

• New users who haven’t pushed code yet
• Product managers or designers who don’t contribute to the codebase
• Contractors or external collaborators without direct Git access

Resolution

To resolve this issue, ensure that the affected user has at least one commit recorded in the connected Git provider (e.g., GitHub, GitLab, Bitbucket). Once LinearB detects the user’s Git activity, the WorkerB account link will be successful.

If the user should not be a contributor (e.g., a PM or stakeholder), they can still receive team notifications via channel-based alerts, but will not have access to individual WorkerB alerts or features.

Note: If the issue persists after following these steps, please contact LinearB support for further assistance.

Additional Notes

• It may take several minutes after the first commit for WorkerB to recognize the new contributor.
• If the user has committed but still cannot link WorkerB, ensure their email in Git matches the one associated with their Slack or Teams account.

Related Articles

• Connecting WorkerB
• WorkerB Team Notifications