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.
The goal of Access Control Kit (ACK) is to provide a customizable system for controlling access to all kinds of things in a Drupal site: nodes, taxonomy terms, menu items, and more. It will give site builders the flexibility to define access based on whatever conditions make sense for the site, while still providing an easy-to-understand UI for security administrators and regular users.
Why you'd want it
There are several outstanding access control modules already available (Content Access, Nodeaccess, Taxonomy Access Control, TAC Lite, Workbench Access, Menu Access, etc.), but many of them share a set of common problems:
Most define their own view/add/update/delete/list permissions, which are incompatible with Drupal's built-in node permissions. This may make sense to the site builder, but can be confusing for whoever is tasked with managing user roles day-to-day.
They don't tend to work well together, so you can only define node access by one scheme at a time.
Most control access to content, but not content-related features like menu links or tags. You can install other modules to handle those, but there's usually no direct integration (i.e. Menu Admin per Menu doesn't know how to relate its controls to your TAC hierarchy), which complicates administration.
Allows administrators to override the visibility of menu items. Normally, items which are inaccessible won't show up in the menu. Using this module, menu items can be set to always show up. Their contents will still be restricted.
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.
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.
I'm currently looking for someone wanting to take over OG Forum D7.
I'm working on an alternative to OG (Groups, Communities and Co (GCC)) and it takes all my free time.
I hope the current version of OG Forum D7 will be used as a starter kit by a new maintainer to create a perfect integration between OG and Forum.
This module allow to make some forum and their topics owned by an Organic group, just like any other group content.
It is a new version of the old and deprecated OG Forum, only for D7 as it use the all new APIs and Fields added in Organic Group D7.
How it works :
This is simply done by adding a group audience field to the forum's taxonomy terms and topics and by automating some task (like selecting the same group audience for a topic than its parent forum)
Currently, there is no forum administration inside the groups. The Organic group forums are managed just like any other forums.
In the futur, i planned to create an internal forum administration for each Organic group and to add some privileges to administer the forum inside an organic group.
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.
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.
Allows node editing access based on menu relationships.
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.
For Drupal 7, this module is being replaced by Workbench Access. An upgrade path will be provided.
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 extends the content access module to put the view (any/own) [TYPE] to the drupal permissions form. So a user settings the access permissions doesn't have to switch between two forms and he doesn't need access to change content type settings.
This module allows integration between workbench moderation and organic groups. Organic group roles can be defined to be responsible to perform different transitions that will move content from the different stages.
A perfect use case for the usage of this module: a website with several groups that contains a content workflow process.
Users with "Content author" role in group "Finance" can create content that needs to be approved before being published to "Finance".
Only "Content editors" of group "Finance" can review and publish those nodes.
"Content authors" can create new revisions of content that is curently published. That content remains published till the new revision gets reviewed and published.
"Content authors" and "Content editors" of different groups will not have access to content that is under review in group "Finance".
This modules allows group managers to configure permissions that allow members with defined roles to move nodes in defined workflows configured using workbench moderation. Instead of configuring permissions to transition nodes to be published by normal roles, this module allows to do in a group context defining group roles that can publish nodes.
Includes multiple modules for video communications including room listing, pay per view access control:
- Video Conference integration
- Video Chat integration
- Video Consultation integration
- Live Streaming integration
- Room List
These modules allow setup of Pay Per Minute / Pay Per View ( PPM / PPV ) video chat, consultations & e-learning, webcam live shows, conferences using VideoWhisper Drupal Modules.
Generates link for view, edit, or delete content without login.
Module maintains authorization key for every node and gives additional grants (view/edit/delete) to every user (anonymous too) who accesses page with correct key in URL. Module offers function node_authlink_get_url($node, $op = 'view') for generate absolute URL to selected operation (e.g. for e-mail notifications).
Authkeys are generated for every node (in configured content type) once for all operations. In content type form you can configure which operations to allow and authomatic expiration of keys.
A simple module that tracks downloads of files added through CCK/Fields by asking anonymous users to enter their email address. Returning anonymous users are tracked using a cookie. A tracking interface shows email address and user account information for tracked files downloaded on the site.
Why only have users enter their email address? Email addresses are a unique and easy way to identify users, and the barrier for entry is lower than actually registering for the site.
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.