Generally speaking, all the Users you create on your internal, production Artifactory instances will have permissions to deploy new files and delete internal "dev" packages. Meanwhile, the public Edge users will only need read access to these files.
One way to achieve this setup is to have two mission controls. One Mission Control would be for the internal production Artifactory cluster network, and the second Mission Control would attached to an edge node. You could use the Edge Mission Control to manage Access Federation for the other edge nodes in the system. This will not interfere with the permissions on your main production Artifactory instance.
Access Federation would synchronize all the different "read" access public users would need. This way IoT devices and other public accounts would only have access to certain edge node artifacts.
One way to achieve this setup is to have two mission controls. One Mission Control would be for the internal production Artifactory cluster network, and the second Mission Control would attached to an edge node. You could use the Edge Mission Control to manage Access Federation for the other edge nodes in the system. This will not interfere with the permissions on your main production Artifactory instance.
Access Federation would synchronize all the different "read" access public users would need. This way IoT devices and other public accounts would only have access to certain edge node artifacts.