| Attribute | Average |
|---|---|
| Features | 5 / 5 |
| Reliability | 3 / 5 |
| Ease Of Use | 5 / 5 |
| Documentation | 5 / 5 |
| Vote Count | 1 |
Manage which roles can view, edit, and/or delete nodes by content type (default) or on a per-node basis (overriding defaults on each node). Also supports changing permissions using Actions. This module is similar in function to Content Access with ACL. Node privacy by role is reported to conflict with... [More...]
| Maintainer: | deekayen |
| Links: | |
| Categories: | Content access control, User Access & Authentication |
| Version | Date | Files | Release notes |
|---|---|---|---|
| 6.x-1.6 | 2011-Jan-24 | Download | Recommended |
| 7.x-1.x-dev | 2011-Feb-25 | Download | Development |
Options: Add a review
This is exactly what I needed!
I wanted to restrict access to selected pages to users in certain roles - this module does the job perfectly.
Simple installation (standard drop into module directory, then enable it), very easy to use!
Whenever you create a node (page, story, etc.), you get a VIEW/EDIT PERMISSIONS grid in the bottom options section, where you can select "view", "edit", and "delete" permissions for each user role, in any combination.
The only problem with this module is that the grid to enable permissions for various roles does not show up in IE7. If the only browser you have is IE, then you will need a different browser to use this module. It worked perfectly in Firefox and Safari.
Other than this bug, the module works great. I haven't found any other problems.
DPM in MS
