Publish a configuration to only one destination

jsmith's Avatar


21 Sep, 2010 06:01 PM

I'm creating a mobile version of a client site. The content for the site will mirror the content on the full site, but will have a different template and possibly formats applied to generate a mobile friendly version. The new site content will also get published to a separate subdomain from the main site.

My plan is to create a new configuration on the existing configuration sets that allows for publishing in the new mobile version. I'd really like to be able to set things up so that the mobile version can only be published to the mobile destination. We can train the users to do this correctly, but there's still a pretty good chance that we'll end up with the wrong content configuration on the wrong server at some point.

Is there any way to limit which destination(s) a configuration can be published to? Has anyone else created a mobile specific version of their sites, and if so, how did you configure it in Cascade?

  1. Support Staff 1 Posted by Tim on 22 Sep, 2010 05:04 PM

    Tim's Avatar

    Hey there,

    The only way to limit destinations at the current time is by using the Applicable for Groups field to allow or disallow certain groups of people from publishing. So, if user A is in group A and group A does is not one of the applicable groups, user A will not see this particular destination when publishing.

    Also, you may be interested in voting on the idea located here.

    Let me know if you have any further questions.


  2. Tim closed this discussion on 06 Oct, 2010 02:30 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac