Hide 'Settings' and 'Add a service' buttons? (so non-critical users can't edit homepage)

[K-J-VV]

Is there a way to hide these buttons?

I'm trying to make a generic homepage other users can't edit. Considering there is no way to create actual user accounts in Homarr, I was wondering if it's possible to "toggle" off these buttons? Maybe by commenting out some code somewhere?

Then when the developer would want to add more services or customize the homepage, they can either un-hide/toggle-on the buttons (or just work in the terminal).

[ajnart]

Is there a way to hide these buttons?

I'm trying to make a generic homepage other users can't edit. Considering there is no way to create actual user accounts in Homarr, I was wondering if it's possible to "toggle" off these buttons? Maybe by commenting out some code somewhere?

Then when the developer would want to add more services or customize the homepage, they can either un-hide/toggle-on the buttons (or just work in the terminal).

I guess you could delete the code that adds these buttons and the modify service menu

[K-J-VV]

Hi, we're still working for this. Homarr had a ton of technical debt until now, and 0.11 focused on removing old code. 0.11.5 will also contain a few new widgets.

Authentication has to be the most requested feature for Homarr, and we already have started working on it for 0.12. We can't give any ETA yet, but it will include quite a complex and detailed system for users and permissions. Stay tuned!

Let me know if you have further questions.

Awesome to hear its still being worked on! Thank you for the quick update, really appreciate it

I know these features will come when they're ready :)

Would you have insight as to whether it may be possible to make an environment variable in the docker-compose file that can disable the 'Edit Mode' and 'Settings' buttons? I know you already wrote about this generally earlier and doing it myself would likely break Nextjs. I've been using Dashy as my public facing dashboard since it is able to do this and was wondering if something similar can be implemented in Homarr?

In Dashy, there is an option to prevent changes https://dashy.to/docs/configuring/#preventing-changes ; they utilize disableConfiguaration as a boolean which "If set to true, no users will be able to view or edit the config through the UI"

Personally, I don't have a need for users/authentication since I utilize services like NGINX Proxy Manager and Authentik to control access to services like Homarr. Just making it possible to completely eliminate/hide the 'Edit Mode' and 'Settings' buttons from the default page would be all I need in terms of control to be able to safely use the dashboard more publicly. However, I understand Authentication will ultimately achieve the feature I am hoping for. I am just wondering if maybe having 'Edit Mode' and 'Settings' buttons hide-able via an environment variable may be a lower hanging fruit to reach than fully functional built-in Authentication

[manuel-rw]

Yes, adding that would be possible.
Judging from the Dashy documentation, they simply block all changes and hide the buttons.
Would you be okay, if we implement a single environment variable, that disables editing and changing the config?
If yes, we should be able to do that for 0.11.5

Biggest disadvantage I can think of is, that you'll have to restart the container, to disable the "disable edit mode".

[manuel-rw]

I made a quick draft.

• Settings menu would be entirely gone and hidden
• Enter and Exit edit mode button is entirely gone
• API does not allow any updates anymore, regardless of their content / authentication
• About shows this information message:

JFYI: @ajnart

[K-J-VV]

From my admin/user perspective, this fix would be great!

Having to restart the container to disable "disable edit mode" is not that big of a hassle, imo. Workflow would be: take page offline, restart container to enable edits, make edits, restart to disable edits, put back online/publish.

Once a dashboard is fairly setup, having to go through this workflow shouldn't be too frequent and not much bother. As a temporary hold-over until proper authentication is built, this would make it possible to confidently use Homarr as a public facing dashboard for family/business use. If I knew my users couldn't make edits, I'd deploy Homarr in public instances today

[manuel-rw]

This has been implemented in 0.11.5. Can we resolve this discussion?