Collaborative editing: restrict access to particular groups of users

al3 - June 29, 2006 - 18:14

Hi there,

My organization's technology division has been looking for some time for a CMS to run the department's intranet. We tried a few open source products, but have recently installed Drupal. We love it, and the response from our bosses has been quite positive.

One of the requirements for our Intranet is collaborative editing of documents and web pages. However, the access to edit, and even to view should be limited on a case by case basis. Press releases, for example, may contain confidential information, and should only be seen and edited by those who are working on it. Another example might be corporate policy documents, that should be readable by everyone, but only editable by senior management.

Drupal Books seem to offer multi-user editing of content, but the access choices, as far as I can tell, are "I can only edit my own" or "everyone can edit everything".

After searching the forums, I see a lot of discussion around what I want to do, but I'm confused by some of the terms that get thrown around, and the varying definitions of book, wiki, etc.

So I'm writing to you. What are my options?
Thanks,
Al3

No ideas?

al3 - July 10, 2006 - 14:52

No ideas at all? I think I'll give the Simple Access module a try. It seems to offer editing based on each individual page.

Taxonomy Access Control Lite

casperl - July 20, 2006 - 15:03

I have a similar requirement and I am trying out thte Taxonomy Access Control Lite module.

http://drupal.org/project/tac_lite

From their write-up:

* Grant permissions based on roles.
* Grant permissions per user. (Give a specific user access in addition to what his/her roles allow).

Hope it helps

Casper Labuschagne
Where am I on the Drupal map on Frapper?

I am using taxonomy access,

gollyg - August 9, 2006 - 10:39

I am using taxonomy access, and have recently enabled the book module for collaborative editing. You have two approaches to controlling the content by role:

  1. editing the permissions options directly (admin/access). This gives some granularity to the types of priveleges, such as outlining etc, but they are more or less applied to all book pages
  2. removing all priveleges from the permissions page, and then setting up a vocabulary for content. Each term will define a level of access. You can then use the roles provided by tax access to allow certain users edit/view/delete priveleges based upon this vocabulary and their role. This means you can lock down individual content and groups of conent very easily. The downside is that you lose some of the aforementioned granularity of the permissions. But from the sounds of things this would suit your organisation?

hth

 
 

Drupal is a registered trademark of Dries Buytaert.