We would like to use Compound Documents for managing user guides and manuals. We understand creating Releases and Revisions but would also like to be able to keep updates to the compound document private untill a new release or revsion.
I've tried using shortcuts and generations (in a different folder) which point the user to the desired release or revision. However, from that release or revision it is still possible to navigate back to the Compound Document and see the work in progress.
Has anyone encountered this issue?
Thanks
Gillian