I am trying to lockdown few schemas to specific groups. e.g; Schema "SuccessStroy" will not be aviable to "GroupB". I applied the permissions to the folder where the schemas exist. The folder permissions are in such a way that "No Read" access to the "GroupB". I have the hide organizational items enabled set to true.
From GUI, when GroupB users login and try to create the component they see the schema "SuccessStory" in the drop down, but when they select they see a message "you do not have access ..". So the permissions for sure are correct, but However when the drop down displays for some reason it is not respecting the permissions and still giving the option to users to select the restricted schema.
Anybody experienced this behavior.?
Environment: Tridion 2011 GA + HR 1, Windows 2008 R2 Sp1, .net 4.
Note: The behavior is not just limited to schemas, I have noticed the same for Page Templates and Component Templates.
This is a defect on 2011 GA, I am not sure if there was a hotfix, but it was definitely fixed on SP1.
I couldn't find a hotfix that specifically addresses this issue, might be worth checking with Customer Support if you need a hotfix before upgrading.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With