Kyle D. Skrinak

I recently needed to add a feature to a Drupal website I didn’t start but now manage. I had to make some webforms (a.k.a., “surveys,” to my beloved customer) available to only a select group of users. I created a role for the targeted user group. There were a few pitfalls — the site is Drupal 5, not 6, (and the difference matters nowadays, as the D6 base is more robust, go figure) and the recommended modules from the webform module references D6-only modules. So I had to hunt down an alternative, and found one, “Content Access.” I plugged it in, and after the usual learning curve, I had it performing its desired functionality whereby select webforms were visible to a selected user role. (My previous post is a video tutorial and setting the content access privileges for my client.)

So, here’s the kicker, something I realized only after I was done and moved on to other things. I have a “view” (as a page) that shows all webforms in the system. This is what I needed to filter down. I added the Content Access module, made the appropriate adjustments, and then my view respected the content access settings without hitch or modification requirements. That is remarkably tight integration. I love standing on the shoulders of giants.