Workbench Access Installation

Install the module and enable it according to Drupal standards.

Creating and assigning editorial access is a three-stage process:

1. Define the access scheme.
2. Designate the active editorial sections.
3. Assign editors to the appropriate sections.

The section structure itself is always controlled by another module (both Taxonomy and Menu modules are supported). Since Drupal already has tools for managing hierarchies, it is not necessary to create another. Instead, we try to use existing site concepts and workflow to enhance your editorial options.

After enabling the module, you will be asked to configure its settings. On the configuration screen, you may choose to install a test vocabulary. This vocabulary will help you learn how Workbench Access works.

When you install the test vocabulary, it will create a test access scheme for you. This scheme is called 'Museum' and it is created as a Taxonomy vocabulary. (It has a machine name of 'workbench_access', however.)

You should be able to view the structure at the path:

Admin > Structure > Taxonomy > Museum

You may use this to build your access hierarchy if you wish. Simply edit the term names to reflect the real use-case for your site.

The created hierarchy mimics a Museum web site, divided into three sections, each of which has child sections for Staff and Visitor pages:

• Museum
  • Exhibits
    • Staff
    • Visitors
  • Library
    • Staff
    • Visitors
  • Gift Shop
    • Staff
    • Visitors

All existing site content will be assigned to the top-level section.

By default, user 1 (the administrative super-user) is assigned to the top-level section, giving this account access to edit all content.

Note that when you install the module, users who are not assigned to an editorial section may no longer be able to create or edit content. This is normal. Since Workbench Access now controls who can create and edit content, you will need to configure the module before resuming normal site operations.

Dependencies

Workbench Access requires the core Taxonomy module to be active on your site.