Authenticator code is rejected
Codes must come from the Wildland Exchange entry for the account shown on the verification screen.
For EveryoneHelp Center
Search 75 guides covering every major Wildland Exchange workflow.
Start with the part of the application where the problem occurred.
All guides
Codes must come from the Wildland Exchange entry for the account shown on the verification screen.
For EveryoneUse the exact verified email and current password, then distinguish password errors from verification or lockout errors.
For EveryoneUse one identity for personnel work, company management, or both. Do not create duplicate accounts.
For EveryoneOne request can contain multiple independently matched personnel, transport, resource, module, and service needs.
For Company staffing manager, Incident operationsPrivate documents require a supported type, valid ownership scope, allowed file format, and successful storage.
For EveryoneA listing needs a seller identity, category, title, description, location, condition, terms, and required disclosures.
For EveryoneA server error should include a privacy-safe request reference that identifies the failed request.
For EveryonePersonnel profiles drive role, qualification, distance, availability, and pay matching.
For PersonnelCreate the company identity first, then add personnel, resources, agreements, and operational coverage.
For Company owner, Office personnelA match requires compatible type or role, dates, status, location, availability, and any hard requirements.
For EveryoneField drafts stay on the device until connectivity returns and the server accepts the current record version.
For PersonnelA stale browser asset, interrupted request, extension, or server error can prevent the page from rendering.
For EveryoneCompany and platform tools are limited by active membership and explicit permissions.
For EveryoneA complete, privacy-safe report makes troubleshooting faster without exposing secrets or protected records.
For EveryoneThe resource picker searches canonical USFS, CAL FIRE, module, transport, and support types.
For Company equipment managerCheck the address and mail routing before creating another account.
For EveryoneEvery missing component should create an independently configurable item.
For EveryoneCreate the unit with a canonical type and unit number, then complete the type-specific pop-open configuration.
For Company equipment managerReadiness depends on current agreement details, required answers, documents, and review status.
For EveryoneInvitations are scoped, time-limited, and may already have a response.
For EveryoneAvailability must be active, within its time window, visible to the intended audience, and owned by the correct provider.
For EveryonePersonnel management requires recruiting or full-administrator permission.
For Company owner, Office personnelApplications require a signed-in personnel account, a profile, and a published job accepting applications.
For EveryoneEditing requires company-profile or full-administrator permission.
For Company memberBilling changes require an enabled provider, authorized billing role, and a completed hosted checkout or portal return.
For Company owner, Billing managerAn invitation can be accepted by email link or invitation code.
For Company owner, Office personnelA company appears only when the account has an active membership or created it.
For Company memberOffer comparison preserves component coverage, provider terms, documents, and partial acceptance.
For EveryoneCompliance status distinguishes company-reported, documented, reviewed, expired, and unverified information.
For EveryoneDispatch relationships and agency readiness profiles are configured separately from physical identity.
For EveryoneVisibility follows document ownership and explicit sharing scope.
For EveryoneNew versions are not downloadable until malware scanning reaches an allowed result.
For EveryoneBrowser download blocking, document scan status, permissions, or a missing generated file can stop output.
For EveryoneEmail can be delayed, suppressed after delivery failures, or disabled by preference even when an in-app notification exists.
For EveryoneA 403 usually means the signed-in account lacks permission or a security check rejected an old form.
For EveryoneA 404 can mean the address is wrong, the record was removed, or the record is intentionally hidden from your account.
For EveryoneFinance archives use reviewed daily records, accepted expenses, receipts, and the selected incident window.
For Company owner, Office personnelThe dashboard and menu change with your profile, company membership, and assigned permissions.
For EveryoneFuel type and minimum tank capacity should appear only for fuel support or a swamper bringing fuel support.
For EveryoneEach accepted request item creates a fulfillment record that tracks the committed component.
For EveryoneNotifications are created for supported events and can be marked read or filtered by account context.
For EveryonePacket generation depends on a supported resource, current template, required company data, and accessible documents.
For EveryoneCodes can expire, be revoked, or belong to a different signed-in email.
For EveryoneApplicants appear to authorized managers only after a valid application is submitted.
For EveryoneListing media must be supported, successfully uploaded, and associated with the correct listing.
For EveryonePrivate matching location is used for distance calculations but is not shown publicly.
For EveryoneUse the audited MFA reset process instead of creating another account.
For EveryoneRanking considers structured compatibility, distance, availability, pay, and provider constraints.
For EveryonePerson membership, company subscription, sponsorship, resource capacity, and permissions are separate controls.
For EveryoneThe mobile menu should scroll within the viewport, including full-screen browser modes.
For EveryoneA conversation must have a valid marketplace, job, need, or support context and participants you may contact.
For EveryoneA conflict means the server changed after the device saved its local draft.
For EveryonePublishing is blocked until every selected need item has its required structured fields.
For Company staffing manager, Incident operationsThe reset screen does not reveal whether an address has an account.
For EveryoneMatching uses structured roles, availability, distance, credentials, and pay preferences.
For Personnel, Company staffing managerUploads require an allowed file type, usable size, stable connection, and a record you can access.
For EveryoneRecurring schedules create occurrences only while active and within their configured window.
For EveryoneReplacing creates a version history; archiving removes the active record without erasing its audit trail.
For EveryoneUse the structured report workflow for prohibited, misleading, duplicate, or unsafe marketplace content.
For EveryoneRoles are filtered by the selected company resource and operational capability catalog.
For EveryoneCompany membership capacity controls how many active physical resources can be managed.
For Company owner, Billing managerRequest options come from the canonical catalog and the company's supported resources and templates.
For EveryoneThe confirmation should dismiss automatically or with its close control without blocking work.
For EveryoneLifecycle changes are recorded and may be blocked by assignments, ownership, or invalid transitions.
For EveryonePersonnel responses and provider offers are structured separately and can cover one or several request items.
For EveryoneOperational capability must be selected from the structured catalog to participate in matching.
For EveryoneSaved listings and search alerts require a signed-in account and active notification preferences.
For EveryoneLong idle periods or security changes can end a session and invalidate a form submission.
For EveryoneCurrent Chrome, Edge, Safari, and Firefox are expected to support the application when cookies and JavaScript are enabled.
For EveryoneToday's Assignment appears only for linked personnel with an active assignment covering the current time.
For Personnel, Incident operationsOversize transport matching uses equipment dimensions, route needs, operator status, and pilot-vehicle support.
For EveryoneThe 30-day option depends on the same browser profile and a valid protected cookie.
For EveryoneThe staging banner means the current deployment is for synthetic testing and must not contain real records.
For Company owner, Platform administratorVerification links are single-purpose and expire for security.
For EveryoneMileage, engine hours, pump hours, dimensions, staffing, and attachments must follow the selected canonical type.
For Company equipment manager