Access Control

I need a way for one or two super users to grant access to nodes on a per user basis. I have tried nodeaccess but I don't get a list of which users have access to which nodes which is very important. And in order to grant access I need to type in a user's name. In the node edit, I would like a list of user names in the system with a checkbox for access. With nodeaccess I can't see how to remove access for a user, I only see a way to grant it. I don't want to grant accesss by role, that would mean making a new role for every new user.

I have a gallery setup whereby a gallery is a node and a gallery can have many child image nodes.

So far so good.

However, I would like to configure the setup so that when a user sets the node access permissions for the gallery (using UserRElationships Node Access), that same permission is applied to all child nodes.

I was thinking that this could be achieved in triggered rules, eg after a gallery is updated and after an image is created.

However I cant find out how I:

a) get the permissions of a particular node

and

b) set the permissions of a node.

We are building our new intranet on Drupal. We are a group of companies, i.e. our organizational structure consists of sub-companies, which again have sub-companies or departments, which also can have sub-departments and/or employees belonging to them. We need to have this organizational structure in our Drupal-based intranet system, both:
1) in terms of content: displaying the corporate structure as a hierarchical list of companies, sub-companies, departments; displaying employee listings per company and department;

Hi!
I have a site with organic groups. When a user submits a content type within a group I would like the user to choose between three levels of access for the node:
1) Open: the whole world (anonymous)
2) Restricted: authenticated
3) Private: members of the current group

Point 3) is achieved with the 'Public' check-box provided by OG, but how do I get point 1) and 2)?

I have tried simple_access and nodeaccess, but it doesn't seem to go well with OG. I am running D5.

Any ideas how to get this three levels of access on each node submitted within a group?

I'm considering developing a module to extend the functionality of TAC to role/field combinations. TAC works wonderfully for controlling access to whole nodes based on their taxonomy, but it's all-or-nothing; the module currently has no way of leveraging the per-field access control offered by Content Permissions.

I don't think the functionality belongs in TAC itself, as my proposed module is an additional layer of complexity that's specific to CCK content types.

Hi drupal !

I'm posting here to request a review of a module i'd just coded and that i would
like to submit on drupal.org. Before doing this, i would like someone to review
my module. Even if i'm pretty confident with my code which i've been testing for last
2 weeks, i would prefer others' advice.

About the module :
This module provides taxonomy based user control for user but unlike modules already
available on drupal.org with inheritance notion. For more information please read the
README (available below).

Thank you by advance.

Code is available here on github : http://github.com/baloo/taxonomy-access-user
Or as a tgz : http://github.com/baloo/taxonomy-access-user/tarball/master

Something I have had issues with on multiple sites I have worked on is administrative areas and permissions.

Example:
If I build a site for a client and then decide I want the client to be able to edit certain areas of the admin panel ("/admin/settings/site-information") but I don't want them to have full access to the administration area then there really isn't a good solution.

So, I ask... What exactly can be done about the issue? What would be some of the best work arounds?

I created a list of content permission modules that I have encountered with their weights on my system.

1. Can we create a comprehensive list?
2. How can they work together or should they. From your experience, what has been the worst and best combinations ?
3. what effect does module weight have on implementation of access? is it true that if access is already granted, it will not be restricted by another module that comes into play later?

Weight/ Name/ Version/ Brief description

0 Content Permissions 6.x-2.x-dev Set field-level permissions for CCK fields.
(admin determines)

Hi to all,

Our organisation recently decided to change our CMS from Joomla to Drupal. We would like to use groups on our site and organic groups seemed the obvious choice. I suggested this to our site designer but he immediately flag a concern with incompatibility of the Organic groups module with the ACL module as he found information in the OG handbook stating that "you can't use this module with other node access modules". He sent a query 2 weeks ago at http://drupal.org/node/384094 but has so far received no replies.

I also found a thread at http://drupal.org/project/og_user_roles which states that the OG user roles modules supports ACL. Does "support "mean that it is compatible? And does this mean that the OG module is as well?

Is the Organic groups module compatible with the ACL module? How can we use both OG and ACL modules together?