By UNarmed on

Hey all, dose anyone know how i would go about restricting access to certain pages for specific roles??

A nudge in the right direction would be greatly appreciated =D

Comments

ludo1960’s picture

ludo1960 commented

Use of content types to restrict access to certain roles

nirbhasa’s picture

nirbhasa commented

In addition to the 'core' approach outlined above there are also contrib solutions:

- You can also restrict access on a per-user basis to content types and also individual nodes (http://drupal.org/project/content_access)

- Restrict access to individual nodes: http://drupal.org/project/nodeaccess

- Restrict access to nodes marked with certain taxonomies http://drupal.org/project/taxonomy_access (or http://drupal.org/project/tac_lite )

- Restrict access to nodes contained within a book (http://drupal.org/project/book_access)

There are also other solutions but these seem to be the most popular

vincent sg’s picture

vincent sg commented

Subscribing

UNarmed’s picture

UNarmed commented

I found a super nice module for doing exactly this, http://drupal.org/project/simple_access

It alows you to group users into user groups and then when you creating or editing a page you can say which user groups should be allowed to access that page.

jimrockford’s picture

jimrockford commented

Why are there create, edit, and delete permissions for content types (i.e., node types), but no explicit view permission? Why should I have to install contributed modules (every new module is more memory and complexity) to achieve this, when 75% of the permissions already exist in core? All I want to do is create two content types, one public and one private. Then, assign view access by role to those content types?

Is this by design in core, or an oversight?

ludo1960’s picture

ludo1960 commented

..have a look at the OG module, posts can be public or private.

jimrockford’s picture

jimrockford commented

Thanks, I've come across several modules that let me restrict a node (and node type) by role. I suppose the root of my question still stands: why does Drupal core have "create, edit, delete" role perms for specific node types, but not "view". The only view option is "access" all content, or none at all. I'd rather not install a module to configure what seems to be a fundamental permission. Maybe, in the end, I'll have to. Makes me think of a table with 3 legs.