Group settings have "Self-Checkout" option under "Self" but no option to add self-checkout option for assets

[vzickus]

Debug mode

• [X] I have enabled debug mode
• [X] I have read checked the Common Issues page

Describe the bug

Under group settings, under "Self" there is an option to enable "Self-Checkout", however, there seems to be no option to mark assets for self-checkout.

We want to use snipe-it in our lab to keep track of equipment, however, now any user can checkout for anyone else, where we want the option to only checkout under their own name.

Reproduction steps

1. Create a new asset
2. No option to enable self-checkout

...

Expected behavior

Option to enable self-checkout when creating a new asset.

Screenshots

No response

Snipe-IT Version

v6.2.3 - build 11759

Operating System

Windows

Web Server

IIS

PHP Version

8.1.2

Operating System

No response

Browser

No response

Version

No response

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No response

Additional context

No response

[welcome[bot]]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

[jcracine-cimeq]

This is also a feature I noticed that seemed to be missing. We would also like to use Snipe it in a decentralized manner like you. One thing we thought would be to use the REST API and assign a unique token to every one, and then make a check-in/check-out station. Since each token is unique and tied to it's user's account, you can fetch the necessary information to check-out the assets to the correct user.

It would be nice if the self-checkout feature could also be used via the REST API.

[vzickus]

Thanks for your input, did you manage to get it working using the REST API?

[jcracine-cimeq]

Thanks for your input, did you manage to get it working using the REST API?

We haven't worked on it yet, but with what we've been discussing, there's a few ways to do it via the REST API.

You could issue each user their own API token, and then use the /users/me feature to query about your user and then use those information coupled with user inputs to create the checkout log. As far as I know, the token should retain the user's permissions but we haven't tested that yet.

You could also create an account whose sole purpose is to be used via the API, and give them enough permissions so that your station can do all operations you want it to do. But that option does also require user inputs to fill all the required fields of a checkout operation.

Either way, the upside of using this method is that you don't need administrators to manage the check-in/check-out operations.

But I do think that having the self-checkout feature working and implemented with the REST API would be the best to do that kind of setup, as that would reduce the number of operations needed to check-in/check-out items.

[jcracine-cimeq]

+1 bump