Description:
This module allows you to grant access for specific user roles to view unpublished nodes of a specific type. Access control is quite granular in this regard.
Additionally, using this module does not require any modifications to your existing URL structure.
Restrict by role who can search for each content type.
Approach of this module is to re-write the search query, so that content is indexed and available as search results to users in role(s) that have permissions to view it, but not displayed to other roles.
Integrates with Apache Solr to exclude results based on the role of the person searching.
Enables moderation of nodes.
Which role can see nodes in moderation can be set per content type.
Views integration, so view(s) can be created to give moderation overview.
.OBSOLETE. Current Civicrm versions are not supported.There is a current limitation of CiviCRM that contact matching rules are not applied to contacts created via profiles injected into Drupal's User Registration.
Provides role-based exemption from limits on the number of actions of a particular type.
Sample usage: allow given roles unlimited use of contact forms as provided by the core Contact module.
By default there is flood control on usage of contact forms in the core Contact module such that users are limited to (e.g., using a site contact form) that a given user can take per hour. Using Flood exemption, you can allow given roles unlimited use of the contact forms.
Role Login enables login to be restricted by role. The module was developed to enable a user table to be shared between multiple instances, but still maintain control over which users can login, for example, on a dev instance versus a live site.
Dependencies
None
Installation
Description
Views UI permissions lets you restrict access to users with the restricted views permissions to edit certain options in the views interface. Toggle the checkbox of any views option to enable access. Disabled automatically:
Module adds 'view own content' and 'view any content' permissions for all of content types.
So, administrator can build a more flexible system of rights.
For example, admin can add 'view own question content' for role 'clients' and 'view any question content' permissions for support engineer so, clients can see only own questions and technical support engineer can see all questions from all clients.
NEW! If you using CCK, you can check new feature 'view content via field_reference'.
Also, see another content access modules:
This small modules exports specified users to a DBM database. This database can then be used to authenticate users in other Apache contexts, for example for Subversion repositories.
Adds auto-completion to login forms' username field.
WARNING: You will have to grant anonymous users the 'access user profiles' permission for this to work. Anonymous users will have access to every users' username, so use with care.
