cancel
Showing results for 
Search instead for 
Did you mean: 

How different users can see different folders under the same root folder?

Former Member
0 Kudos

Hello,

I have a KM root folder and 10 folders below it.

Each folder below the root folder has different authorizations, for example:

Folder A under the root folder has full control permissions to user User1

Folder B under the root folder has full control permissions to user User2.

I would like that both of thse users will see the root folder but when each one of them navigates inside the root folder he will see only the folder/s that he suppose to. At the example above, User1 will see folder A and User2 will see folder B.

The problem I am having is this: In order for both users to see the root folder at all they need authorizations on the root folder, but once I do this these 2 users see all the folders below this folder and not just the subfolders they suppose to see which is not good.

My question is: How can I accomplish this than?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Roy

I think that you can set Everyone to have read access to the root folder, but give Everyone None access to the folder udner there.

Cheers

Former Member
0 Kudos

Hi Michael,

I've tried that, once you give any user or group (including Everyone) read access to the root folder they see (and read) whatever inside this folder even if no access for these users/groups was given to the subfolders...

Message was edited by:

Roy Cohen

Former Member
0 Kudos

Whoops, I was getting mixed up with PCD folders!

Looking at /userhome, they have the same idea. The difference is that they have given Full control to everyone.

For examle, if you navigate to http://myportal:myport/irj/go/km/navigation/userhome, you only see your own folder.

Cheers

Former Member
0 Kudos

I can see that too but yet it's not working for me...

I assume they made code adjustments to this folder for runtime access, unless you see there something I should have done and didn't do correctly

Former Member
0 Kudos

I have noticed a strange thing now:

I am presenting this root folder in a standard KM iView.

If I create these permissions for 2 folders directly under this folder it is working, meaning user1 sees folder A and user2 sees folder B.

But, if I go one level down, meaning doing this inside 2 folders which are located inside a folder which is below the root folder it doesn't work.

Any explanation for this phenomenon ?

Roy

Former Member
0 Kudos

I don't think there any adjustments, I think it is behaving as expected.

Is this a folder in your own repository, or a folder under an existing SAP supplied repository? Have you got any strange service permissions? Do you have an ACL manager (if it's your own repository)

When you say that two levels down doesn't work, does this mean that the permissions aren't what you expect?

/top

/top/folderA - name seen by user 1

/top/folderB - name seen by user 2

/top/folderA/xxx - what happens here?

Cheers

Former Member
0 Kudos

Exactly:

Assume I have a KM iView that strats presenting the content from folder /top

If I create two folders below it (folder /top has permissions full control for everyone) and set permissions I get the results I need as you described:

/top/folderA - name seen by user 1

/top/folderB - name seen by user 2

But, if I create folderA and folderB under /top/someFolder (and at this case both folder /top and folder /top/someFolder has permissions full control for everyone) and do the same it doesn't work, both users see both folders.

Roy

Former Member
0 Kudos

Hi Roy

Do you have any special service permissions on /top/someFolder or maybe an approval process? There are a few things that cause read access indirectly, such as being the approver of a document.

Cheers

Former Member
0 Kudos

Hi Michael,

someFolder was created under /top folder therefore it inherited all it's permissions from it (including Service permissions).

Other than that I haven't made any changes to this folder, simply created it

Roy

Former Member
0 Kudos

Hi Roy

Can you try setting the permissions specifically on /top/someFolder instead of inheriting and see if that makes any difference?

Cheers