An asset register is a list of people as much as a list of things — nothing can be checked out to a person who does not exist in the system. Here is how to build the people side properly.
Checkout needs a name, and that name must exist in Snipe-IT first. The People section is the register's other half: every employee who might hold equipment, organised by department, location and company, with permissions deciding who can see and change what. Set up carelessly, this becomes a second mess to clean. Set up with the few rules in this guide, it stays boring for years — and boring is the highest praise a people list can earn.
The practical order of work: people first, assets second, checkouts third. A person record needs a name, a username and an email — the email matters because checkout receipts, acceptance requests and alerts are delivered to it. Creating eighty users by hand is an hour nobody enjoys, which is why the CSV importer also handles users: export your staff list from wherever it already lives (payroll, a spreadsheet, Active Directory), shape the columns, import once. The asset-import guide in this set covers the importer's habits, including its famous failure modes; the same lessons apply. What you must not do is create people lazily at checkout time with names like test or laptop boy — those records live forever in audit history.
Snipe-IT offers three organising axes and small offices overthink all three. Departments (Accounts, Sales, Support) power the reports owners actually ask for — what does Sales hold, what did Support break this year. Locations answer where things physically are across sites and floors. Companies exist for groups running several firms or MSPs tracking client kit; a single company should have exactly one. The discipline: create the few values that match reports you will genuinely run, use them identically every time, and resist creating a department per team-leader. Structure that mirrors the real org chart's top level survives reorganisations; structure that mirrors every internal shuffle does not.
Snipe-IT's permission model has a property worth building your process around: users without management permissions can only see items checked out to them (and items they have requested). That makes the ordinary staff login safe to hand out — an employee can confirm what they hold and sign acceptances without browsing the company's whole asset map. Above that sit granular permissions for the IT team (who may create assets, who may only check out, who may delete) and the superuser level, which should be held by as few people as have fingers on one hand — two is a good number, with the second being a break-glass account. Every extra admin is another door into the register that says who holds what, which the security guide in this set treats as sensitive data in itself.
If your office already runs Active Directory or LDAP, Snipe-IT can sync users from it, and also offers SAML single sign-on — new joiners appear, leavers can be disabled centrally, and nobody maintains a second people list. The honesty: this is a project of an hour or three, not a checkbox. Attribute mapping (which AD field becomes department, which becomes location) needs care, and a bad first sync creates the same dirt as a bad CSV. Offices under roughly fifty people often find the one-time CSV import plus manual joiner/leaver updates genuinely simpler. Offices above that, or with high staff churn, earn the sync effort back within a quarter. Decide by churn, not by fashion.
When someone leaves, two things must happen in order. First, their user page is the return checklist: everything checked out to them comes back physically, and is checked in (the checkout guide in this set covers the exit-day flow). Second, the user is deactivated so they cannot log in — and that is all. Do not delete the person. Deleting a user tears holes in the audit history of every asset they ever held; the chain who had this laptop in 2026 becomes unanswerable. Deactivated users keep history intact while holding no access. The same principle applies to departments and locations that close: tidy forward, preserve backward.
See the system taking shape in the video — structure first, then the assets that hang on it.
▶️ Watch Full VideoNo, not by default. Users without management permissions only see items checked out to themselves and items they have requested. Broader visibility is a permission you grant deliberately to IT staff and admins.
If your office already runs AD or LDAP and staff churn is high, yes — Snipe-IT supports LDAP sync and SAML login. For a small, stable team, a one-time CSV import plus manual updates is honestly simpler to run.
It breaks. Deleting users damages the audit trail of everything they ever held. Deactivate leavers instead — they lose access, and the history of who held what stays complete.