Return to Jive Software

Up to Discussions in Feature Discussion
1,179 Views 1 Replies Last post: Jul 8, 2009 12:20 PM by Karl Cyr RSS
mbehr Novice
mbehr
14 posts since
Aug 7, 2008
Currently Being Moderated

Jul 8, 2009 10:44 AM

Discussion/Document/Poll Editing

When a user creates a poll, discussion, or document, he/she may edit the question, content, etc. and any other user's comments. This seems highly problematic. For example, if the poll was "Do you agree with Obama," and the users vote 99% Yes... the creator can then go back and change the question to "Do you disagree with Obama"... and the poll results stay 99% Yes.

 

Also, for comments on any of these items... if I created the piece of content, I can edit another user's comment. So, if I leave a comment on a Document, the Document creator can change my response (w/o me knowing, thereby putting words in mouth).

 

What's the use case here? Why are creators allowed to edit their question or others' comments midstream in collaboration? Is there any way to stop this functionality in the Admin Console?

 

Thanks,

Mike

Tags: discussions, documents, polls, editing
Karl Cyr Jive Employee
Karl Cyr
6,481 posts since
Mar 12, 2008
Currently Being Moderated
Jul 8, 2009 12:20 PM in response to: mbehr
Re: Discussion/Document/Poll Editing

Hi Mike,

 

At this time, that is how the permissions are structured. The design is that content owners should be able to administer their own content. Yes, there is potential for abuse as you describe, but the assumption is that the community will be monitored by fellow members and System Administrators. There is potential for abuse any time content is posted to the system. In reality, the far more common use case would be that a poll creator would discover s/he made a typographical or semantic error on the poll, and return to edit the poll to fix this mistake at a later time.

 

Regards,
Karl

More Like This

  • Retrieving data ...

Bookmarked By (0)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.