Snipe-IT is an asset management system that LSIT has implemented to keep an updated list of managed assets and all relevant information about those assets. Snipe can also keep track of users and software licenses.
The official github repo for Snipe-IT can be found here https://github.com/snipe/snipe-it
And the official documentation can be found here https://snipe-it.readme.io/docs
Any general issues or questions can probably be resolved from those two sources.
Categories should not need to be edited very often. The categories as of writing this are computers, servers, printers, and VM’s.
These indicate the current status of an asset. New status labels can be created but that should not happen very often. The status labels currently include the following:
- Ready to Deploy - all the required information is filled out and the asset is ready to be checked out to a user. An asset must have this status assigned to it in order to check it out.
- Deployed - the asset is currently checked out to a user
- Pending - sort of a neutral status. An asset should not be assigned pending for very long.
- Archived - this means the asset has been surplussed. To surpluss an asset it should be checked in, assigned to this status, and then deleted.
- Unknown - this means this asset has not been inventoried for at least 2 years as of August 2020. This is meant to be a temporary status label. Any asset assigned to this label should be inventoried and assigned the correct status as soon as possible.
- Retired - This status label is also meant to be temporary. Assets assigned this label were assigned to retired faculty members when we migrated from scinet to Snipe in August 2020. Any assets assigned to this should also be inventoried and fixed as soon as possible.
Fieldsets are a way to assign custom fields to categories of assets so that it doesn’t need to be done for every asset model. We currently have fieldsets for the computer and server categories. Custom fields can be set to be a required field or not. They can also be set to different types such as a list or date. This helps keep the data cleaner and easier to manage.
Auditing is Snipe’s version of doing inventory. When you audit an asset, it lets you change the location as well as add notes. It also sets the next audit date automatically or lets you change it to a different date. Darin asked that the default audit timeline be set for 2 years. 7 days before the next audit date, the asset will go into the “Due for Audit” section. If the audit date passes, the asset will go into the “Overdue for Audit” section. This will help keep our inventory up to date better.
You can use this dropdown to edit the fields you see on the page.
The search bar can be used to search for information in any field.
You can bulk edit or delete assets by selecting multiple assets and clicking on this dropdown.
Snipe is currently connected to Active Directory meaning new users can be created by simply entering their AD credentials. There can be issues logging in if a user is already in the database. You can fix the issue by deleting the user and having them log in again or by simply going into the edit page for the user and manually changing their password for them.
The developers of Snipe are currently working on a SAML integration which should allow us to use CAS once that is pushed to the main branch.
Groups allow you to manage permissions for users. We have created a group for Engineering Team and Full Timers, Service Desk, and department secretaries. If a user is not assigned to any group, they can only view their own assets.
Companies are a way to allow users to have access to a subset of assets and users. We have created a company for each department so that department secretaries can view all the assets and users in their department. If a user is assigned to a company, all permissions they have will apply only to the company they are assigned to so LSIT employees should never be assigned to a company. Both users and assets need to be assigned to the correct company in order for secretaries to see them.