Content Access Control

This module is now a submodule of Permissions by Term and will no longer be maintained here!

Why Permissions by Entity module?

Per default the Permissions By Term module extends Drupal by functionality for restricting access to single nodes via taxonomy terms. The Permission by Entity module extends this functionality so that you can not even restrict access to singles nodes but any content entity like eg. paragraphs, media bundles or even user pages via taxonomy terms.

This module is under development on GitHub. More detail available there.

Github Project

Attribute-based Access Policies

Attribute-based Access Policies is special implementation of a Policy plugin as defined by the Entity Access Policies module module.

Attribute policies are written in YAML.

The pluggable Access Control Handler ("pACH") module replaces the default
entity access control handlers with an extensible plugin system.

This allows modules to extend access control for entity types using plugins
without overriding the main handler.

About

This module extends Workbench Access functionality to control access to editing taxonomies.

Workbench access works with node entities only. This module allows to also restrict editing of taxonomy terms in select vocabularies. Here is an example use case where this module may be handy:

You have a site where you want your users to create nodes, blog pages etc. You use tag style taxonomy terms on these nodes. You want your trusted site editors to be able to add new terms when they create content but your regular users are polluting your tags vocabulary with misspelled words. How can you stop these users creating new terms but allow your editors to add terms whilst writing content? The answer is this module!

Simple module for checking access for all registered routes for given user.

Introduction:
-------------------
This module makes it easy to add speech recognition to your web pages to search content.

Note: This functionality will work with Chrome browser only.

Requirements:
------------------
This module requires the following modules:
* Search

Installation:
------------

Subscription

A Subscription is an entity which can be associated to a user. When a subscription is activated (from a pending or expired state) the user gets a role which matches the role that is recorded against the subscription entity. When a subscription has expired that role is then removed from the user.

To manage a subscription's state subscription term entities should be assigned to the subscription.

By default subscriptions are 1 year long, (i will add in additional functionality to update this to be configurable).

Respect people privacy and let every particular user to decide which external services to be rendered on your pages.

The implementation is frontend-based, so you can safely use this project alongside with caching services, like Varnish or Nginx.

How to use

The main idea of implementation - to process fields and blocks and check their contents for external widgets. How this achieved?

Fields

Third-party services filtering might be enabled for every field.

Locked Content satisfies a specific access control use case: you want users to be able to see teasers, links, and search results for locked materials, but want them to log in before actually visiting the full page view. It's useful for situations where keeping the existence of information secret isn't critical, but making sure users are logged in before they actully view the complete contents is important.