[FEATURE_REQUEST] Hide Settings from Guests and Specific users

[G-S322]

Is your feature request related to a problem? If so, please describe.

I don't like how users and guests have access to the menu can download the config file from the settings menu, which also contains the hashed password...

Describe the solution you'd like

I would like to have the option to disable the settings menu for guests and/or specific users completely so that this just acts as a dashboard/ Landing page for links.

I was thinking something like
hideSettingsForGuests: true
and
hideMenu: true
for users under the auth section.

Priority

Medium (Would be very useful)

Is this something you would be keen to implement

None

[liss-bot]

If you're enjoying Dashy, consider dropping us a ⭐
_{🤖 I'm a bot, and this message was automated}

[rxunique]

+1

[Lissy93]

Actually, this sounds like something which should be implemented by default.
If basic auth is enabled, and the user is not logged in, they shouldn't be able to write any changes.

Thoughts?

[rxunique]

should be implemented by default

Do you mean there is already implementation? Or thinking its a good idea to be default?

If basic auth is enabled, and the user is not logged in

In my mind, I was hoping add an option to appConfig.hideComponents . currently hideSettings only collapsed the setting

maybe an option disableSettings to globally stop non-admin to edit and basically view only

[Lissy93]

maybe an option disableSettings to globally stop non-admin to edit and basically view only

Thanks @rxunique - Done!

I figured, if you've setup basic auth, and have guest access enabled- you wouldn't want guests to be able to edit configuration (otherwise there's not much point to the auth, beyond roles).

So instead of adding an extra option to disable edits from guests, it's now (since V 3.0.1) disabled by default. And so logging in is required to make changes, if auth is enabled.

If you need anything else modifying around this, let me know below, and I'll reopen.