Hi,
Is there a way to prevent certain users that have access to production Orchestrator from uploading new process packages that they may have been working on in the Dev environment (I know that Orchestrator shows in details who built each version of code but I don’t think this is sufficient for our oversight people who want to prevent it except by publishing via a production robot machine which requires access permission and monitoring.
Other than that we want those users to have full access to add assets/queues/schedules etc.
You can either restrict access to upload packages or give access to upload packages but in relation with the dev orchestrator is something you cannot enforce. And yes people can have access to schedules,assets and queues and you can retrict them to upload packages that is also possible…you have to create appropriate roles and assign to the respective users
Yes I don’t care what happens in Dev. I just want to make sure that packages that were for example created in the Dev environment (or anywhere else) can’t be uploaded to Production. I’ll have to create a new role with only view access to packages I suppose.