Can you please advise if its possible to create a user who could view all gateway configuration pages, allowed to launch all projects in designer but not capable of changing anything ? it would call this user "admin_readonly" This user could audit the project but will not be able to modify anything.
No, nothing like this is available. The only distinction you can configure is between config and status pages.
This could be configured, but you'll have to set it up on each project.
You could set this up a "security configuration project" and set it as inheritable. That way you wouldn't have to set it up on each project, just inherit the config.
that's how i thought things are. So i always take a backup first when checking live gateway.
PS. even taking a backup might be a dangerous as i remember you mentioned that database connections are dropped momentarily which normally is ok but has potential to disrupt something sophisticated.
there is plenty of control in the designer but i believe gateway being critical element does need this functionality as well to prevent a cat walking on the keyboard stoping the plant
No, database connections don't stop. The internal database can be tied up with the backup, and if that takes more than 30 seconds, other services can be disrupted.
so in general huge backups with many projects have higher potential to discrupt something,
do you think during backup which takes around 30 or more seconds false log entries like clock drift might be generated?
Not usually clock drift, but errors about obtaining an internal DB session.
I didn't find any existing requests for being able to view the gateway configurations without being allowed to make changes.
You could put in a feature request on the ideas page to gauge interest.
As someone who is currently learning ignition for first time and has admin access to gateway, i am surprised to learn there is no way to limit control! I shall definitely be careful.
yep be careful, i would do fresh backup first just in case and keep cats away
It's not a good idea to make gateway changes on a production server while it's live. It is a far better practice to use a development server, which does not have to be licensed (just use in trial mode), to make and test changes. Then when the changes are proved to have no ill side effects, push them to the production gateway during downtime when possible. A lot of integrators use a development gateway, quality assurance gateway, and a production gateway for this.