Hi,
I have 2 contexts 'web' and 'site2'
I wanted some manager users to only be able to edit resources in the site2 context.
I've set up a 'site2-editor' user group and only added context access for mgr and site2, which sort of works until you come to edit a resource under the site2 context. You get an access denied.
What has seemed to of worked is if i add load only access to the web context. Is this how i should be doing it and why does that make a difference.
Ok one problem i'm having with this, is if you just click the create new resource icon the new resource is automatically created in the web context which the user can't see so can move it to the correct parent.
from what ive understood when using contexts the create new document only adds the document to the default context and not the visible context via permissions.
It would be probably be wise to get your site2-editor to right click the context and create new doc instead, a bit of client education.
Is there a a system setting to change the default context on a per context basis.
The problem is you can educate them but there are going to be times when they do create the resources that way and that means there will be a number of resources created in the other context as the site2 editor will be unable to see what they done and delete them. Wouldn't be so bad if they got an access denied error
I dont think so, not that I have seen.
The only thing i can think is to actually remove the shortcuts using form customisation (but thats something well above me)
