I have a scenario in Tridion like this, with a handful of SGs and pages sitting in the root of a publication:
My requirement is to allow a certain group of users to publish content only from SG A. Ideally they would only be able to see SG A, but this is not a firm requirement.
This is quite straightforward on SG B and SG C, I can set the Permissions to deny read access for the group. However, I don't see a way to restrict publishing access to the loose pages in the root.
So far I've considered the following:
- Publishing rights are set on the publishing target types, so this is not granular enough to handle what I need.
- If I explicitly deny read access on the root for the group, but explicitly grant access to SG A, SG A is still unreachable and throws an error.
- If I set SG A to be a favourite of the users in the group and have them access it directly from the favourites menu, bypassing the root structure group, it has the same issue as in point 2 above.
- I could move all the loose pages into a SG. However, the homepage should still be in the root of the url, at www.clientsite.com, not www.clientsite.com/home or something like that. I could use the solutions provided here: How to override page publish url or path while publishing?, namely URL Rewrite, but this seems like a complicated solution to handle what I'm sure is not an uncommon use case.
- I could also use custom page/SG metadata and a GUI extension, but again, this seems like a complicated solution to handle the scenario.
Am I missing an obvious solution to this scenario? It seems like a simple and common enough use case that it shouldn't require significant development.