Multiple (different) dashboards for multiple users (with login)

I need different users to view different dashboards (the users needs to be able to see only its own dashboard, not the other), I can password protect the dashboards with Cloudflare, but this can work only if the dashboard URL never changes, how can I do that?
Do you know of any other better way?

create multiple node-red instances and give different port numbers ?

I don't use cloudfare - but on the basis it can password protect single URI's
Each Tab in the dashboard, does indeed have its own URI

First Tab - http://x.x.x.x:1880/ui/#!/0
Second Tab - http://x.x.x.x:1880/ui/#!/1

and so on.

just set the dashboard to hide the title/nav bar at the same

This will get you close to a working solution
I have not tested this of course

How does Node-red decide which is dashboard #0 ?

As I develop, deploy, develop ... precisely which dashboard is displayed at :1880/ui keeps on changing. Does that mean dashboard 0 changes too?

Isn't dashboard 0 is the first active tab listed in the right sidebar and dashboard 1 the next active dashboard ?
there was a discussion in this forum to 'name' the dashboard tabs

When I sort the tabs in the side bar - i usually manually order them myself - and the ID's are list ordered - at least most of the time :sweat_smile:

You can use any proxy service to achieve this with Dashboard. Though, of course, as has been pointed out, an instance of Node-RED only has a single instance of Dashboard. Other dashboards (lower-case "d") exist as well of course.

Actually, as there is only 1 Dashboard in a node-red instance, the same dashboard is always displaying - however, as a Single-Page Application, Dashboard's default tab may have changed. But worth remembering that an SPA is indeed a single "page". It is just that the framework is good at hiding/showing parts of the page to make it look like multiple pages.

Ok I used the wrong term.
I guess that the OP's question is regarding dashboard tabs.

I have found that the "default" dashboard tab changes and I suspect that might imply that dashboard tab 0 is not fixed.

Therefore I suspect that calling dashboard tabs by name is safer than calling by the tab number.

Since I don't like the idea of running multiple instances of Node Red to have multiple Dashboards, the idea of having multiple tabs with different (and static) url could work, but reading the other reply, this doesn't seems possible, correct?

node-red-dashboard v 3.4 has this feature

Add ability to specify to start page by tab name in url

so it should be possible. (I am not sure that I understand that sentence from the release notes, I'm just now looking at what you can do with it)

The main issue is that it won't be secure. All of the data in Dashboard is all part of the same page. So I don't think that using something like CloudFlare Zero Trust to apply a login to different users on different tabs won't really help.

I have only two, one for supervisor control other view only

@smanjunath211 could you enlighten us as to how you do this? I assume one node-red instance functions normally in an admin role. But how does the second instance supporting a view only dashboard access state/data from the first instance?

May be you mis-understood me. i have two flows, one of them which has a 'write' access to the MySql database which, in the other flow i dont have any dashboard contents that 'write' to the database, only view.
The original post asked for different dashboards so that users can be segregated, so having different instances, can do that. for example :1880 for suprevisor with flows with escalated controls and :1881 for just viewing the dashboard, without any 'change' actions.

so you can give password of :1880 to one and :1881 to others. so you have a fixed URL.

i dont have a setup to interact between instances, since i directly write and get information from a database. but i'm sure you can do interactions between instances with MQTT setup, there are information available in the forum.

Using MQTT is probably the easiest way. See this tutorial MQTT Essentials - All Core Concepts explained

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.