By leeaston on

Any suggestions please on how to make it so that authenticated users have access to (can see) specified primary links and associated pages?

Thanks very much, Lee.

⋅ Categories: Drupal 5.x

Comments

dldege’s picture

dldege commented

You set the primary links in

admin/build/menu

Which menu items show up for the given user is controlled by access control settings

admin/user/access

menu items (and thus pages) will be shown/hidden based on the currently logged in user or the access control settings for anonymous if there is no user.

dLd

MariaY’s picture

MariaY commented

I think nodes can still be seen, if the address is known, even though the currently logged in user can not see the menu item. If not, how is access blocked to a node?

grendzy’s picture

grendzy commented

The taxonomy_access module can do this. You assign each node a taxonomy term, and then you can restrict access to each term based on user role. There's also a tac_lite module to control access on individual pages.

MariaY’s picture

MariaY commented

Much appreciated!

dldege’s picture

dldege commented

node access and menu items that go to node is controlled by "access content" permission. Other modules let you make that more granular (node by node basis). This doesn't control the behavior of other primary links you might configure.

dLd

leeaston’s picture

leeaston commented

I'd really appreciate a little more detail on how to make a primary link and it's associated page only available to an authenticated user. Just looking for some basic steps so I can get this working.

Thank you, Lee

doublejosh’s picture

doublejosh commented

I'd like to have a few restricted nodes myself, planning docs ect, viewable by the team, but not the public...

Found this information...

Someone else asking for a list: http://drupal.org/node/152422
The Drupal System: http://api.drupal.org/api/group/node_access/5
Deeper Info: http://api.drupal.org/api/file/developer/examples/node_access_example.mo...

This seems perfect: http://drupal.org/project/node_privacy_byrole
(I'll report back.)
http://drupal.org/project/content_access
(So does this, but the first has been migrated to 6 already, so it's being supported.)

Group/Role/Taxonomy Access Systems: http://drupal.org/node/200631

In case you get really complicated: http://drupal.org/project/na_arbitrator

Hope that's helpful.

doublejosh’s picture

doublejosh commented

Ok, so I installed node_privacy_byrole. Eventually worked.

Immediately all my content went private :(

But all I had to do was...
1. Go through the content types and set their default permissions.
2. Go into admin/content/node-settings and click "rebuild permissions."

Not all that bad, really.

I do have a sneaking suspicion though that when any specific changes to a node's permissions may be wiped out by a content type default change. (Because changing the default altered all the already-existing-content's settings.) Haven't tested this.

PDavid85’s picture

PDavid85 commented

Thanks, that was useful for me.

scotthoff’s picture

scotthoff commented

Problem is you cannot assign taxonomy to menu links can you?

thesubliminaljuggalo’s picture

thesubliminaljuggalo commented

Not really because you can create your own navigation menu with the links to those pages and make the blocks visible only to the certain roles associated with those links.

lourenzo’s picture

lourenzo commented

subscribe

augbog’s picture

augbog commented

If you go to your View page and go to the middle column under Page Settings, there is an option to change Permissions. You can change permissions so that only certain roles can see the page (simply select Role and then choose the roles you wish to allow to see the page).

If you need more fine grain control of people seeing certain content on pages, you can use some of the modules recommended before like Taxonomy Access.