Assumption 1. Many modules outside of OG rely on Sitewide Roles.
Case 1: Blocks - Role specific visibility settings.
Case 2: Views - Basic settings - Access restrictions - Roles.
Case 3: Permissions - to provide access to view/display content

Assumption 2. Not all content is posted into an Organic Group, and thus often Group Roles don't apply.

Problem:
I often find myself outside of 'group scope'.

Solution:
If someone is accepted into a particular group I would like to automatically assign them one or more Sitewide Roles. This is would allow for cases when roles should extend beyond the limits of OG's scope. With clear documentation the difference between assigning a Group Role and Sitewide Role should not be to confusing.

Example: Joining Group A automatically assigns you to Sitewide Roles B and C. Leaving Group A revokes Sitewide Roles B and C.

My Environment:
1. Super admin has complete control over the creation of new groups (currently only 3 groups).
2. Super admin has complete control over accepting/rejecting join requests.
3. For Group 1 and Group 2 (but not Group 3), new users should be assigned Sitewide Role A, so ONLY THEY can view a particular Block, access a custom View, and view a particular page... all this 'content' is outside of OG, but I use OG to manage User Groups... it seems Sidewide Roles are the missing link.

Your thoughts?

Comments

i.chris.jacob’s picture

i.chris.jacob commented

I wonder if this could be done using the Action.module and Trigger.module?... Does anyone have experience? Thoughts?

somebodysysop’s picture

somebodysysop commented
Assigned: Unassigned » somebodysysop
Status: Active » Closed (won't fix)

Doesn't the OG Roles module already do this? Back some 2 years ago, the reason I decided to write OG User Roles was because the existing OG Roles module only added sitewide roles.

OGUR does have one setting to assign a site-wide role to any user joining any group, but that's as far as I think this module should go with this. The problem we run into is that ogur is an og module designed to operate in og group context only. Once you start assigning site-wide roles, you run into the potential problem of someone in a group being able to assign a site-wide role to himself in order to give himself permissions you don't want him to have.

I think you should look into actions or triggers for this functionality because it appears to be outside the scope of ogur.