When working with multiple environments, it would be good if certain users could publish content to be viewed on dev / staging instances without having the ability to 'Deploy' to live.
Unfortunately, there is no separate user restriction setting for Deploy currently.
If a User (either directly, via a Group or for the granular content / media) has the 'Publish' or 'Send to Publish' permissions available, they also have on the dropdown next to the 'Save and Publish' or 'Save and send for approval' button, in the bottom-right, the option to 'Deploy'.
This makes even less sense when only the 'Save and send for approval' button is present as it means a user can bypass the approval process entirely.
This would be very helpful in enabling users to test their changes and view them as visible in a dev / test / staging environment and then another user (e.g. admin, manager) must activate the publishing to Live once approved.
To phrase this is a question, could this be implemented? Essentially having the 'Deploy' action as a separate permission?
Umbraco Heartcore: Prevent Deploy for users whilst still allowing Publish / Send to Publish (Approval)
Hi there,
I raised this as a feature request on GitHub (https://github.com/umbraco/Umbraco-CMS/issues/8228) but that might not be the correct place.
When working with multiple environments, it would be good if certain users could publish content to be viewed on dev / staging instances without having the ability to 'Deploy' to live.
Unfortunately, there is no separate user restriction setting for Deploy currently.
If a User (either directly, via a Group or for the granular content / media) has the 'Publish' or 'Send to Publish' permissions available, they also have on the dropdown next to the 'Save and Publish' or 'Save and send for approval' button, in the bottom-right, the option to 'Deploy'.
This makes even less sense when only the 'Save and send for approval' button is present as it means a user can bypass the approval process entirely.
This would be very helpful in enabling users to test their changes and view them as visible in a dev / test / staging environment and then another user (e.g. admin, manager) must activate the publishing to Live once approved.
To phrase this is a question, could this be implemented? Essentially having the 'Deploy' action as a separate permission?
Thanks :)
is working on a reply...