Equipify.ai

Troubleshooting

Technician access

Mobile access, MFA, device limits, role templates, and offline behavior—symptom-first checks that reduce “can’t log in” churn.

Quick answer

Start here

Technician access issues cluster around wrong credentials, disabled users, device/browser restrictions, missing role assignments, or branch scoping. Reset password flows first, then verify role + branch alignment before escalating to device policy.

Issues & fixes

Technician login fails on mobileCheck account status, MFA enrollment, clock skew, and whether the device is managed/blocked. Confirm they’re using the correct tenant URL and not an expired bookmark.Tap to expand steps & related links

Recommended checks

  1. Verify account active — Disabled users fail with generic errors—check admin console.
  2. Reset password / unlock — Follow your security policy; prefer invite-based reset links.
  3. Validate MFA — Re-enroll if device changed; provide backup codes if policy allows.
  4. Check device policy — MDM may block installs or clipboard access needed for SSO.
  5. Try another network — Corporate Wi‑Fi sometimes blocks auth endpoints.
Workflow: Mobile technician offline opsMobile technician opsMobile experienceSecurity
Technician can’t see assigned jobsUsually branch mismatch, assignment not saved, date filter hiding today, or the job is in a status hidden to that role. Confirm assignment saved server-side with a record ID.Tap to expand steps & related links

Recommended checks

  1. Confirm assignment saved — Have dispatch re-open the WO and verify technician field persisted.
  2. Check branch context — Technician profile branch must match job branch rules.
  3. Reset date filters — Default views sometimes exclude same-day additions.
  4. Validate role visibility — Role templates may hide certain statuses or job types.
  5. Refresh/reinstall mobile — Clear cache only after server-side verification.
Playbook: Technician accountabilityWork order lifecycleMobile technician opsWork orders

FAQ

Should technicians share logins?
No. Shared credentials destroy auditability and break permission intent. Issue individual accounts and use role templates for temporary help.