Asset records hold value, locations and custody, so access should follow the job. Asetavo gives every user a set of nine permissions, and the API refuses anything a permission doesn’t allow. Every change records who made it, and a lost handheld can be cut off in one click.
The way it usually works today, and the way it works once it lives in one system.
Before: Everyone who can open the asset spreadsheet can change the purchase cost, delete rows or overwrite a location.
With Asetavo: Permissions separate reading, creating, editing, deleting, configuring, finance, audits, devices and alerts, so each person gets only what their job needs.
Before: When a value changes, nobody can say who changed it or what it was before.
With Asetavo: Every asset change is written to an append-only history with the old value, the new value, the event and the person, taken from their verified sign-in.
Before: A handheld goes missing or a contractor leaves, and their access keeps working for weeks.
With Asetavo: Each signed-in device is its own session. Revoke it and its next request is refused and its refresh token stops working. Deactivating the user cuts off every device they have.
Before: Readers and integrations share one password, and nobody knows what they can reach.
With Asetavo: Fixed readers use their own per-reader signing secret and can reach only the event-ingest endpoint. Integrations sign in as a named user with scoped permissions.
Coded from the real Asetavo screens, with sample data for a fictional company, Northfield Group.
Priya Shah, Inventory manager: she can register, edit, configure and count assets, but has no finance, delete, device or alert permissions. The right-hand side shows what that means in practice.
Every card below is in the product today, on the plans shown above.
view, create, edit, delete, manage, finance, audit, devices and alerts, combined into roles such as admin, technician and viewer. The app hides what a role can’t do and says why, for example “Needs the Finance role”.
One central route-to-permission table, checked on every request. Unlisted routes are refused.
Cost, residual, accumulated depreciation, method, rate and life are stripped from writes unless the user holds finance.
Access tokens of 12 hours or less, rotating refresh tokens, and a per-device list with one-click revoke. Lost a phone? Sign it out from More › Devices in the app or from the web; anything it hadn’t synced stays on that phone and is never sent.
Five failed attempts trigger a lock-out that doubles each time (30 s up to 1 h). Unknown users and wrong passwords get the same response.
Append-only per-asset history with the verified actor, plus who acknowledged and resolved each alert.
Each workspace’s data lives in its own database with its own token-signing secret.
Readers sign each batch with HMAC over device id, timestamp, nonce and body hash. Replays, stale timestamps and floods are rejected.
Alert webhooks carry an HMAC signature, go only to public HTTPS hosts and never follow redirects.
In the Asetavo app
The app follows the same roles as the web: viewers look things up, editing and status changes need edit access, and money shows only to Finance. Location is recorded only at the moment of an action, never in the background, under a workspace policy of Off, Optional or Required. A lost phone can be signed out from More › Devices or the web.
Swipe to see more screens →
Each company workspace runs on its own database. Tokens are signed with a per-workspace secret, so one company’s token is useless on another’s.
Add people on the Team page and give each a role. Every sign-in creates its own device session with a short access token and a rotating refresh token.
Group permissions into roles that match real jobs, such as Finance, Inventory manager, Auditor or Security officer. Admins hold everything.
Nine permissions: view, create, edit, delete, manage, finance, audit, devices and alerts. Anything not granted is denied.
Every API route maps to one permission and is checked on every request against the live user and device records, not just the token.
Changes are stamped with the verified user and appended to the asset’s history. Alert acknowledgements and resolutions record who and when.
| Criteria | Can | Cannot | Permissions |
|---|---|---|---|
| Finance | See cost and NBV, run depreciation, dispose | Create or move assets | view, finance |
| Inventory manager | Register, edit, configure, count | See cost, delete, manage readers | view, create, edit, manage, audit |
| Auditor | Run and reconcile stock-takes | Edit the register, see cost | view, audit |
| Maintenance tech | Work orders, move and check out | Configure, finance, delete | view, edit |
| Security officer | Readers, zones, alert rules, ack alerts | Edit the register, finance | view, devices, alerts |
| Viewer | Read assets, reports, exports | Change anything | view |
Roles are examples. Your workspace admin combines the nine permissions however your organization works.
How a person gets in, and how you get them out:
What each permission unlocks, and the rules around it:
Walk us through your sites and we’ll show you security & permissions set up the way you’d use it.
Book a demoSet up roles, protect finance data and keep a verified record of every change from day one.
No card required · Workspace ready in minutes · Simple USD pricing
