When your Snipe-IT installation is first set up, it can be a little overwhelming to figure out where to get started.
The first place to start is usually your Admin Settings. We go through each of the specific admin options one by one in the Admin Settings section of this documentation, but that's where you can set your branding (logo, etc), alert preferences, LDAP configuration, two-factor authentication and so on.
There are some high-level concepts you should be familiar with before you start adding assets. We discuss those below.
Asset tags are a unique identifier for assets within your system. Each one must be unique, and is often used in conjunction with Asset Labels. They identify each unique piece of hardware so that you know which specific device it is.
For users who don't need asset labels, the unique serial number of each device is often used as the asset tag, or you can turn on auto-incrementing asset tags in Admin > Settings, which will generate a unique asset tag for you when you create new assets.
Checking in and checking out are two primary concepts within Snipe-IT. When you checkout an asset, license or accessory, you’re marking them as being in the possession of someone else. This means that they cannot subsequently be checked out to another person until they are checked back in. This prevents “double-booking” assets, where one asset has been promised to or assigned to multiple people.
When an employee leaves your company, or if an asset, license or accessory is not functioning properly, you would check it back in. Checking it back in indicates that it’s back in your possession, or potentially out for repair. It’s up to you to decide what status to assign it, based on the condition of the asset.
Status labels are used to describe the state of the asset. You can add as many status labels as you’d like. Each status label will have one of four characteristics that describe the state of assets with that status label:
|Status Label Type||Description|
|Undeployable||These assets cannot be assigned to anyone.|
|Deployable||These assets can be assigned to people|
|Archived||These assets cannot be assigned to people, and will only show up in the Archived view|
|Pending||These assets can not yet be assigned to anyone.|
Use status labels however you see fit. You can just keep the starter labels we set up for you, or you can flesh out a detailed set of statuses that will make sure your team always knows exactly what’s going on with each asset.
If you set up your status labels well, they can be enormously useful. A status label that is a pending label named “Awaiting Re-Imaging” tells your team that this item can’t be deployed because it’s still in the re-imaging stage and isn’t ready yet. Once it’s ready, your team can update the status to “Ready to Deploy”, and then it’s added to the pool of available deployable resources.
*Once an asset that belongs to a status that is "Deployable" is assigned to a user, it assumes the meta status of "Deployed".
In most of the table-based interfaces in Snipe-IT, you have the option of showing or hiding specific columns, so that columns you don't care as much about don't take up space on your screen, and columns you do care about are easily visible.
To use this feature, simply click on the icon that looks like a split-pane window in the top-right of the table interface. Checking and unchecking the checkmarks next to the column name will show and hide the columns accordingly.
Updated about 4 years ago