Skip to Content
author's profile photo Former Member
Former Member

Authorisations in Content Management folders..Controlling viewing

Hi All,

Need some advice over a situation that I have here in controlling access in Content Management...I am a bit stuck here.

CM Structure

User 1

Folder 1 Group1 Read

Folder 2


Folder 3


Folder 4


Folder 5

Folder 5.1 Group51 FC

Folder 5.2

1) User 1 has FC over folder 5.1

2) Created a group 51 and attached the user to the group

3) For the user to see the entire folder structure, he needs to have a read access to the top Folder. Hence created a Group1 in the top. Attached Group 51 to group1.

Now when the user logs in, he sees the entire structure, but when he clicks on Folder 2, Folder 3 etc...he does not see any content in it, this is because these folders inherit permissions from the top folder.Hence all this folders gets a "read" access. and when the user clicks on to 5.1, he is allowed full control.

However, my client does not want users to see the Folder 2,3,4..If I give Read access in the gets inherited down..if I dont give read access in the top, no one can see anything below.

Since I have a large number of folders in the next level, it is not practical for me to delete read access in the next level.

Any advice on how I can solve this problem.



Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Jan 24, 2005 at 02:26 PM

    Hi Rajan,

    one way to solve this is to implement a ResourceListFilter which filters folder which do not belong to the users area (you have to implement the detailed logic by yourself, e.g. check down the tree of a folder if there is any folder for which the user has full control or so).

    Then create a CollectionListRenderer (copy from the renderer used so far) using this ResourceListFilter. Create a LayoutSet (copy from the set used so far) using the new CollectionListRenderer.

    Hope it helps


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 25, 2005 at 08:59 AM

    Is it feasible in your scenario to simply set the unwanted folders to "hidden" or is it completely ACL-based? With the regular end-user explorers (e.g. ConsumerExplorer), hidden folders won't be shown (this is a setting of the corresponding collection renderer). Administrative Explorers (e.g. Admin Explorer) do show hidden files, though. Note that you can only modify the hidden state with such an administrative explorer. This makes sure that you have at least one way to reset that state and to not hide it in an explorer that afterwards does not show the file and thus would not allow you to reverse that step (in principle this means that users with no administrative accesses whatsoever will never be able to hide resources).

    Regards, /-/ans-Juergen

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.