Develop, Deploy Journeys using VBCS
Segregation of duties to developing and deploying Journeys/Redwood pages
I have a query on how can we control that developers only perform personalizations for the redwood pages or Journeys module in the project/workspace and should not be able to deploy to higher instances.
For migrating the same project/workspace, only the admin person should be able to migrate to higher instances including production.
Version (include the version you are using, if applicable):
Code Snippet (add any code snippets that support your topic, if applicable):