The xMatix mobile app brings your apps, lists and records to your phone or tablet, using the same account you use on the web. It is built offline-first: you can keep working when the connection drops, and your changes sync when you are back online. This page covers getting the app, signing in for the first time, working offline, and reading the sync status.
Prerequisites
- An xMatix account that already signs in on the web — see Signing in to xMatix.
- The app itself, provided by your organization. Your administrator tells you whether your organization uses xMatix on mobile and how to install it.
- An internet connection for the first sign-in and the initial download.
Procedure
Step 1 — Get the app from your organization
Follow only the installation link or managed-app-catalog instructions supplied by your organization. Check the publisher, app name and requested permissions before installing; tenant-branded distribution can differ by organization. Open the app and confirm the xMatix sign-in screen appears. If no instructions were issued, stop and ask the administrator rather than installing an unrelated store listing.
Step 2 — Sign in with your work account
Open the app while connected, enter the exact invited work email and use the same password, one-time-code or passkey method as the web. Complete device verification when prompted. Confirm the expected organization and app navigation appear before allowing data to download; an unexpected tenant means you used the wrong account or invitation, not that a second mobile account is needed.
Step 3 — Let the first sync finish
Keep the app foregrounded, connected and awake during first sync. It downloads permitted apps, layouts, reference data and the configured transaction window. Open sync status and wait until the initial queue is complete with no failed entity. Spot-check one expected customer or item before leaving connectivity; a missing item at this point is usually scope or permission configuration, not an offline fault.
Step 4 — Work online and offline
Use the same lists and touch-friendly forms online or offline. Before a field shift, open the records you expect to need so they are present locally. When connectivity drops, save normally and verify the app marks the change pending; do not repeatedly tap Save. Server-only lookups or posting actions wait for connectivity and should not be interpreted as data loss.
Step 5 — Check the sync status
After reconnecting, open sync status and compare last-sync time, pending count and failed count. Keep the app foregrounded until pending reaches zero. Open every flagged item, read the server validation or conflict, correct and resend—or discard only when the work truly should not reach the server. Confirm a critical record on the web before considering the field work delivered.
Expected result
The user is signed into the intended tenant, initial sync completes without unresolved failures, and expected reference and work records are available locally. Offline saves appear as pending once, then reach zero and become visible on the server after reconnection.
Common problems
If you cannot sign in on mobile, try the web first with the same credentials — if that fails too, it is an account question for your administrator. If a record you can open on the web is missing offline, that is usually the offline scope: the app keeps a configured subset of data on the device, and some record types are online-only. If queued changes are not going out, open the app in the foreground with a working connection and check the sync status for flagged items that need your attention.
Common questions
Where do I download the app?
From your organization. Your administrator tells you exactly how to install xMatix on your device — the installation route is set up per organization, so follow the instructions you are given rather than searching for the app yourself. If you have no instructions, that usually means your organization has not rolled out mobile access to you yet; your administrator can confirm and arrange it.
What happens to the changes I make offline?
They are saved on your device and queued, then sent automatically when you are back online. If a queued change cannot be applied — the record changed on the server in the meantime, or a validation rule rejects it — the app flags that item in the sync status so you can review it, fix and resend it, or discard it. Until a change has synced, it exists only on your device, so reconnect and check the sync status before you consider the work delivered.
Will I see the same data as on the web?
Your access is the same: one account, one set of permissions, so what you are allowed to see and do on mobile mirrors the web. What is stored on the device for offline use is a configured subset — reference data plus recent transactions — so an older or less-used record may need a connection to open even though you have access to it.