Deputy

The Deputy module helps developers and site-builders "deputize" users of their application with a limited set of configuration control. It is not a permissions management module.

Deputy's primary focus is on two things

• Helping developers encapsulate functionality in such a way that it can be easily enabled or disabled via a simple operation.
• Building a clean, centralized UI for those bits of functionality so someone with limited site privileges can still find a central administrative page to control those pieces.

What does Deputy provide?

Deputy provides a single info hook that allows the definition of a stripped-down module-lite namespace that can be managed via the Deputy form. Additional options allow this to be turned on by default, to provide an advanced settings form, or to include a specific file when the "deputy system" is enabled.

All deputy systems have permissions associated with them as well, allowing you to grant access to all aspects of the Deputy form to some roles, but only strategically selected sections to others.

It is a feature, not a bug, that Deputy Systems ignore any access control not specifically put in place on the Deputy form--the goal is to expose configuration settings that would otherwise be trapped behind complex module forms that require far too sweeping a set of permissions to comfortably expose to users that are not in a site building role.

When should we use this instead of just defining a form and using hook_form_alter()?

When you want to surround your form with permissioning and meatier functionality than just some bits of UI and variables in the database. We've used it for several "micro-features", such as turning on and configuring the Contact module.

For more information, visit the README.txt in the repository.

Sponsorship

Sponsored by GoingOn Networks. We provide a unique academic life platform that enriches the student experience through the focused application of Drupal and other technologies.

Downloads