Setting up private views with access control

Drupal: 20m
Video Series
Information

Views is great for making listings of all kinds of content for many different tasks and users. You don't always want everyone on your site to see everything you put in a view though. In this video we'll learn how to limit access to a particular view, using the built-in menu and access restriction settings. We create a new view to ist all of the applications that have been received on the site and make sure that only site staff can access it.

Discussion

Comments on this video

You need to be an active subscriber to comment. or .

This is excellent!
I greatly appreciate the access control and the possibilities it opens up for my planned site.

I am wondering how granular this might be. For example, can a view's permissions be restricted down to certain individual users somehow? I want to have viewable content that can only be accessed/viewed by certain roles (e.g. Administrator, Staff) AND individual user(s) (e.g. a specific client) to which the content pertains (e.g., a client's data, entered by them or someone else). Also it would be ideal for the individual users (clients) to be able to grant revokable/limitable access permissions for other specified users (e.g., a client's group affiliated with parts of their data, or a trusted contact who can see more but perhaps not all of the particular data relating to an individual client).

This demonstration definitely gets me a lot closer to being able to implement my ideas. It may even be able to be adapted if I change my ideas around a little bit. But it isn't really quite there yet, or I'm missing something, like how to change the options under permissions, because simple roles won't do and they can become quite elaborate if I'm trying to create my intended level of granularity without having the option to search and specify individual users with various options for who can control access and see various data elements (fields). I also don't want the clients to be able to accidentally or intentionally remove the ADMIN/Staff roles who should be able to access ALL content. I'm sure what I'm describing has been desired and probably figured out by someone already. If your aware of any solutions, could you please direct me to a link or a tutorial on how to implement this granularity to access control? This is the most major and necessary backbone for any "features" I will implement on my site.

Thank you!

-Steve

This was very informative. I have a quick question, I noticed on one the example wen you showed a job application it had a resume attached. I assume in a normal site you would build something with webform (or similar). Does webform have the ability to upload a file or is there an upload module that I would need?

Thanks,
David

Hi Pallino,

Well you wouldn't necessarily use a webform for this. That is a choice based on other needs for the data on the site (nodes are very handy, but maybe overkill, depending on what it will be used for). Since you can customize node forms, you can do it either way. Webform does have a File field you can use. You should definitely play around with it, as it is a great module for various use cases.

Lullabot logo

Lullabot has trained thousands of Drupal developers & guided the development of some of the largest Drupal websites.