join   login
Close

Permission list to View and Edit page

It would be very nice to have 2 permission lists, one for View a specific page, and another to Edit the page.

This way you can restrict the people who can see the page, and the people who can edit the page.

hpcorona submitted 759 days ago to Deki Wiki
9 comments - 1 person says it's been done
Official response
  • 13 points
  • DONE
The Deki Wiki Team - Official Response - 291 days ago
Available in MindTouch 2009
coreyg - 759 days ago
Permissions are included to make a page view only or edit only, plus there are roles that you can create to assign to people so that they have view only for the whole system. Also in our next release we are coming out with internal groups so that it is even easier to permission
hpcorona - 759 days ago
When i define a permission, it has 3 different types:

Public - Anyone can edit and view.
Semi-public - EVERYONE can view, but the selected users or groups can edit.
Private - Only selected users can view AND edit.

These 3 options are great, but i need to restrict access to a Knowledge Base, so i need something like this:

Semi-private (maybe) - Some people (list A) can only VIEW, and other people (list B) can VIEW AND EDIT.

This way i can restrict access for both options separately for a SPECIFIC page (not the whole system): a list of users that can VIEW and another list of users that can EDIT a specific page.

Is this alreary done? is there a Wiki page where i can find information on how to implement this? Or is it included in the next release with the Internal Groups support?

Thanks :D
coreyg - 759 days ago
Just to clarify, you are looking at being able to say for a page or set of pages: 1 group can edit and another group can only view. Correct?
hpcorona - 759 days ago
That is correct :D
marcoya2 - 738 days ago
Yes, I think that lake of adequat access restrictions can be a stopper in controlled environments.
In fact, actually we don't consider Roles in page restrictions. I tried to add people with VIEWER Role to "Private" and they are able to Edit, even they have a more restrictive role assigned, because of the definition of Private, and not of the group/user role.

If we would consider Roles then you could assign the wanted roles to groups, then use groups to control.(it's the same with users roles which are not considered).

Imagine a user is Contributor on some pages, but should only be viewer on others.

If roles are considered, then by creating a group "Contrib_on_A" and "View_on_B", assign group "Contrib_on_A" -> Contributor, assign "View_on_B" -> Viewer, then use the groups in "Semi-Public" or "Private" Page restrictions.
If the roles are considered, the Role would then dictate what you can do.
coreyg - 758 days ago
Gotcha...I'm sorry for the confusion, this is something that we are working on but will not be out in our next release. Thank you for the submission
hpcorona - 758 days ago
Cool :D

This product is great, the best Wiki system we've used.
shware - 540 days ago
This looks kind of old but I'm just playing around with the product. It would be great if 2 sets of permissions could be defined for an article - one for visibility and one for editability. Current model is EXTREMELY limited in an enterprise wiki environment.
mdolf - 439 days ago
I agree. Where things get tricky is when you want some viewers to edit certain pages while at the same time other users should only view those pages but without giving access to ALL users.
Groups are great but with the 'public' and 'semi-public' settings you cannot restrict viewers to certain groups.

Thanks
© 2007 FeVote - Terms of Use | Privacy
Blog | Contact