Search form

Download & Extend

248 Modules match your search

Maintenance status

Development status

Module categories

Core compatibility

Status

Search Modules

Sort by

Extend and customize Drupal functionality with contributed modules.
If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.

This module extends Profile 2 by allowing administrators to create privacy levels as predefined groups or sets of profile fields on a per role basis. Users can then select from among the privacy levels to apply access control to their profile.

Requirements:

Installation & Configuration

You must configure this module! Failing to configure this module will result in inaccessible user profiles. In order to protect user privacy, profiles created prior to enabling this module will have strict access control (i.e. be inaccessible), until the user updates the setting.

This module allows setting a node as frontpage for anonymous and authenticated users. Users can be allowed to set the frontpage by setting the appropriate permissions.

Once the module is enabled

two new links will appear at the end of the node body (Set as anonymous frontpage, and Set as authenticated frontpage) for any content type that has been enabled, and for the users with the right permission;

Two new node operations will appear at admin/content (Set as anonymous frontpage, and Set as authenticated frontpage) for any user with the right permission.

Only users with the edit frontpage permission, or the bypass node access permission can edit the node that as been set as authenticated (anonymous) frontpage.

Only users with the set frontpage permission, or the bypass node access permission can set the frontpage for the authenticated (anonymous) users.

Access Denied Backtrace will help you track down the specific place where Drupal is triggering the access denied for a certain role.

Use Case:
Have you ever gone crazy when certain roles cannot access nodes in Drupal? Then you have to start checking permissions on and off just to finish right where you were to begin with? Or even worse get some more permissions control modules so they can override Drupal permissions.

The Deny Access module (Drupal 7 only!) allows overriding access granted by other node access modules and/or core. It uses the node access system but not the {node_access} table, and so if you don't have any other node access module installed, then it does not carry the typical overhead. The downside is that it will not work to guard against showing lists of nodes, like lists created by the Views module or the front page. At this point it's a very simple module.

Deny Access provides the following global 'permissions' on the Permissions page, admin/people/permissions#module-deny_access:

Webform Private File Gateway provides umbrella functionality for controlling access to private files through the use of a webform. Users are forced to fill out a webform before they are granted access to the private file they are requesting. Developers can optionally specify whether or not to send an email the the user with a link to the file download and/or enable cookies for remembering the user.

The difference between this module and Webform Protected Downloads is that Webform Private File Gateway controls access to ALL private files whereas Webform Protected Downloads requires separate webforms to be created for different files.

UC Node Access lets you attach Node access features to products in your Ubercart store. These features allow customers who purchase the product to receive view access to nodes on your site either indefinitely or for a limited time based on the feature's settings. UC Node Access does not handle access grants itself but rather depends on other modules to define handlers that integrate UC Node Access with the various node access modules developed for Drupal.

Currently integrated node access modules include:

ACL + Content Access - adds the customer's user account to the ACL defined by Content Access and adds expiration information beside the names in the Grant view access fieldset of the Access control tab for nodes governed by Content Access.

Available callback functions are defined by modules using hook_views_access_callbacks() function (in the same way as in hook_perm()), then could be set in in view's "Access restrictions" configuration.

With this module you can lock fields in a webform so that those fields cannot be deleted or modified except by administrators with appropriate permissions. It was written to work in tandem with the Webform Default Fields module but is not dependent upon it. The idea is that if you create default fields for a webform, you may want to ensure consistency by preventing webform creators from modifying some or all of the default fields.

The Menu Node Edit module allows the site's menu system to be used as the sole organizing principle. It does so by allowing specific menu items to be defined as 'sections' of a Drupal web site. Individual users can then be assigned as editors of one or more sections.

Section editors are then granted access to edit all nodes that fall within a specified menu hierarchy.

This structure means that, for small web sites, the menu system can be used as the sole ordering principle, removing the need for taxonomy or group-based editing controls.

Drupal 7

For Drupal 7, this module is being replaced by Workbench Access. An upgrade path will be provided.

Dependencies

Use of the module requires that you download and install the Menu Node API.

Menu Node Edit and Node Access

The Menu Node Edit module is deliberately not a Drupal node access module. It does not provide any access controls for the viewing or deleting of content.

This module is no longer active. The Masquerade module does what this module does, only better, so go and download that instead.

The difference with Masquerade and my module is that mine displays the "switch" link along side the "edit" link for users, where as Masquerade has the option to masquerade as a user in the operations dropdown. Masquerade also logs the user-switching as well as giving you a switch-back link, so it is truly superior.

Overview

OG Workflow integrates the permission systems of Organic Groups (OG) and Workflow. Permissions for workflow state transitions can be granted based on OG group roles (see screenshot).

7.x-1.x

Use Version 1 for OG 1.x. There is no node access control for this version, but you can use Rules to bind state transitions e.g. to publish/unpublish actions.

7.x-2.x

Version 2 integrates with OG 2.x and is not compatible with OG 1.x. Additionally, it integrates with og_access (part of OG). That means that private entries in groups are respected and people cannot view them even if workflow would allow them (enable strict access control in OG settings).

Workbench Moderation Profile adds the ability to have multiple workflows, divided into profiles, based on the states and transitions defined by Workbench Moderation. These workflow profiles can then be applied to nodes based on criteria you determine, and an API is included to help with that process.