Back to library
SupportWorkflow capture pending

Troubleshoot access, invitations and QR codes

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

7 minutes6 stepsCoreFinal screen capture pending

Outcome

The correct entry problem is resolved without creating duplicates, weakening access or using the wrong site or QR route.

Find it in TASC

Identify person typeCheck access stateRetry safely

Before you begin

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

Interface landmarks

Labels are present in the current production source; final role-by-role screenshot capture is pending.

Identify person type
Check access state
Retry safely
1Person typeUser, worker, invitee or public participant.
2Invitation or QR statusPending, expired, inactive or incorrectly scoped.
3Role and site assignmentAuthenticated access boundary.

Decisions that matter

Classify first

Separate organization user, connected worker, invited worker and public QR participant before changing anything.

Minimum correction

Fix the invitation, assignment or QR scope directly. Do not grant broader permission as a workaround.

Safe escalation

Share role, route, time and error text—not tokens, QR secrets or worker information.

0 of 6 steps complete0%
x

Progress is saved on this device only.

  1. Step 1

    Identify the person and entry path

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

  2. Step 2

    Check role and permission profile

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

  3. Step 3

    Check invitation state

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

  4. Step 4

    Check QR scope and status

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

  5. Step 5

    Retry safely

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

  6. Step 6

    Escalate with useful context

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

Prove 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

Common problems and safe recovery

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.

What happens next

Record the cause and affected guide. Repeated issues should become a known-issue notice or a product fix, not tribal knowledge.