All lessons
SupportVideo + step screenshots

Troubleshoot access, invitations and QR codes

Resolve the most common entry problems without weakening permissions or using the wrong site link.

7 minutes6 stepsCore

Watch first

Captioned walkthrough using the real TASC screen

24 sec · no sign-in required

Do the task

Follow these steps in order

0 of 60%
x

  1. Identify the person and entry path

    Confirm whether the person is an organization user, connected worker, invited worker or public QR participant.

    Troubleshoot access, invitations and QR codes step 1: Identify the person and entry path.Step 1: Identify the person and entry path

  2. Check role and permission profile

    Confirm the required module and platform surfaces are enabled for authenticated users.

    Troubleshoot access, invitations and QR codes step 2: Check role and permission profile.Step 2: Check role and permission profile

  3. Check invitation state

    Review whether the invitation is pending, accepted, declined, expired, cancelled or already connected.

    Troubleshoot access, invitations and QR codes step 3: Check invitation state.Step 3: Check invitation state

  4. Check QR scope and status

    Confirm workflow, site, shift or asset context and whether the code is still active.

    Troubleshoot access, invitations and QR codes step 4: Check QR scope and status.Step 4: Check QR scope and status

  5. Retry safely

    Use the correct resend, replacement or sign-in path rather than broadening permissions as a workaround.

    Troubleshoot access, invitations and QR codes step 5: Retry safely.Step 5: Retry safely

  6. Escalate with useful context

    Record the role, route, time, expected outcome and non-sensitive error text without sending tokens or worker information.

    Troubleshoot access, invitations and QR codes step 6: Escalate with useful context.Step 6: Escalate with useful context

Check that it worked

  • The person uses the intended entry route
  • Access is no broader than before
  • No duplicate person or asset record was created
  • The expected workflow result is visible to the authorized reviewer

If something goes wrong

Invitation and sign-in loops continue.

Check the exact email, invitation state, account state and whether the person used the matching entry route.

A QR works for one person but not another.

Compare connected, signed-in and public participant states against the workflow’s supported access model.

Before you begin and supporting details

Before you begin

  • Person type and intended role
  • Entry route and time of failure
  • Non-sensitive error text
  • Expected site, workflow and outcome

Find it in TASC

Identify person typeCheck access stateRetry safely