Users

No I haven’t been able to restrict access to specific pages only contexts, and again I can hide everything in the elements tab the same, but not the tab it’s self, given the relevant names and containing panels I reckon I can hide the tab.

As you say I think only the devs can answer some of the questions and at the moment they are as you say busy a)trying to earn a living, and b)trying to get a rc out.

looks like we might have to wait.

OK done some playing with Resource Groups, these only appear to affect what is and is not visable on the front end and do not affect what pages a given person can edit. I may be wrong on this if one of devs read this maybe they can confirm or deny this so I know where I’m heading on trying to sort this out.

Be carefull when playing with this as I lost a couple of pages when removing them from a group (I think), and I mean complety gone, wiped out of the resource tree completely.

Going to play around with more and track down exactly when they where deleted and file a bug report.

Quote from: BobRay at Dec 10, 2009, 12:48 PM

Have you found a way to restrict what resources show in the tree? Using Resource Groups and User Groups, I can’t seem to restrict users to any subset of the resources.

OK looks like I have discovered how to do this, and thats why they where dissapering in my previous post. Not sure exactly what I did, will work on working out exactly what I did, and let you know Bob

I look forward to hearing about it. I found that stuff disappeared from the tree when I didn’t make the admin a member of the user group, but it wasn’t lost for good.

Yea thats why I think i spotted it they are still in the database, but not in the tree.

So it looks like if you don’t want people to edit a given resource it is not even viewable.

There is a setting in the Configuration to make the whole tree visible, including documents the user doesn’t have permission to access.

Quote from: sottwell at Dec 14, 2009, 04:31 AM

There is a setting in the Configuration to make the whole tree visible, including documents the user doesn’t have permission to access.

OK thanks, have had a look around in system settings and the Access controls and resource group, but can’t spot any setting. Any clue as to where this is.

Quote from: peteedley at Dec 14, 2009, 02:33 AM

Yea thats why I think i spotted it they are still in the database, but not in the tree.

So it looks like if you don’t want people to edit a given resource it is not even viewable.

I haven’t tried it, but you can definitely create a Policy that allows "view" but not "edit."

We definitely need some docs on what those permissions actually do in an Access Policy. I don’t know, for example, whether "view" and "load" affect the tree or the Create/Edit panel, or both. I wonder if a policy permission of "show_in_tree" would make life easier.

BTW, I think the default rule may be that, as in Evo, any document that’s not in a resource group is viewable and editable by everyone. There may be a way you can give users access to the mgr and web contexts and hide resources from them that are not in a resource group, but if so, I haven’t found it.

Quote from: BobRay at Dec 15, 2009, 02:35 PM

BTW, I think the default rule may be that, as in Evo, any document that’s not in a resource group is viewable and editable by everyone. There may be a way you can give users access to the mgr and web contexts and hide resources from them that are not in a resource group, but if so, I haven’t found it.

I have managed to put some docs in a resource group and these then be hidden from people who are not allowed access to the group, but those who do have access to the group can see them plus all those pages that are not in a group.

Yep we deff need some docs on the access policy settings and what each one is.

And on the whole Form customization what fits in to what containers.

Quote from: BobRay at Dec 15, 2009, 02:35 PM

Quote from: peteedley at Dec 14, 2009, 02:33 AM

Yea thats why I think i spotted it they are still in the database, but not in the tree.

So it looks like if you don’t want people to edit a given resource it is not even viewable.

I haven’t tried it, but you can definitely create a Policy that allows "view" but not "edit."

We definitely need some docs on what those permissions actually do in an Access Policy. I don’t know, for example, whether "view" and "load" affect the tree or the Create/Edit panel, or both. I wonder if a policy permission of "show_in_tree" would make life easier.

BTW, I think the default rule may be that, as in Evo, any document that’s not in a resource group is viewable and editable by everyone. There may be a way you can give users access to the mgr and web contexts and hide resources from them that are not in a resource group, but if so, I haven’t found it.

Resources not in a Resource Group are "Public". "load" and "list" are the policy permissions you’ll want in a policy you assign to allow users in a group to see those resources in the tree. "load" means the Resource can be loaded from the database at all, and "list" controls whether it appears when a node of the tree is loaded.