[DONE ✅] Improve policy options ux in server settings

[britttttk]

I find the current list of policies a little hard to read. I proposed in the chat to reword and reorder them. @dennisreimann also suggested grouping and adding doc links. This is my suggestion, also a few rewordings:

Server Admin Policies

Existing User Settings

• Allow non-admins to use the internal lightning node in their stores
• Allow non-admins to create hot wallets for their stores
• Allow non-admins to import hot wallets for their stores

New User Settings

• Disable new user registration on the server
• Disable non-admins access to the user creation API endpoint
• Require a confirmation email for registering

Notification Settings

• Disable notifications from automatically showing (no websockets)
• Disable stores from using the server's email settings as backup

Maintenance Settings

• Check releases on GitHub and alert when new BTCPayServer version is available
• Discourage search engines from indexing this site

Currently it's this:

[Zaxounette]

In the string Check releases on GitHub and alert when new BTCPayServer version is available, the word alert could be replaced by notify, making the link between that setting and the notifications feature it uses more explicit ?

Other than that, good idea !

[dstrukt]

Had mocked this out when I first started bringing over all the screens to Figma, same idea, but slightly different groupings, will give it another look over and see where we aligned.

Regardless, I love that we all seem to be on the same page!

Will get this cleaned up for @dennisreimann to implement.

Would be good to open a PR if there isn't one already -- should be a relatively easy patch.

[britttttk]

I like the green checkboxes very nice. Although I think the groupings Dennis made were quite clear. I agree this should likely be closed.

[Eskyee]

Yes I liked @dennisreimann groupings

[britttttk]

I don't see how to close it. @pavlenex

[dstrukt]

Oh yeah, those colored checkmarks, etc.. will be addressed UI updates with Bootstrap changes (dennis and I working on already, so no need for extra ticket, etc..), but I've gone through the linked PR, and it looks like you guys covered everything.

I just completely missed it - great work!

Nothing else from me on this one.

[Zaxounette]

You missed it probably because Github messes up things with discussions.
You can't tag or close discussions via PR's. Makes kinda sense, but still.

[Eskyee]

Been going thru most of the UX and it’s clear and simple... not found nothing at the moment!! Everything seems to be working fine on the testing server @britttttk will dig deeper tonight.. no problems so far... we love Colours that make it instinctively easy, and confident 🙌✨📸 great work in front of me ❤️✅

[NicolasDorier]

we can close this?

[pavlenex]

There's no really way to close discussions for now unfortunately, I believe it's something they're working on, either archiving or hiding from the main view. We can delete but I don't think that's good.

[MaxHillebrand]

yes, fwiw maintainers can lock the conversation and prevent new comments being written.

[dennisreimann]

Isn't there a feature to turn discussions into issues?

[pavlenex]

Not yet, but issues -> discussions is possible.

[dennisreimann]

Ah ok, I must have misread that. Thanks!