PHPackages                             localgovdrupal/localgov\_content\_access\_control - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. localgovdrupal/localgov\_content\_access\_control

ActiveDrupal-module

localgovdrupal/localgov\_content\_access\_control
=================================================

Creates access control mechanisms so specific editors can only edit specific sections of the website.

1.0.0(2y ago)01.7k↓100%[1 issues](https://github.com/localgovdrupal/localgov_content_access_control/issues)GPL-2.0-or-later

Since Nov 3Pushed 2y ago8 watchersCompare

[ Source](https://github.com/localgovdrupal/localgov_content_access_control)[ Packagist](https://packagist.org/packages/localgovdrupal/localgov_content_access_control)[ Docs](https://github.com/localgovdrupal/localgov_content_access_control)[ RSS](/packages/localgovdrupal-localgov-content-access-control/feed)WikiDiscussions 1.x Synced 1mo ago

READMEChangelog (1)Dependencies (2)Versions (3)Used By (0)

LocalGov Content Access Control
===============================

[](#localgov-content-access-control)

Thanks to Essex County Council for funding this module.

This module adds access control to your LGD site sections, which allows you to restrict editing/publishing/etc actions to subsets of users.

It uses the workbench\_access module as its base.

New role - Devolved Editor
--------------------------

[](#new-role---devolved-editor)

With this module we are introducing a new role to LocalGov Drupal: "Devolved Editor". This is a role we can use to allow a subset of editors (perhaps people from outside of our organisation) to create/edit only a small amount of content. By default they can create news, events, service pages and can edit existing subsite overview and service landing pages, but not create new ones.

How to use this
---------------

[](#how-to-use-this)

### Install this module

[](#install-this-module)

Firstly, install this module. This will install the workbench and workbench\_access modules as well.

### Set up your access control taxonomy

[](#set-up-your-access-control-taxonomy)

Following that, you will have a new vocabulary called "Access Control". You can set as many taxonomy terms in here as you wish. Each one will be equivalent to a site section that a subset of users can edit. This vocabulary, like all in Drupal, is hierarchical. What this means for content access is that if you are added to a parent term, you automatically get access/edit rights to all of its child terms.

Let's the the following as a sample taxonomy:

```
- Adult social care and health
- Children, young people and families
- - Children and young people
- - Social care
- - Adoption
- - Fostering
- - Health and wellbeing
- Schools and learning
- - School Admissions
- - Early years and child care
- - Post-16 options
- - Adult learning
- Jobs and apprenticeships
- News
- Events

```

In the above scenario, if an editor is tagged with "Children, young people and families" then they can also edit "Social care", "Adoption", "Fostering", etc. However, if someone is tagged with "Fostering" only, they cannot edit "Adoption", "Social care" etc.

### Add "Access Control" field to content types

[](#add-access-control-field-to-content-types)

By default, we have added the "Access Control" field to Subsite Overview, Subsite Page, Service Landing Page, and Service Page content types. **Note**: make sure to go to the "Manage form display" page for these content types to make the field visible to editors.

If there are other content types you want to add it to you can follow the same pattern we have for the items above.

### Add editors to site sections

[](#add-editors-to-site-sections)

Finally, you can go to the workbench access settings to define which users are assigned to which site sections. This can be found at `/admin/config/workflow/workbench_access`. We have created one "Scenario" called "Site Section" which uses the "Access Control" taxonomy. You can add more scenarios if you need them (you probably won't). Click on "Site Section" and then on the next page beside each site section click the link for "Editors" to manually add each editor to each site section.

#### Role based access

[](#role-based-access)

When on the "Site Sections" page, you will also notice a link beside each site section for "Role". Using this interface allows you to add *all editors* with a certain role to a site section. For example, you might add all editors with the "News editor" role to the "News" section in our sample taxonomy above.

###  Health Score

26

—

LowBetter than 43% of packages

Maintenance27

Infrequent updates — may be unmaintained

Popularity17

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity43

Maturing project, gaining track record

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

2

Last Release

917d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/135fe190210b35fbde2ecd82d36b7babd12202595e4c5a705b57c9dc9c0eea6b?d=identicon)[markconroy](/maintainers/markconroy)

### Embed Badge

![Health badge](/badges/localgovdrupal-localgov-content-access-control/health.svg)

```
[![Health](https://phpackages.com/badges/localgovdrupal-localgov-content-access-control/health.svg)](https://phpackages.com/packages/localgovdrupal-localgov-content-access-control)
```

###  Alternatives

[govcms/govcms

GovCMS Drupal Distribution

18997.1k3](/packages/govcms-govcms)[az-digital/az_quickstart

Arizona Quickstart

50234.3k2](/packages/az-digital-az-quickstart)[palantirnet/drupal-skeleton

A Drupal project template.

141.4k](/packages/palantirnet-drupal-skeleton)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)