Access and navigation

Trailhead mobile is invitation-only. The signed-in identity is resolved against an organization, field profile, lodge access, roles, and server-issued capabilities. Those records—not the device—determine which tabs and actions appear.

Activate an invited account

For a new Trailhead user:

1. Open the latest invitation link from Operations.
2. Confirm that the invitation names the expected organization and guide role.
3. Register with the email address that received the invitation.
4. Create the password and enter the six-digit email verification code when prompted.
5. Let Trailhead finish linking the invitation before closing the app.
6. After the app opens, go to Profile and confirm the name, role, lodge access, and onboarding status.

If an account already exists, open the invitation while signed in to the matching account so Trailhead can finish linking it. The same identity may accept invitations from more than one Trailhead organization; accepting the new invitation does not replace an existing membership. Select Use another account when the active identity does not match the invitation.

Sign in to an existing account

Enter the account email and password. If second-factor verification is required, enter the code sent by email. Trailhead lists only organizations where the identity has active membership and Trailhead access. One eligible organization opens automatically; when several are available, select the organization before Trailhead resolves the mobile profile and authorized work view.

If sign-in succeeds but the field profile cannot be resolved, the app shows a blocked or error state. Retry refresh once, then sign out and confirm the invitation email, organization membership, guide or assistant record, and lodge access with Operations. Signing out and back in refreshes the session; it cannot grant a missing capability.

Confirm the active context

Before opening an assignment or submitting work, confirm:

• Active organization — Every profile, lodge, assignment, account, notification, and pending offline action belongs to this organization.
• Identity and role — Profile can show Guide, Coordinator, Assistant, Manager, or another field role.
• Work view — Company access opens the Company CIS view by default. A person authorized for both Company and Guide work can switch between those real backend views.
• Lodge access — Guide and Assistant field roles receive organization-wide lodge navigation. A selected lodge changes context; it does not grant access to another organization's data or permission to mutate unassigned work.
• Active lodge — Field screens use the selected lodge as their working context.
• Onboarding status — Not started, In progress, Submitted for review, Update requested, or Verified.
• Visible actions — Tabs and buttons appear only when the current profile has the required capability.

Use the organization selector before the lodge selector when the identity belongs to more than one organization. Switching organization clears the prior organization's selected lodge, cached profile, queries, notifications, assistant context, and visible offline work. It never reveals why a guide is unavailable in another organization.

When more than one lodge is available inside the active organization, use the lodge pill in a field-screen header to change the active lodge. Recheck the page after switching: assignments, Beats, Signals, Account context, and other lodge-scoped data can change with it.

Use the mobile navigation

The bottom navigation adapts to the profile:

Use the profile icon in a field-screen header to open Profile. Profile owns personal details, documents, Seasonal Kit, Guide account, appearance, settings, and sign out. Use the back arrow to return within a workflow. The Map uses a close action because it is presented as a focused full-screen workspace.

A hidden tab or action is an access boundary, not a loading defect. Do not borrow another person's account to expose it; ask Operations to correct the role, organization membership, assignment, or capability. For Guide and Assistant roles, a missing lodge is a profile/context defect rather than a request for one-lodge membership.

Manage location access

The location icon in a field header shows whether foreground location is available. Select it to request permission or open device settings when permission was denied. Location access supports map orientation; it does not change lodge access, approve entry to private property, or replace the instructions on an Access record.

Recover safely

• Loading does not finish — Confirm connectivity, then retry the profile request.
• Wrong organization — Switch organization before opening records or retrying pending work; never continue from a screen cached for another organization.
• Wrong lodge — Switch the active lodge where the header allows it and reopen the record.
• Expected tab is missing — Confirm role, lodge access, onboarding state, and required capability with Operations.
• Blocked profile — Use Retry once; if the state remains, sign out and ask Operations to verify the field record.
• Wrong identity — Sign out from Profile, then sign in with the invited account.
• Invite cannot be used — Open the latest invite or request a replacement; do not repeatedly register new accounts.

Next: complete guide onboarding.