@Tom-Elliott Perhaps @StefanTS does not want to set this testing software as the default item for all the systems in his environment? Perhaps he only wants to set it for a specific group of computers. That’s what I was asking.
Report bugs, request features, or get the latest progress.
as tom says it is quite difficult to explain entirely, but if you understand how hooks work, then access control works in the exact same way. take a look at /$webroot/fog/lib/plugins/accesscontrol/hooks
Access Control works by “UserType” and at the moment the only way you can set this is via database
the idea would be
User Type 0 = Admin
1 = Creator
2 = Editor
3 = Engineer/User
What you are trying to achieve to stop users imaging from one location when they’re at another, would get complex. unless you have certain engineers who will only ever image from one location then you could go down the route of
Type 0 = Image From any location
Type 1 = Can only image from location A
Type 2 = Can only image from location B