We have a requirement to provide the production URL to the client, as they don't have preview internal page access, and let the client review the prod page before we finally mark it as ready for all. How can we achieve this in Tridion?

  • Your requirement is not really clear to me. Sounds a bit like a typical Staging / Live configuration? Mar 19 '19 at 18:20
  • The client want to review the content page in prod region, as they cannot access the lower region page externally. Once they review it in prod region, then only they want us to release it for public use. Hope this makes sense.
    – Sikarwar
    Mar 19 '19 at 21:08
  • Makes perfect sense, and that's why you'd normally setup a "Staging" environment - potentially with Experience Manager enabled, but let's go one step at a time...
    – Nuno Linhares
    Mar 20 '19 at 6:30

What Rick had suspected, you have confirmed with you comment, this is indeed a typical staging/live setup. That means, that for a single CM environment (Production) you have 2 delivery environments (Staging and Live). They both have their own Content Delivery stack and Content Data Store, and you can publish to either of them independently from the other.

Because Staging is not publicly available, one of the main reasons for using it is indeed reviewing. And because you're publishing from the same CM environment, the same templating and content is used, so the resulting item on the staging site will be as close to the live one as possible. Once the reviewer is satisfied with the outcome, the same item can be published to live, making it publicly accessible to others.

You have tagged the question DXA 1.7, so I'm guessing you're using Web 8 or higher (SDL Tridion 2013 SP1 is only supported up to DXA version 1.6.). See the following links for additional information and how to achieve this in Web 8+:


Next to what Atila said, DXA also provides some specific support for Staging / Live configurations:

  • It provides a pre-defined "Staging / Live" Business Process Type (and associated Topology Type)
  • It ensures that XPM markup is output when publishing to "Staging", but not when publishing to "Live"
    • Experience Manager (XPM) is typically used for reviewing and in-context editing purposes on a "Staging" environment

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.