Tagaris for iOS and Android
Tagaris has a companion app for iPhone and iPad, on the App Store, and for Android, on Google Play. It works against your own Tagaris server: nothing is hosted by us and the app talks to no one else.
What it does
- Scan a label to open the asset. Point the camera at a printed QR label and the asset opens, with its whereabouts, status, history, photos, attachments, maintenance records and linked tickets.
- Report an issue after a scan. The asset's screen lists its issues and has Report an issue, so a fault found on a walk round is logged against the right item there and then. See Issues.
- Change whereabouts and status. Assign to a person or location, put an asset into stock, or change its status, including your own custom status labels, with the same one-tap next steps as the web app.
- Add assets from the phone. Scan an unknown serial or tag and choose Create asset, or fill in the basics by hand. A blank tag takes the next free one. Photos can be taken with the camera.
- Physical audits from the shelf. Audit mode records an audit for each label you scan, as the stock-take workflow does in the browser, and tells you when a label belongs to a different server or is not found.
- Audits with no signal. If your server cannot be reached, audit mode keeps scanning and saves each scan on the phone. See Auditing offline.
- Stock. Check accessories out, install components and issue consumables where it happens.
- Browse and search assets, people, locations, accessories, components and consumables when there is no label to scan.
- App lock. An optional lock (Face ID or Touch ID on iOS, fingerprint or face unlock on Android, device passcode as the fallback) guards the app when it opens or returns to the foreground. The sign-in session is unaffected; the lock only gates the screen.
- Appearance. Match the device, or force light or dark.
What you can do in the app
The app shows the actions you may take. Your role and your access groups apply exactly as they do in the browser: a view-only person sees the register and no buttons; someone whose access group lets them move kit sees Assign and Check in; someone who may report issues sees Report an issue. The server checks every action again, so a refused one names the permission it needed. A site limit applies too: assets and locations at other sites do not appear.
Auditing offline
Audits happen where the server is hard to reach: comms rooms, basements, warehouses, and anywhere off the office network when your server only answers on it. Audit mode carries on regardless.
- A scan that cannot be sent is saved on the phone, with the time it was made, and shows as waiting with a cloud icon. A count at the top of audit mode says how many are waiting.
- The app sends them by itself when the server is back: when you open the app, when it returns to the foreground, and every 20 seconds while any are waiting. "Sync now" does it on demand. You do not have to keep audit mode open.
- Each audit is recorded at the time of the scan, not the time of the sync, and the asset's history says it was scanned offline.
- A scan that syncs late never undoes a newer audit. If someone audited the asset in the browser in the meantime, the later date stays.
- A printed Tagaris label carries the asset's id, so it needs no lookup. A plain asset tag or serial barcode is matched by the server when it syncs.
- Anything the server refuses is listed with the reason (for example no matching asset) and leaves the queue. Nothing is dropped silently, with one limit: a scan more than 30 days old is too old to record as an audit and is dropped with a message.
- Scans wait for the server and organisation they were made against. Switching organisation does not send them to the wrong one.
Only audit scans work offline. Changing whereabouts, status or stock still needs the server: two people making different offline changes to the same asset could conflict, and an audit scan cannot.
Needs a Tagaris server newer than 2.5.1. Against an older server the scans stay on the phone and audit mode says the server needs updating; they sync once it has been.
Pairing and signing in
- Install the app, open it, and enter your server's address (the same
address you use in the browser, for example
https://assets.example.com). - Sign in the way you do in the browser: password with two-factor if it is enabled, or single sign-on with whichever provider your server uses. There is no separate mobile account and no API key to create; the app uses your own session, so your role, access groups and your organisation's security policy apply unchanged.
- The app remembers the server and the session. Sign out from the Account tab.
The app works on the free plan. It needs to reach your server from the
phone, so the server must be on a reachable address, not localhost, and
BETTER_AUTH_URL must match that address (see
Installing Tagaris). Plain http:// works for a server on
your own local network; anything reached over the internet should sit behind
a reverse proxy with HTTPS. iOS and Android do not trust self-signed certificates
unless the certificate is installed on the device, so use one from a public
authority such as Let's Encrypt where you can.
Privacy
The app connects only to the server address you enter. It sends nothing to Goodhall Solutions or to any third party, carries no analytics, and stores only your server address and session on the device (in the iOS keychain or the Android keystore).
Trying it without a server
Pair the app with demo.tagaris.co.uk to try it against the public demo.
The demo credentials are shown on the sign-in screen. The demo data has
assets with QR labels, but the Scan tab needs a printed label, so the Browse
tab is the quickest way to see asset detail, status changes and stock.
Requirements
- An iPhone or iPad, or an Android phone or tablet; the store page lists the supported OS versions.
- A current Tagaris server. The app's endpoints ship with the server under
/api/appand are separate from the REST API; no API key is involved.
Android
The Android app is the same app, on Google
Play. Two
Android points worth knowing: a server on your own network over plain
http:// works without any setting, and the app lock uses whichever
biometric the phone has enrolled (fingerprint or face unlock). Scanning a
printed QR label with any phone camera still opens the asset's page in the
browser.