This module provides the ability to have more fine-grained control over what users with the permission 'administer permissions' can configure. You can decide which user roles will see a limited permissions table at admin/user/permissions, and who has unrestricted access to it. The modules allows you to lock certain permissions and / or certain roles. This means that these permissions / roles will not be available for configuration to a user with limited permission configuration rights.
This module could be useful if you want to allow a client to control website permissions for relatively harmless things like posting comments, creating content, administering taxonomy etc..., but you don't want the client to have the opportunity to change permissions for things like Views, content types, themes, ...
Features
Remove a configurable set of permissions/roles in the permissions administration table for users in roles that you want to give the 'administer permissions' permission, but don't trust completely with that power.
Provides a hook_permissions_lock() to define locked permissions / role from within your (custom) module. This makes it easier to deploy / repeat permissions_lock module settings
This module is meant to work with FeedAPI, FeedAPI Node and Feed Element Mapper to give more control over what happens with incoming taxonomy terms.
Example Use.
Vocabulary of 'Categories' feeds the a piece of the primary links using taxonomy_menu. When a feed-item comes in the options->tags element is mapped to the 'Tags' vocabularies using Feed Element Mapper. If the term is found then I remove it from the association from the 'Tags' vocabulary and add the association to the 'Categories' vocabulary. Now the new items are automatically in the correct place for views.
The feed owner (or other person) would then come match the new tags to an existing category. If they wish to add a new category then they fill out a request form and the site administrator can create the term and move the nodes accordingly.
Suggested Workflow
1. Feed is refreshed
2. New node is created using the taxonomy setting from Feed Element Mapper. If using FeedAPI Node Inherit, this is applied here also.
3. All mapped and inherited terms are run through this module.
4. Matched terms are added to more defined categoreis.
5. Unmachted terms are placed in a general vocabulary where the feed administrator can add them to specifc categories later.
REQUIREMENTS
FeedAPI
Taxonomy
FeedAPI Node
Feed Element Mapper (to match the incoming vocabularies.)
View the development Blog Here