2

I have a simple problem of permissions. I work in a company which is divided into different sections. I have to make a Drupal intranet for them.

Each section must be able to manage their own content on the Intranet. The contents of the intranet are always the same, ie the same "content type" with the same "fields". It is necessary that a section could only edit the contents within its section. Thus, "computer" could only create / edit / delete content of "computer". The section of "press" could only create / edit / delete content of "press". All sections can view all content.

I tried different modules. "Field permissions", which lets you field level permissions, is interesting but does not help in this case. "Content Access" allows me to level management content type, but I can do what necesito.Con "Taxanomy Access Control" can define visibility rules, editing and deletion according to the presence or absence of one or more terms a taxonomy. It could be interesting, was not that "computer" should not be able to create content "press", for example.

You could create a content type for each section equal, and each give the required roles. The problem is that they are over 15 and does not seem the most optimal way to do this, because if I have to add a field so I have to do in the 15 (DRY).

I sense that Drupal has a more efficient way of doing this, but as I am new to this CMS I can not find it.

1
  • 1
    Taxonomy Access Control was good for me. What exactly you need that cannot be done with it?
    – Mołot
    Jun 26 '13 at 8:38
1

The thing you are looking for is Organic groups. It does exactly what you need. Further more you may be interested in some solutions already made on drupal. Like Open Atrium or Drupal Commons

Hope it helps.

0
1

The Group module allows for creating arbitrary collections of your content and users on your site, and grant access control permissions on those collections. It is available as of D7, and has a D8 version also. It is designed to be an alternative to Organic Groups. The Group module creates groups as entities, making them fully fieldable, extensible and exportable.

For this specific question, you'd enable the gnode submodule, and for each group type you would define the appropriate permissions (view, edit, delete, etc) for the various Content Types. That's it.

For more details about the various types of roles used by the Group module, refer to my answer to "What are the various roles supported by the Group module?".

Resources

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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