I’m building a dashboard in the Ignition Perspective module. How do I properly publish my Perspective project and share it with users so they can view the dashboard? Also, how can I configure or limit access so that only people in my organization can open and use it?
You should check Inductive University Course List - Learn Ignition Free.
Perspective:
Security:
If later you have any question you can come back with the specific problem you encounter.
How do I properly publish my Perspective project and share it with users so they can view the dashboard?
When you launch the project from Designer it will open a browser window. Copy the URL and share it with your users.
Also, how can I configure or limit access so that only people in my organization can open and use it?
Most Ignition instances are inside a company firewall so they are only accessible to people inside the organisation anyway. If the gateway is exposed to the Internet or you need to limit access for other reasons then Ignition's inbuilt security will do what you need. As Daniel has suggested, start with the online training.
Thank You. I will look at them
When the project is launched and the URL is shared with others, they are not able to open it. It appears like this
If you are on a local area network with other people, replace localhost with your IP address.
1 Like
That's because you are using Designer on the gateway machine. When you launch the project it uses localhost which is a kind of IP loopback to itself. If you share that then the other user's browser will look for the gateway on their PC / laptop.
In production setups Designer is used on a separate PC, not on the gateway.
Tip: before taking screengrabs, resize the window to just contain the relevant data. Yours is about 90% whitespace and has to be magnified to read the URL.
While especially true for production, I would say it applies to development, too. Don't run designer's on the same machine as the gateway. If you are connecting to localhost, you are either screwing up, or setting yourself to screw up.
(Containers may technically be connecting via localhost, but you should be using the container names, not localhost.)
Or, like me much for much of my forum work, I'm at home with my laptop running a gateway and designer on the same laptop to test out my answers. I'm not connected to anything else.
For training and quick hitters for the forum, I can understand. But not for any real development. Use VMs or containers in your laptop.
My primary workstation is my souped-up laptop, that goes wherever I go. It has multiple VMs and containers defined and ready, for isolated dev work. It does not have any gateway installed on the bare metal OS.