Skip to main content
Deutsch (Deutschland) Español Français Hebrew (Israel) Italiano Português

Troubleshooting LinearB login and access

Ciara Clements
Updated

Use this guide when someone cannot sign in, signs in but sees an empty or incomplete product, or used to have access and no longer does.

Work through the checks in order. Most access issues are resolved in Settings → Users & Teams by an organization Admin.

Quick checklist

1. Cannot complete sign-in

Confirm the sign-in method

Users must use the same method your organization expects:

  • Email / password
  • Sign in with GitHub, Google, or Azure
  • Enterprise SSO (SAML), if configured

If colleagues use SSO but a user tries GitHub (or the reverse), sign-in can fail or land in the wrong place.

Errors on a Microsoft / Entra / Azure page

Screens such as “Need admin approval” or AADSTS… errors are shown by Microsoft Entra ID, not LinearB. They appear before LinearB receives a successful login.

Ask an Entra admin to:

  1. Approve / grant admin consent for the LinearB application, or
  2. Assign the affected users to the LinearB enterprise app

Then have the user try again in a private/incognito window.

For SSO setup and enforcement, see Authentication – Start Here and Enforcing SSO.

Still failing at the LinearB login page

  • Confirm the email matches the address used in LinearB (including aliases).
  • Try a private/incognito browser window (clears stale sessions).
  • If SSO is enabled, use your company SSO entry point rather than a personal Microsoft/Google account.

2. Can sign in but cannot see data

Signing in only proves authentication succeeded. Visibility inside LinearB depends on role and team scopes.Screenshot 2026-08-07 at 10.24.36 AM.png

If a user has no team scopes (or scopes that don’t include the teams they need), the product can look empty: no teams, blank dashboards, greyed-out metrics, or “nothing to show” even though the organization has data.

What team scopes control

Team scopes define which teams’ data the user is allowed to see (Pulse, Metrics, dashboards, teams views, and related reporting).

  • Team membership = which teams the person belongs to as a contributor / member.
  • Team scopes = which teams they are allowed to view in the UI.

A user can be a member of a team and still see little or nothing if scopes were never assigned. Conversely, scopes without membership still control what they can open in reporting views.

Assigning All Teams (when appropriate) gives organization-wide visibility for that user’s role.

How to assign or fix scopes (Admin)

  1. Go to Settings → Users & Teams (Users view).
  2. Find the user (search by email).
  3. Open the user and set:
    • Role — Admin, Editor, Viewer, or Basic
    • Team scopes — one or more teams, or All Teams
    • Team membership — as needed for contributor attribution
  4. Save.
  5. Ask the user to refresh or sign out and back in.

Note: Inviting someone or adding them as a git/PM contributor does not automatically grant UI visibility. Platform access requires a LinearB user with a role and team scopes.

Step-by-step: Adding a New User. Role capabilities: User Role Permissions Matrix.

3. Check Deleted users

If someone previously had access, or an Admin cannot find them under active Users, check Deleted users before creating a duplicate account.

Why this matters

Deleting a user in LinearB:

  • Removes them from teams
  • Removes platform access
  • Hides them from the main Users list

They may still appear under Deleted users, where an Admin can restore them instead of inviting again (which can cause duplicate or confusing identity states).

How to check and restore (Admin)

  1. Go to Settings → Users & Teams.
  2. Click Show deleted users (Admin permissions required).
    Screenshot 2026-08-07 at 10.25.45 AM.png
  3. Search for the user’s email.Screenshot 2026-08-07 at 10.25.55 AM.png
  4. If listed, use the ⋮ menu → Restore User.Screenshot 2026-08-07 at 10.26.54 AM.png
  5. Re-confirm role, team scopes, and team membership after restore — these may need to be set again.
  6. Ask the user to sign in again.

Full steps: Managing Deleted Users · View deleted users · Restore a deleted user.

4. Wrong organization

If your company uses multiple LinearB organizations (multi-org / sub-orgs):

  • After sign-in, confirm the user is in the intended organization (organization switcher).
  • Access, roles, and team scopes are per organization. Access in one org does not grant access in another.
  • Enterprise SSO is typically configured for a single organization; multi-org SSO has limitations; confirm with Support if you are unsure.

5. SSO and SCIM gotchas

When SSO is enabled:

  • Users are often provisioned in LinearB only after their first successful SSO login.
  • Until then, they may not appear in Settings → Users & Teams, and Admins may be unable to set roles or scopes.
  • Ask new users to complete one successful SSO login, then an Admin assigns role and team scopes.

SCIM: role and team scope attributes must be mapped correctly in your IdP. A provisioned user with no scope mapping can authenticate but still see an empty product.

See SSO Gotchas and SSO user provisioning behavior.

6. When to contact Support

Open a ticket (or reply on an existing one) if:

  • Sign-in fails after IdP admin consent / correct method is confirmed
  • The user is not in Deleted users, has scopes set, and still sees no data
  • Restore user is unavailable and you need help recovering access
  • You suspect a multi-org or SSO configuration issue

Please include:

  1. User email
  2. Organization name
  3. Sign-in method (SSO, Azure, GitHub, etc.)
  4. Exact error text or screenshot
  5. Whether the user appears under Users and/or Deleted users
  6. Current role and team scopes (screenshot from Users & Teams helps)

How we work tickets: How to Engage with Support.

Related to

Related articles