Content Access Control

Privacy Per User provides a simple framework to enable privacy settings per user, similar to the privacy settings on a site like Facebook. Those settings may be used to check access for display of entire pages, elements of a page (such as in a theme), or as an argument validator in a View. This allows individual users to control access to things such as their profile, specific elements of their profile, or lists of content they may have made, e.g. flagged nodes. It offers a flexible API to allow additional privacy states to be added (e.g. friends only) and an exportable set of privacy types.

A Drupal 7 node access module that doesn't make use of the node access system. Just because I can now. :D

Eggther is an extension to Node access user reference.

This small module adds the missing permission "view any unpublished content" and "[Content-Type]: view any unpublished content" to Drupal 7 and provides an replacement for /admin/content aka "Find content".

Taxonomy based Access Control List module provides taxonomy-based access to the nodes. tacl module provides only a common API but this package also contains a "frontend" - tacl_user that allows for managing per-user, taxonomy based permissions.

The target audience are site builders (tacl_user) and developers (tacl).

Workbench Moderation adds arbitrary moderation states to Drupal core's "unpublished" and "published" node states, and affects the behavior of node revisions when nodes are published. Moderation states are tracked per-revision; rather than moderating nodes, Workbench Moderation moderates revisions.

KeyCAPTCHA - CAPTCHA with social features. You may support charity funds by using KeyCAPTCHA. Unlike many other captchas, it does not require any text typing.

Free Variants of Using KeyCAPTCHA:

Enabling access control for specific fields on nodes based on user location. Administrators create settings for each profile containing a list of countries and which fields are under control. It's possible per profile set default behavior to whitelist or blacklist.

Separation domains of Backend / Frontend

set a domain for the administration area, the normal user can not access to the administartion pages which the path start with 'admin/...', it will throw a 404 page not found.

The user will be restricted from premium content. The content will be unlocked with the presence of page specific cookies and/or a master (Profile complete) cookie.

Users will unknowingly register and login with just an email account. All other required profile fields will be progressively required for access to premium content.

This module will be dependent on premium content or content access? Still deciding...