# Summary

The Workbench Access module creates editorial access controls based on hierarchies. It is an extensible system that supports structures created by other Drupal modules.

When creating and editing content, users will be asked to place the content in an editorial section. Other users within that section or its parents will be able to edit the content.

A user may be granted editorial rights to a section specific to his account or by her assigned role on the site. To create, edit and delete content in a section, the user must have the core node module permission (e.g. Edit all Article content) and the content must be assigned to the same section.

As of this writing, the module supports the core Taxonomy and Menu modules for the management of access hierarchies. It uses Drupal 8's plugin system to create new hierarchies.

# Project URL

https://www.drupal.org/project/workbench_access

# Where is the code?

https://www.drupal.org/project/workbench_access/releases/8.x-1.1

# Estimated completion date

May 2016

# Dependencies

Core Node module, plus Taxonomy or Menu modules.

# Who's doing the port?

@agentrickard

# What help do they need?

See the prioritized issue list at https://github.com/agentrickard/workbench_access/issues. We especially need tests.

Comments

agentrickard created an issue. See original summary.

agentrickard’s picture

agentrickard’s picture

Status: Active » Closed (fixed)
webchick’s picture

Status: Closed (fixed) » Needs review

For the purposes of this queue, alpha == "needs review", "fixed" == stable release.

millionleaves’s picture

I just installed Alpha 1 into a fresh copy of the Lighting distribution and, within 10 minutes, I'd replicated a D7 configuration I manage where I use Taxonomy to control which roles can create/edit content of specific content types. Use case is a master franchise website where franchisees have their own multi-page sub-site inside the site and can create content within their own sub-site but not outside it.

I experienced no issues whatsoever.

I'm sure you've got more work to do before this reaches a release state, but on the basis of what I see here, I could use it in production today. In fact, I'm now thinking hard about doing just that.

Thanks!

agentrickard’s picture

We're about to deploy to production as well. The issues list for a stable release is pretty small.

https://github.com/agentrickard/workbench_access/issues

The big missing piece is tests, so any contributions are welcome.

begun’s picture

Is there any work on an upgrade path from Drupal 7 to Drupal 8? I am trying to figure out how to do it in this issue: Upgrade path for Drupal 8

agentrickard’s picture

avpaderno’s picture

Issue summary: View changes
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.