275 Modules match your search

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.

Domain Override

Allows overriding page nodes on a domain-specific basis.


  • Provides an "Override" tab on node pages that removes the current domain from the node's domain access, clones the node, and publishes the clone to only the current domain.
  • Copies translations of the node being overridden (if any), too, so they're considered translations of the newly created node.
  • Sidesteps need to use multiple url_alias tables (with Domain Prefix). Makes Drupal interpret the URL alias for a node that's been overridden as a path to this domain's version of the node. Example: node 1 (the node at node/1) is published to all domains with the URL alias contact-us. You visit the node from the subdomain "cats" and select the "Override" tab. Now a new node has been created (node 2), that's published only to the "cats" subdomain, and node 1 is no longer published to the "cats" subdomain. When you visit http://site/contact-us you'll see the content of node 1. However, when you visit http://cats.site/contact-us, you'll see the content of node 2 -- node 1's override.


Pirobox Limit

Example of use Pirobox Limit

The Pirobox Limit module extends the Pirobox module with limiting and access functionalities.


  • Limiting the display of image groups.
  • Define a user role can see full image groups.
  • Configure a bypass to allow content owners to see full image groups.
  • Limits are configurable per content type and per Pirobox image field. In other words: per image group or respectively per gallery.
  • The limiting works also with multiple galleries for example on teaser pages.

The limiting-action is possible in 2 ways:

  1. Quietly
  2. Busily


  • Image groups are limited and no other actions.

It is possible to inform the visitor.

  • Display one, two or three limited images.
  • Use different image styles for the limited images in the content and the Pirobox.
    It is recommended to use the ImageCache Actions module.
  • Use an different Pirobox caption text for the limited images.
    The different caption text is configurable.

The quietly and busily settings are generally configurable for all limited galleries.

Required modules


URL token

URL token is an API module to make token-based access control simple.

There are two main features:

  • Request a token
  • Check that a token is valid (usually via a URL)

You should only install this module if another module requires it. This module doesn't provide any functionality by itself, it provides features for other developers to use in their modules.


Simple Ready Workflow

Simple workflow module preview

This module adds a new "ready" publishing option on node bundles and fine-grained permissions on publishing options.
It gives you a simple worflow:

  • Ready not checked (draft)
  • Ready checked (ready to be published)
  • Published checked (and surely ready!)

If you need a more suitable and customised workflow, you better look at Worflow module: http://drupal.org/project/workflow


Og comments access

Og comments access allow you to manage comment access in Og group context.

It comes with 2 new og permission :

  1. Post comments
  2. Edit any comments

With these 2 permissions, you can now restrict comment posting on group.
You can also allow particular OG role to modify all group comments.

There 2 permissions overwrite the global Drupal permission in the group context.


Webform Per Email

Attaching to a webform


This module implements a permit based access system to allow anonymous users submit a Webform only if they display a valid one-time access permit.


OG Node Access

When you update the privacy settings of an Organic Group, you may need to rebuild the node access settings of the nodes assigned as posts to that group. Unfortunately the node access rebuild system focuses on rebuilding all nodes, instead of just those affected.

This module has forked the node rebuild system to allow developers to target one or more Organic Group's for node rebuild. It has the following features:

  • Automatically detect when group privacy changes as the result of the node edit form and directs users automatically to the batch edit screen.
  • Integration with Spaces allowing group administrators to rebuild node access for their group at need.
  • Developer API in the form of a og_node_access_needs_rebuild() function to add new groups for rebuild.
  • Plays nicely with general node access rebuild flag, allowing general node access to trump og-specific rebuild.

This is in response to #1101738: Repairing node access permissions without rebuilding all, thanks to @btopro for getting the ball rolling.


This module is set for maintenance and bug fixes only and is unlikely to get much in the way of new features. Good, minimal feature patches are welcome. As we currently have no use for a D7 version of this module, we are open to requests to create and co-maintain a D7 branch.


Ctools Compare ID

Settings form

The module provides a ctools plugins to provide access control by checking for equality ID.

Supported entities for check access:

  • Node
  • User

An example of using the module:

  • Deny the display of the page to a particular user, if you know its identifier.
  • Overriding a specific page.


Node Relativity Access Control

This module enables access control based on (and so requires) the Node Relativity module. It propagates the grants from a node to its descendants. You should use another module like content_access to provide the grant to the ancestors.

Just enable the module and select the content types that will inherit the grants at /admin/settings/relativity/access.


Conditional Roles

After much consideration, I've decided to scrap this module and take the project in a different (and, I hope, far better) direction as Access Control Kit. No further development will be done on Conditional Roles, other than to provide a migration path to ACK.


Content Type Archive

This module allows you to "archive" content types by preventing new content from being created, but still allowing full access to existing nodes.


OG Announce

Extends the Organic Groups module to allow creation of announcement only groups, into which only group administrators may post.


Shared Access

The goal of this project is to provide a method for users to easily configure access settings to their own entities. The interface for configuring access will come from a shared access field attached to the entity.

Development Roadmap

  1. Implement field hooks to define the new shared_access field type.
  2. Define formatters and formatter settings.
  3. Define widgets.
  4. Implement an extendible access controller class structure for defining access realms and their underlying functionality.
  5. Define several default access realms (user, organic groups ... perhaps a few more).
  6. Implement field hooks so that a form shows up on the entity content page.
  7. Implement a standard sharing settings form that can hook into the access controller classes and be used to control access to the entity.
  8. Provide autocomplete functions and hooks for displaying user name/og suggestions as the user types
  9. Implement access hooks and query/query_HOOK alter functions to control access
  10. Implement field access hooks so that the form only shows when the owner or configured admins view the page.


Restricted Home Link

This module provides a permission to prevent users from creating/editing/deleting/moving menu links pointing at <front>.

Use case: you wish to grant a user the ability to administer menu links, but you want a home menu link to always be the first link in the menu.


OSF for Drupal

OSF for Drupal

The Open Semantic Framework (OSF) for Drupal is a middleware layer that allows structured data (RDF) and associated vocabularies (ontologies) to "drive" tailored tools and data displays within Drupal. The basic OSF for Drupal modules provide two types of capabilities. First, there are a series of connector modules such as OSF Entities, OSF SearchAPI, OSF Field Storage and OSF Views to integrate an OSF instance into Drupal's core APIs. Second, there is a series of module tools used to administer all of these capabilities.

By using OSF for Drupal, you may create, read, update and delete any kind of content in a OSF instance. You may also search, browse, import and export structured datasets from an OSF instance.

OSF for Drupal connects to the underlying structured (RDF) data via the separately available OSF Web services. OSF Web Services is a mostly RESTful Web services layer that also allows multiple Drupal installations to share and collaborate structured data with one another via user access rights and privileges to registered datasets. Collaboration networks may be established directly to distributed OSF Web Services servers, also allowing non-Drupal installations to participate in the network.


Field ACL

This module will grant access to a node from a field. The field contains usernames.

This module requires the ACL Module.

This is useful when you need to audit who has access to a node. The changes will be tracked via node revisions.

This module is also compatible with nodechanges


Restrict Abusive Words

Restrict Abusive Words

The Restrict Abusive Words module restrict to use words or phrases in forms all over the site content. The Restriction can be applied on content form, comment form, user profile form, user registration form and webform.Restriction can also be applied based on user roles.


File access by node type

File access by node type allows website administrators to select which roles can access files belonging to nodes of a certain node type. This goes beyond simple field permission, since there can be situations where users might embed an uploaded file into a Body textarea, or a WYSIWYG editor.

This module allows the restriction to work even in those cases by intercepting the file download before it happens. It also respects other access control mechanisms, since it defaults to either restricting access, or delegating it further. If the file download is not denied, and no other module is there to make a second decision, then it will download it. This allows for future integration with other modules and should be consistent in how Drupal handles access control.

To use

This module currently depends on FileField.

Enable this module as usual, then go to http://www.example.com/admin/settings/file_access_by_node_type to configure the different roles and node types.


This module was developed for Switchback by


ClickBank Download

PLEASE USE ClickBank IPN INSTEAD. This module is no longer maintained.

NOTE: This module is in no way affiliated, endorsed, nor provided by ClickBank.com.

What is this module?

This module validates purchases on payment processor ClickBank, and provides a "secure" file download link. This module IS appropriate in the following situations:


Phone Captcha

With phonewithcomputer.com service, we use phone for CAPTCHA service.

It provides a unique way to authenticate user.


Phone CAPTCHA depends on the CAPTCHA module.
A patch is required for CAPTCHA 7.x-1.0 https://drupal.org/node/918856#comment-7583533




Node Access Fixer

This module does nothing on its own, other than to attempt to make harmony out of multiple node-related "access callback" changes made in the hook_menu_alter() implementations of various modules. It does this by ensuring that its own "access callback" handler is called for each of several node-related menu paths ('node/%node', 'node/%node/edit', etc.). This handler then calls all other "access callback" handlers for the given path, returning TRUE if any handler grants access.


Require OG access

Prevent access to OG private posts except to privileged users and OG group members.

This module serves to ensure that OG private posts remain private to the Organic Group(s) to which they're posted, regardless of which other modules may be trying to grant access.

Organic Groups usually does a fine job of ensuring that group posts marked "private" will only be accessible by group members. But other access-control modules may still grant non-group-members with access to those nodes.

This module adds an additional check to the node access system, so that group posts marked "private" will be inaccessible (for view, edit, and delete operations) to anyone who is not a group member, even if other modules grant such access.


Workbench Access Content Type

Extensible editorial access for the Workbench suite for granular access permissions by content types.

This module will add a new tab "Content Types" at the configuration page of Workbench Access, to provide permission by Section by Content Type.

This module was developed by Vardot for Georgetown University in Qatar.



IP List


The IP List module allows administrators to maintain and search list of IP addresses and IP address ranges, and associate each address or range with an arbitrary organization (string). The module doesn't do anything with this list, but the list can be integrated into other systems.

This module was written to be integrated with a Varnish ACL (access control list) and thereby allow non-technical administrators to manage a list of IP addresses and ranges that can bypass a content paywall.



Audience provides an abstract definition of user groups and types in a given context. These definitions are called "Audience presets" and can be used by other modules to control different types of audience related actions or permissions. By using CTools these audience presets are exportables and can either get stored in a database or live in code provided by modules.

Modules can use these presets to check if a user is member of a given audience. Therefore audience_is_member_of($preset, $account, $context) is used.
Using audience_members($preset, $context) all users of a given audience in the given context can be retrieved.

Audience presets are instances defined by an audience type. Default audience types shipped with Audience are "user", "roles", "author" and "userreference". There also "intersection" and "union" that merge multiple preset definitions to one preset (e.g. User is "author of node xy" and has "role admin").


These modules are part of the project.

  • Audience - Definition of audience presets
  • Audience ACL - Caching of audiences by using ACL
  • Audience NodeAccess - Provides a CCK Field that uses ACL cached audiences to control access on the given node