Organic Groups Integration

How would this be different from the toolset that OG gives you now?

Do you need to define Groups as Workbench Access sections?
Do you need Group-based Views into content administration?
Do you need Group-based content moderation?

What features are you referring to as 'Workflow'?

In terms of editing and moderating, Workbench gives you this split structure, if you desire.

What it doesn't provide (yet) is OG-style segregation of content when its being Viewed.

You might, in fact, be able to use Workbench Moderation with OG to provide the separation you want. Otherwise, you'd want to use Workbench Access and Workbench Moderation, and we'd have to know if you need content separation for different site visitors.

It likely will be, as it is almost trivial to implement. You should open a feature request for that.

The scenario you describe should be possible with Workbench Access and Workbench Moderation, eliminating Organic Groups. Your editors would belong to WA editorial sections, and have appropriate permissions as set for the two modules.

I view content separation on 'View' for public users a different issue than group publishing rules.

My suspicion is that implementing these feature may remove the need for OG in some cases.

What happens if you instead integrate an OG view into the Workbench panel, and skip Workbench Access entirely?

That would require a little bit of code, but might be the better direction.

I'm not sure. I just saw that agentrickard asked a question that wasn't answered.

What happens if you instead integrate an OG view into the Workbench panel, and skip Workbench Access entirely?

+1 for integration between OG and Workbench. Each Group should behave as though it has its own Workbench ruleset for access, workflow, etc. IMHO.

Also, does it make sense to ask about integrating Workbench with Rules?

Thanks.

@lloydpearsoniv

Wow. That was entirely unhelpful.

I asked for a clear list of the features you wanted _because_ we don't understand what you're asking for. If you can't explain it, we can't support it.

In the meantime, you might try http://drupal.org/project/revisioning

I thought I asked pretty clearly, but then, I've been asking the same questions in a bunch of separate issues.

I think much of what you're after is detailed here #1096530: Same user, different role in different sections, which went through a very similar process.

From the dev side, we get equally frustrated with people asking for "features" that aren't really defined.

The "control panel" idea, in particular, needs a lot of work. Even a sketch on a napkin would be helpful. See http://drupal.org/node/1096530#comment-4544498 for example.

My suspicion is that what we need is to finish those issues and then provide a "groups" access type that allows the group to be the access control container.

That plugin should be fairly simple. However, I suspect that's not what you're ultimately after.

Are you looking for taxonomy-based access controls within the larger context of a Group? Or is the group itself the defining container?

Right. Thanks. That's a tough UI challenge, because it also involves Workbench Moderation.

I wonder if #1103638: Task plugin for 'admin/workbench' will help support that.

One the plus side, from an Access point-of-view, since we are using string keys, it becomes fairly trivial to support multi-value keys for access controls, such as (GROUPID-TERMID), so we could create hierarchies by group and term at the same time.

Short answer yes, I think further CTools integration could led to support of Organic Groups in Workbench Moderation.

The specific issue with that discussion is #1108502: Allow modules to alter the list of possible next states. My idea here is to allow CTools access plugins to operate on WB Moderation transitions and perhaps the states themselves. Then CTools could use existing OG plugins to allow or not allow a transition or state.

That alone might not meet the use-case you're describing lloydpearsoniv. I think you're suggesting that each Group could have completely separate moderation states and transitions that would be configured at completely separate paths like http://workbench.persch.sandbox/admin/config/workbench/moderation/transi.... Or some path like that. That reminds me of the way Domain Access can "take over" arbitrary admin forms and make their values domain specific.

Do I have that right Lloyd?

Allowing "ALL the options that workbench provides to a site" to be exposed on a per Section level would be really rad. Not literally all of the options of course, we'll have to make a list of which ones make sense.

@stevector @agentrickard Are you guys familiar with Spaces? From the Spaces module's project page:

"Spaces is an API module intended to make configuration options generally avaliable only at the sitewide level to be configurable and overridden by individual "spaces" on a Drupal site."

For starters though, an integration with Group roles as opposed to Drupal sitewide roles would be cool. The goal be to allow a group Administrator to upgrade some specific user to editor in that group. The Workbench Access module would see that a user has been granted group role "editor" and apply a permission scheme that allows them to edit nodes (or change nodes to specific workflow states) in that specific Section. I'm still getting myself familiar with Workbench... it's possible to grant this kind of access for nodes to specific users on a per Sections basis using Workbench Access right? The catch I think is that this is administered on a site-wide level so some Super Admin that is trusted not to mess with the wrong Section is allowed to manage their section in the site-wide Section manager.

Not a fan of Spaces / PURL. Doesn't exist for 7.x, either. Use it if you prefer.

Also not going to allow "privilege escalation" per group. That's just a non-starter. See #1096530: Same user, different role in different sections for that debate.

I think, however, that most of what you're looking for is being worked over in #1155692: Allow per-section CRUD permissions, which allows fine-grained node access controls per content type and section.

[Removing tags. See http://drupal.org/node/1023102]

Subscribing.

I've looked over workbench and perhaps the easiest way to integrate this with OG would be to add OG membership to the Workbench Access settings options. Where there is currently 'menu' and 'taxonomy', add 'organic group membership'. I'll put this into the Workbench Access queue, and you can close this one if you agree that that is where it belongs.

Thanks!

Let's leave this ticket open because there has been some discussion of using og within wb_moderation too.

Hi Robeano and the rest of ppl,

I'm in a similar situation as lloydpearsoniv, I need to create groups for different organizations in different cities, and each one will manage their own content, to do so I think that Workbench and OG would be a perfect match.

anxiously waiting :DD

Cheers,

Alejandro

+1

This is what the best solution would be - adding group membership to the access settings

Can we integrate Workbench module with the admin crud. Is it possible to manage different content types separately along with the workbench module features.

Please suggest whether it is possible or not and if yes then how?

I don't understand the question. You are speaking in shorthand.

Sorry for bieng so concise, what I wanted to know is that we develop sites and give an Admin CRUD to the client to manage all the content types, so my question is when we use workbench module it provides a great dashboard Interface to manage the content but using workbench we can manage all the content types in general as the drupal core feature provides,so is it possible to manage each content type separately as we do using admin CRUD,say for wxample Manage Page,Manage Article,where user can manage page content type CRUD(Create,Read,Update,Delete).
So is it possible to get such admin functionality integrated with Workbench module,because I actually liked the Interface n easy access of content provided by this module.

That question is totally off-topic for this issue.

The following module integrates OG with Workbench Moderation, allowing group roles to have permissions to move content only inside their groups. http://drupal.org/sandbox/hernani/1788510

It looks like sandbox project linked to in comment 37 is now a full project.

Is this issue still relevant?

@bonobo Only to help people find the right answer without filing duplicate support requests.

Should we mark it as fixed then so people can find it but also know to skim to the bottom where they can find the solution in #37?

seem reasonable.

The link above still works, but the full project is at: https://www.drupal.org/project/workbench_og