cancel
Showing results for 
Search instead for 
Did you mean: 

Details dialog not available without write permission on folder

Former Member
0 Kudos

Hello Forum,

we created our own repository and provided access rights for consumers and authors.

My issue is that consumers, who have only read permission on a folder, can not access the details dialog, while users having write permissions can.

The menu item itself is avaliable in the Layout-Sets we used, so I believe it's not a rendering issue.

And also strange regarding service permissions:

- for the consumers, we provided the service permission "Subscription user", but not "Collaboration". Nevertheless the "Feedback" and "Rating" options are shown on resources. They should not, since these two are Collaboration services?

- we need the Details dialog because we'd like to provide Subscription service to consumers. And Subscription is only available through "Details -> Action -> Subscription", right?

As mentioned we provided the service permission "Subscription user" but no details dialog option nor any other subscription menu option is shown.

- by the way: for authors, who have write permission and can access the details dialog, subscription works fine.

Thanks in advance for any hint.

Carsten

Message was edited by:

Carsten Schö

Accepted Solutions (1)

Accepted Solutions (1)

sascha_tubbesing
Contributor
0 Kudos

Hi Carsten,

the missing Details command is a bug and will be solved with SPS12 of NW2004s.

Regarding the Feedback, Rating, Reviews, Discussions and Personal Notes the behaviour is the following: to create these only Read Permission for the resource is neccessary.

The Collaboration Service permission is only to give somebody with Read only the possibility to "moderate" these things. See SAP Note <a href="https://service.sap.com/sap/support/notes/515942">515942</a>

In SAP class EP300 we teach these topics.

Regards,

Sascha

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Sascha,

thanks for your reply and sorry for the delay, I was on another topic for some time.

Regarding the bug it's clear to me now. As I mentioned we helped us out by a copy of the Layout-Set. I have to admit that this is not the most clean approach because now it's not controlled by permissions any more, right?

About the "Collaboration Permission" I still have a question: It's ok, that users with read permissions can access these services, but only when they have the collaboration permission also, right? Is this another bug which will be fixed in one of the next SP?

I mean, if read only permission is needed, what are is the purpose of the collaboration permission? Moderation only? Or is the restriction of collaboration services not intended for KM users, i.e. all KM users should have the right to participate?

sascha_tubbesing
Contributor
0 Kudos

Hi Carsten,

without any service permission and only the read resource permission a user can give feedback, start discussions on folders/documents, write a review and rate.

Now think of a situation where a huge discussion is going on for a folder and you want have a moderator for this discussion. Moderating means deleting posts from other users, and even if there are already replies to the post.

A user with only the read resource permission and nothing else cannot do this. You could give one of this users read/write resource permission, but then this user is also an "author" in some scenarios, which means he can change the document and its properties or submit a document for approval.... If you don't want to have this, you can give one of your read-only-users the Collaboration service permission. Now he is a "moderator" but not an "author".

So, yes, the collaboration service permission is just for moderating. Nothing else. And thus only needed in rare cases, I think.

And yes, all KM users should participate in ratings, reviews and so on.

If you want to restrict the use of some of these functions you can change the properties of the respective UI command itself. In the property "Roles with visibility" of the UI command you can enter a portal role and only users with those roles can access the UI command. For example you create the role "Rating" and enter it into the "rating" command. Only user with this role will then be able to rate documents all over KM.

I hope this made things a bit clearer

Regards,

Sascha

Former Member
0 Kudos

Hi Sascha,

thank you, that made it clearer a lot.

Given the precondition that collaboration should not be restricted in general especially the last part of your answer is very helpful.

The reason for this part of my question was that the online help somehow confused me the first time I read it. But I just checked again and the purpose of the permission is stated very clear in the help file.

Thanks again,

Carsten

Former Member
0 Kudos

Hello,

we solved it by adding the desired subscription command to a copy of the UICommandGroup which is now used within a copied Layout-Set.

Anyway, this is not what we wanted because the way we provided permissions the command should've been available.

Any idea about that behaviour?

Thanks

Carsten