FAQ
Common questions about what AssetR is and how it behaves.
Is this a hosted/SaaS product?
By default, no — AssetR is self-hosted, run on your own infrastructure via Docker Compose against your own Postgres database, with no external account required. If you'd rather not run it yourself, we also offer managed hosting where we run a private instance for you — see Pricing for details.
Is AssetR open source?
The source code isn't publicly published, but the compiled application is free to use — for personal, internal, or commercial purposes, at no cost. See the License page for the full terms.
Do the employees whose assets are tracked need to log in?
No. AssetR is an admin-only tool. An Employee is just a record representing who something is assigned to — no login, password, or session. Only IT/admin staff (Admin Accounts) log in.
What roles are available?
Two: Super Admin (everything, including Settings, Backups, and the Audit Log) and Asset Manager (day-to-day asset/license/accessory/employee management and Reports, without access to Settings, Backups, or the Audit Log).
How do email alerts work?
A fixed daily check at 08:00 server time looks for expiring warranties, expiring licenses, and low accessory/consumable stock, and emails an explicit, admin-configured recipient list. It's opt-in per recipient, not automatically sent to every admin account, and can be toggled off without touching your SMTP configuration.
Does it print QR codes for asset tags?
No — asset labels use a Code128 barcode, not a QR code. A 1D barcode works with dedicated barcode-scanner guns and stays meaningful without any app, network, or login involved.
Can I restore a backup from inside the app?
Restoring is deliberately not a one-click action. The app documents the exact manual command for restoring a backup instead — an automated restore is too risky to trust to a button.
Can I import my existing spreadsheet of assets/employees?
Yes — nearly every entity (employees, assets, licenses, accessories, consumables, and every org-lookup) supports CSV bulk import with a downloadable sample template. Rows that fail validation or duplicate an existing name are skipped and reported, not silently dropped.
What happens when someone leaves the company?
One "Offboard" action from the employee's detail page previews exactly what it will do, then checks in every assigned asset and accessory, revokes every license seat, and deactivates the employee record.
Is SSO supported?
Yes — connect any standards-compliant OIDC identity provider (Microsoft Entra ID, Okta, Google Workspace, Auth0, Keycloak, and others) from Settings with an issuer URL, client ID, and client secret. It signs in existing admin accounts only, matched by verified email, and never auto-creates one. Local email/password sign-in stays available alongside it as a fallback.
Is there an API?
Yes — a bearer-token authenticated public REST API covers read access across assets, employees, licenses, accessories, and consumables, plus write endpoints for the two integrations most teams actually need: employee lifecycle (create/update/offboard, e.g. from an HRIS) and asset/accessory checkout-checkin (e.g. from a ticketing system). Departments get full CRUD too. Keys are created and revoked from Settings, each scoped to a role with an optional read-only flag, and a ready-to-import Postman collection covering every endpoint is one click away from the in-app API docs.