As of now all content is viewable by an autonomous user.
But i want some content viewable, and some not.
how do i do this?

Comments

cog.rusty’s picture

Here you will find several access control modules.

http://drupal.org/project/Modules/category/74

You can use one, according to how you want to restrict access. For example, to restrict some content types you can use the Content Access module. Or, to restrict content tagged with some categories you can use TAC Lite (or Taxonomy Access (TAC) if you also want to restrict creating/editing content with some categories). For access control for individual nodes see the Nodeaccess module. For subscriber groups see Organic Groups (OG).

Consider how you want it to work and choose only one, otherwise it is possible that one will allow what another one forbids.

Other options are the Path Access module and the Premium module, which can coexist safely with any of the above. The Premium module can show teasers while protecting the rest of the content.

rigdzin’s picture

I want that I have a web page with information and content,
but if people are users they can have private content that is hidden to anonymous users. and beyond that there is content for only specific users.

darumaki’s picture

Something I've been finding as a new drupal user, there are many modules but many are so complicated and difficult to understand, unless you are from another planet.

How about just one fully functional restriction module that does what we need it to do restrict access to content, multiple user groups, we create a page and simply restrict it to a usergroup, what ever happen to simple stuff.

I'm almost scared every time i click on the module list, 50 modules of the same thing and not one that makes any sense

belmondo’s picture

yes, I agree with darumaki, there are quite a few modules that do almost the same thing and it is not clear which one to choose. There needs to be some control mechanism by the Drupal gurus to decide what modules are 'allowed'. I have noticed that for access control, most modules have a huge overlap in functionality and with a managed community effort all of this could probably be brought into just one module . What happens now is that instead of adding the required functionality to an existing module, somebody has created a totally new module. Anyway, with a bit of trying out different modules I have so far been able to get the functionality I want and have never had Drupal crashing, great!

cog.rusty’s picture

People have different needs and those access control modules, with one or two exceptions, are very different. Also, most modules are initially written by developers who work on a project, to cover their own needs.

To choose one, consider the following:
- Who can give permissions. An admin? The author?
- To whom are the permissions given? Individual users? User roles? Subscriber groups?
- Permissions for what? For individual posts? For content types? For posts tagged with some categories?
- Permissions to do what? To view? To list? To create/edit/delete?

The more things a module can do, the more complicated its setup.