User Access & Authentication

This simple module overwrites permissions the node declared menu path /node by adding an extra 'access node path' permission to your permissions page.

OG User Roles Access (OGURA) extends OGUR 4+ (OG User Roles) and introduces group roles specific node access realms.
Thus you can specify assign group specific roles to a user and have per content type specific access permissions.

This module overrides og_subscriber realms (on request) and further limits permissions instead of granting more permissions.

(Compatibility to OGUR before version 4.0 has not been tested and is not subject of this project.)

Parts of this functionality might be integrated in OGUR one day...

The Drupal userpoints nodeaccess module enables you to sell access to a single node for a specific category and amount of userpoints.

Grant individual users access to the results of specific webforms.

Adds a tab to each webform "edit section" that allows you to add users that should be able to access the results of a webform, but not adjust the form itself.

Users who are granted access this way then don't see the "edit" tab on the webform but only the "results" tab. They can then view results, download them, ...

The Premium Content Access Permissions By Term module allows access to content to be restricted to certain roles by taxonomy term and Drupal role permissions and supports multiple access tiers.

This module is useful to publish nodes that require an agreement to be signed by each user before they can access the content. Examples of agreements include Non-Disclosure Agreements, End-User License Agreements, etc. Nodes of any type can be protected by agreements, and each node can have its own specific agreement.

Block Content Per Role allows a block to be defined which contains content that is displayed depending on a weighted set of roles. This is useful, for example, if you want one block for a subscriber role, one for authenticated and one for anonymous.

This is difficult to do with Drupal out of the box as a users with the subscriber role will also be logged in and therefore also have the authenticated role. The Blocks system in Drupal does not allow a "complex" selection such as "Users with roles XYZ but not ABC".

This module allows users to have a public name, shown as attribution and identity but not used for login. There are some significant requirements you must know about if you choose to use this module. See also http://drupal.org/project/realname for a module that accomplishes a similar purpose, but is more sophisticated and complex in its approach.

This module allows administrators to moderate entity access by issuing licenses to site users. These licenses may optionally be set to expire at a predefined date and time.

8.x-1.x

This module provide a new "license" entity which can be used to moderate access to any other entity type(s) and bundle(s). These may be created via a (provided) user interface or programatically.

The license entity has the following base fields:

Adds an AJAX Login/Registration page to any node/add form(s).

Users can login using their email address or username, depending on configuration, without having to leave the creation form. If the username or email address is not found in the database, a registration form is presented that may optionally include a username. If the username is not part of the registration process, the email address is used as username.