Roles configured by default on Drupal Commons clean install
In Drupal Commons 1.1 clean install we have just two(2) additional roles:
- 1. DRUPAL_COMMONS_MANAGER_ROLE (community manager)
- 2. DRUPAL_COMMONS_CONTENT_ROLE (content manager)
During the installation process the firts role (1) is automatically assigned to USER-ID 1
The second role is not assigned to any specific USER or module permissions, for what I can see in the drupal_commons_perms.inc file that is included_once during the installation process.
As Drupal Commons main task is to allow an out of the box Drupal distribution for building a Social Commerce Community I though that it would be interesting and usefully if we do add
some additional ROLES with the appropriate permission settings by installation with the use of the drupal_commons_perms.inc.
I could imagine that following roles might be worth consideration:
- A. DRUPAL_COMMONS_ADMIN_ROLE (Site administrator) implication to change assignment in the default install profile file.
- B. DRUPAL_COMMONS_MANAGER_ROLE (community group manager)
- C. DRUPAL_COMMONS_CONTENT_ROLE (Community group content manager)
I'm working to test this and will report back. Meanwhile would be interesting what you think.


Comments
group manager role
We are looking to have the group admins be able to manage all the content within the group - allow them to edit any content types that have been entered within the group (i.e. documents, blogs, discussions, etc). Is that what you were thinking in your group manager role and if so, how did you give them permission to edit the documents only within their group?
Thanks.
Interesting question
I have some experience now with the complex and not always easy configuration of roles and permission settings.
During my testing with trying to integrate DRUPAL-COMMONS and DISPLAY-SUITE I face the problem that I fine grain of permission for view, update, create, delete for users
could be implemented with TAXONOMY ACCESS. And I can say that it works, meanwhile on my Local Test and Development Host.
The next will be to extract all the Roles permission settings and Taxonomy configuration as to integrate that in the Drupal-Commons installation profile and give it a run.
Some notes
In my post I did made some unwanted mistakes. Sorry for that I'm still a newbie in build full clear understandable post.
1. I missed to mention that in the Drupal Commons package and exactly in the root folder ./profile/drupal_commons you will also find a file named drupal_commons_perms.inc .
This file contains all permissions setting that will be configured/implemented on the fly by installation.
So with a bit of testing and changing you may in the position to custom for your needs.
purpose of user 1 assigned to community mgr
"During the installation process the firts role (1) is automatically assigned to USER-ID 1"
Please confirm that the reason user 1 is assigned the community manager role is so the admin role has access to the WYSIWYG full-html editor. I can't see any other reason. Is there any?
No it's not only reason
With assigning the USER-ID1 to the Community Manager means that Any users that you will be assigning the role "Community Manager" will have all permission are set by default after clean install.
You can see those additional permission under the column of "Community Manager" role when you go to admin/user/permissions/3
Because many newbies user get easily confused about user permissions and roles I post an issue to Drupal.org Drupal Commons Issues:
Pledge for additional administrative role for Drupal Commons
My motivation due to help newbies for distinguish best around Roles and Permission which is a very sensitive and security aspect for building Community site IMHO.
So if you find that you get confused post your support for the issue.
Thx
Happy New Year