Content Access Control

The domain content types module is add on for Domain Access which allows you restrict access to content type creation forms based on active domain.

e.g. I want users to be able to create pages on domain x and y, but not on domain z

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.

GeoIP Role allows to dynamically grant roles to the current user according to his IP address location.
It depends on the GeoIP API module.

Currently, GeoIP Role allows to attach countries to roles, thus defining geographical zones.
When a user visits your site, he dynamically gain the role(s) attached to the country reported by his IP address.

GeoIP Role may be used with any other module like Nodeaccess that controls access based on user roles.

The Flexi Access module will provide a simple and flexible interface to the ACL (Access Control List) module. It will let you set up and mange ACLs naming individual users that are allowed access to a particular node.

The module let you manage access to individual nodes. The administrator may grant individual users the right to: View (read), update (edit/write), and delete the node.

Virtual Site allows a site admin to quickly instantiate a sub-site or standalone site within a single Drupal install. Virtual site instantiation includes, among other things, the ability to quickly populate a new site with placeholder content, menus, and selection of custom themes.

This module is in early development, so it may be a few weeks before the first development release is posted. However, this project page has been created to begin fleshing out documentation and feature set.

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:

• DENY accessing any content
  Override content view access (to single nodes!) granted by other modules.
• DENY creating any content
  Override content create access granted by other modules.
• DENY editing any content
  Override content edit access granted by other modules.
• DENY deleting any content
  Override content delete access granted by other modules.
• DENY access per content type
  Generally override access (to single nodes only!) for a specific content type.

Allows for selected filefields to protect their files from download unless from users with appropriate role permissions. This allows a site to use Public file access method for the main site, but selectively secure a subset of files as required.

The module works by creating a secure subfolder under files. Therefore there are a few requirements:

* Ability to use .htaccess files to secure folders on your server (i.e. Apache webserver).
* Filefield_paths to put selected files in the secure folder.

Allows overriding page nodes on a domain-specific basis.

Features

• 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.

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.

 

This module allows granular control of block visibility on a per-domain basis.

Use this module to set different visibility rules for each domain on your site, as setup by the domain access module. You can use this module in conjunction with the Domain Blocks module to restrict blocks from certain domains.

After installing your module, visit a block edit page and see the extra options added to "page visibility".