Hardware assets, licenses and users, worked for you
A companion works the 6 operations your Snipe-IT account exposes. It can update a hardware asset and create an user, and every one of those waits on an approval card showing the hardware asset before it changes.
Open the hardware asset. Check it against something else. Write the change. Move to the next one. That is the Snipe-IT afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a hardware asset until you approve it.
What it can do is exactly what Snipe-IT exposes to an account you authorise and nothing beyond it: 6 operations, 3 reads and 3 writes. In practice that means it can update a hardware asset, create an user and create a hardware asset, and work across the hardware assets, licenses and users.
The Snipe-IT API stops at Snipe-IT. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Which Snipe-IT hardware assets does a companion see?
3 of the 6 operations are reads.
Your account, not a guess at it: a companion can get user assets, get a license and get a hardware asset, and the full list below is the whole list, with nothing inferred from Snipe-IT's documentation.
The hardware assets are what most of this inventory is about, alongside the licenses. A companion can hold all 6 of these operations and forty open tabs in the same pass, which is how an afternoon of Snipe-IT admin becomes a queue you review.
- Get User Assets
- Get License
- Get Hardware Asset
What happens before it can update hardware asset?
All 3 write operations wait for you.
A companion can update a hardware asset, create an user and create a hardware asset, and each one is staged on an approval card first: you see the hardware asset, the field and the new value before it lands in Snipe-IT.
Nothing in Snipe-IT is sent, changed or deleted on your behalf without that click, and a rejected card leaves the hardware asset exactly as it was. The gate is the same one on every surface, described at security.
- Update Hardware Asset
- Create User
- Create Hardware Asset
Can the hardware assets pass run every Monday?
Yes.
Saved as a routine, the Snipe-IT hardware assets pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of the ticket queue, the Snipe-IT hardware assets sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents