Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By rocketboy37 on
I have Organic Groups currently running smoothly on a local City Government as an Intranet. I have created the groups to represent Departments so each group is a Department. I have several departments created for example Information Technology, Human Resources, and Town Clerk to name a few. Currently all the users have access to each others departments basically all the doors are open anyone can go into Human Resources and look at there content and vice versa and its that way for the entire site. Users don't have to login to look at content either they can navigate the entire site at will but only 12 members and I are allowed to post content. Also the content once posted goes straight to the site there is no editing process or workflow, initially this was enabled but managers didnt like it.
I'm now interested enabling some type of restriction so that only members of the department/group can access that departments content. But i want staff to still be able to access all the public content. Also I want to enable logins so I can manage the Departments a lot more effectively, obviously this is a necessity in order to do the restrictions. I then want users to be able to customize there content, I had bunch of aggregates coming to the site but older generation thought it was to much information so I pulled back to about 2 RSS.
Anyhow, I hope this is the correct place to post this I have the following modules already installed and have looked at countless sites, online videos, and Lulabot for help but nothing gives me the amount of technical detail I'm looking for.
Modules:
-CCK
-Organic Groups (Enabled)
-Panels (Enabled)
-Views (Enabled but not configured)
-Aggregator (Enabled)
-Path (Enabled)
-Calendar (not being used)
Would eventually want Department Events Calendar.
-Flags (not being used)
-Image & ImageCache (Enabled)
-Messaging (not configured)
-Shoutbox (Staff love this module)
-Notifications ( not being used)
-FcKeditor (Enabled)
-Menu Block (Enabled)
-Nice Menus (Awesome module)
-Workspace (Enabled)
-WebFM (About to be replaced with IMCE, because of Issues with WebFM)
-WorkFlow (Disabled)
Websites or books anything you can provide would be most appreciated.
Drupal Rocks!!!
~=> Rocketboy
Comments
_
I'm not sure what the question actually is. To restrict content to a group enable the og access control module and select the nodes visibility right in the node edit form. To enable per group editor type functionality you'll want to add the og_user_roles module.
Clear as 1 2 3....
1- I want to restrict content by department, only members of a department can access there content?
2- I want members to access public content?
3- Users must request permission to be member of a department?
Sorry if I didn't make that clear got carried away explaining my environment.....he he.
_
1) see my previous comment
2) anyone can access public content-- that's what 'public' means, lol.
3) make the membership of the groups closed
Per group editor type functionality
I am trying to set up Drupal to do the same thing for a School of Business.
I'm wondering about the 'per group editor type functionality' you mentioned.
I have set my installation up where all the content can be seen by anonymous users (it's all public), but people who are logged in and belong to a group have edit access to all that groups content. I did this by setting the content types to be "Wiki group post (any group member may edit)."
What kind of additional functionality does the og_user_roles provide? Does it just make it so that you can assign only certain members that edit access and have other group members that don't have that access?
_
og_user_roles makes it so if someone is assigned the 'editor' role it will only be valid within the context of THAT group. They won't have that role outside the group or for any other group unless it's explicit given.