[Feature]: EULA Customization

[ItPerson-k12]

Snipe-IT Version

8.3.4

How can we help?

I have 4 different items pertaining to EULA that I am hoping could be considered.

First, the EULA text box is just that, a plain text box with no capabilities.

I am proposing two options.

1. The ability to upload a file with our language in it instead of the Markdown text box. When the user is sent an email, it displays the file in the email with the language format and then the user can select to accept or deny the terms.
2. The ability to have the EULA text box be a fully functional text editor with the ability to Bold, highlight, Increase/Decrease font, color, font type, etc.

Second, I am looking for the option to use a text to sign option as well vs the signature box which when using a mousepad makes signatures difficult. This could be typed in basic font and does not necessarily need to look like a signature. Mentioned in #12135

Third, the ability to send the EULA back out upon check-in to use as a confirmation of returned assets.

Use case for this would be after a user leaves, we have no ability to prove they did not turn in their device other than saying I don't physically have it. A signature upon check-in would protect the end user from company retaliation, that they did indeed turn in the device.

Lastly, At the top of the EULA after signed, it displays all asset data (company, model, etc.). It would be nice to be able to change the location of this to the bottom and customize what fields are included. For example, company, we use this field for the vendor it was purchased from. The end user does not need to know this.

Code of Conduct

• I agree to follow this project's Code of Conduct

[snipe]

I'm not sure what the benefit of having a file-based EULA is? The markdown lets you customize the text quite a bit already.

As for the WYSIWYG markdown editor, I did give that a stab, but nobody really seemed to respond to it, and any sort of WYSIWYG editor will inherently introduce potential XSS issues.

[ItPerson-k12]

My main thought was its dependent on formatting of your EULA; it can be difficult to reproduce in the markdown. If you already have something curated in a pdf, having the file displayed would be easier than learning to use the markdown on the user side. I do not want to speak about if it would be difficult to make work on your end. But completely understand if it is not an option.

Any thoughts on the other ideas mentioned? Thank you for all your work, this is a great product!

[snipe]

I think the main challenge with a pre-formatted PDF is that we cannot integrate the signature, date, etc, since it's a pre-made PDF. When we generate the PDF on the fly, we can insert that data, but we wouldn't be able to do so with an uploaded one.

[snipe]

@ItPerson-k12 I'm not saying no - let me be clear about that part. It would just be more limiting, and I'm worried that folks who see the new feature won't read the fine print on the limitations. :(

[ItPerson-k12]

No worries at all. I understand being open source allows for all sorts of use case and it must be hard to balance what to implement for all vs how one many use it. I appreciate you taking the time to look into all of my suggestions.

I also closed this just out of habit, you responded and I did not have any more to contribute. If I should have left it open I apologize!