Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I'm developing our first Sharepoint site, and have a specific question in regards to the read permission in conjunction with a discussion list.

Well, to begin, I am setting up a sort of knowledge base. There are 15 categories (which are separated into 15 web pages); each category/page has a discussion list in it for a total of 15 discussion lists/boards. I like the discussion board setup because it is easy for a select few individuals (through the contributor permission) to add/tightly control new pieces of information in each discussion list. The regular users come along, see something they want to read more about, and can open it in a new page format.

Here's the kicker, though: NOW it turns out "they" don't want to give the users the ability to reply to the posted information... a discussion list without discussion (don't ask). I've experimented around with announcment lists instead, but don't care much for how they open in a popup. Basically, we want to have all of the regular intranet users only able to read what has been posted by the select few who will maintain the discussion lists (i.e., not post anything to or reply to the discussions we control). Similarly, we will have a discussion list where they will be able to add their own questions and reply to each other. Does the read/restricted reader permissions make it so that they can only read, but not reply? I've searched tons of places but find no specifics on how it applies to discussions.

share|improve this question
add comment

2 Answers

up vote 2 down vote accepted

To answer your question, if users are set to restricted read on the discussion list, they will not be able to reply to the discussions. They would need an elevated priviledge, like a custom permission based off of Read that allows them to Add list items in order to reply. This then makes it so they can't edit anything or delete anything.

Rob's suggestion of wiki pages would be better, you basically are pushing out content to people to read. You could give them read access to the whole site except for a separate discussion board where they could have higher permissions to discuss information on the wiki pages in the site.

share|improve this answer
    
I am experimenting with the wiki page library right now (never tried it; tried Enterprise Wiki for the past couple of weeks and hate it). I am liking the wiki pages in the library, but, unfortunately, I am not the one that will be maintaining the site; the reins are being passed fully to the contributors for this FAQ-style knowledge base. I like discussions because they place everything in a neat, small package where the contribs won't be wantonly creating new, uniquely-titled pages in question format, then having to link to it. I may change my mind. We'll see. –  user4517 Aug 23 '11 at 20:06
    
Well that's an IA thing you'll have to figure out based on your requirements and what works for the users and the content creators and maintainers. –  PirateEric Aug 23 '11 at 20:28
add comment

That sounds like a Wiki to me. Just create 15 Wiki pages and set the folks you want to contribute and the folks you want to read.

share|improve this answer
    
That's the easier method. –  PirateEric Aug 23 '11 at 19:51
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.