Snipe-IT Asset Management Installation Documentation

Welcome to the Snipe-IT documentation hub. You'll find comprehensive guides and documentation to help you install Snipe-IT as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Cloning Assets

The "Clone" button on the assets listing page allows you to quickly create a new asset with the same overall characteristics as the asset you're cloning. This means the new cloned asset will have the same Asset Model, model number, custom fields, supplier, purchase date, purchase cost, order number, notes, warranty months, etc.

🚧

A note on cloned asset images

Images uploaded to a specific asset will NOT be copied over to a newly cloned asset. The reason for this is that generic asset images should be set at the asset model level. Images uploaded to specific assets should reflect only that asset.

For example, if you have an asset called "Birgit's Laptop" - a 13" MacBook Pro Retina, with asset tag 12345678 - the asset image you upload to that specific asset should only be related to that particular asset.

If you were to clone Birgit's Laptop to make a new asset called "Brady's Laptop", if we carried over that specific image from Birgit's Laptop, it would not be accurate, in the same way that we do not copy over the serial number from a cloned asset, since a different specific asset would not have the same serial number. Brady's Laptop is not the same physical device as Birgit's Laptop, so those characteristics do not get cloned over.

If you wish to use generic images, such as an image of any 13" MacBook Pro Retina, just to have the overall visual of what that model should look like, you should set that image at the Asset Model level.

If an asset does not have an individual image uploaded to it, it will fall back to whatever the Asset Model image is, if one exists.

This allows you to use generic images and images specific to a particular asset as is appropriate.

Updated 7 months ago


Cloning Assets


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.