Let's Reconnect, thank you for making 2022 our best year yet.

Look Back
Develop, Deploy Journeys using VBCS — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Develop, Deploy Journeys using VBCS

Received Response
17
Views
1
Comments

Summary:

Segregation of duties to developing and deploying Journeys/Redwood pages

Content (required):

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):

22D

Code Snippet (add any code snippets that support your topic, if applicable):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!