The documentation states

So one can install the ACL module and set per user access control settings per content node.

I have enabled both content access and ACL, but cannot find any per-user capability.

Having not done this before, I'm not sure where to look. I expected to see something in the Content Access tab of a content type, but it is not there.

Has this even been implemented in D7 or is it only in D6?

Comments

zeezhao’s picture

You have to enable on the specific content types via link admin/structure/types.

Edit your content type to enable via "Access Control" tab for the content type.

David4514’s picture

That much I did understand. The impression that I got from the description was that it was possible to give specific users access to content if you combined both Content Access and ACL.

Instead I get the ability to allow anyone to View|Edit|Delete content or for the owner of content to View|Edit|Delete content all qualified by roles.

However, other than through assignment of roles which I could do without ACL, there does not appear to be a way to say that John and Jane have Edit capability for specific content.

Possibly I am not understanding what "per-user" access control means. The description gave the impression that access to content could be directly assigned to a user.

zeezhao’s picture

Yes you can. That's what "Enable per content node access control settings " does. Set this first.

Once you do this, you will be able to grant access to specific users to a specifc node. You will see this on a node via its "Access Control" tab.

Have a look at any of your nodes for the content type you've enabled it for. You will see "User Access Control Lists" section.

David4514’s picture

I never thought of looking there. It was not done in the way that I expected (no big news there!). At minimum, a note should be included in the "Enable per content access control settings" that indicates that this is where you can set per-user access permissions if ACL is enabled. If I had seen such a note, I would not have look all over for where to set the per-user permissions.

I was expecting/hoping to associate per-user permissions to the content type as a whole rather than requiring that it be set on each and every content instance. At least it would be nice to be able to set a default.

I really did not want all users that may have edit/create permissions for the content to be able to alter per-user permissions (or any other permissions). However, if the user does not have permissions to edit content access, it will not be possible to set per-user permissions at all on content they create.

So it seems that if I wish to keep tight control over content access (i.e. Content creators should not have the ability to control any permissions. Only a few administrators will have that ability) that I may need to use roles (possibly a lot of them) to accomplish this.

Any ideas.... BTW Thanks for your help!!!!

zeezhao’s picture

The way I have done that in past is by using roles, even if it means one person in a role...

The other alternatives are:
- use rules module to grant access based on content type
- Write a small module that grants access based on your criteria.

gratefulsk’s picture

I am using Content Access + ACL for a per user access control which is great, but it is starting to get very cumbersome. I agree with David4514 that having the per user functionality for a whole content type would be a great addition.

romaingar’s picture

Same problem, same request is there a way to have a user/content type access control ?
Thanks.

pipep’s picture

+1

not working for me neither.

breezing65’s picture

Unfortunately, I'm having the same issue with Drupal-7.16. Both the Content Access and the ACL modules are installed and there is no access control tab in the user interface for content type nodes. Thus, I'm unable to configure role based access control settings as well.

zeezhao’s picture

Make sure permissions are set via: admin/people/permissions
"Content Access", etc.

Also see comments in #1 and #3 above.

kaizerking’s picture

yes. it is bit of confusion there, but it works excellent
The confusion is caused by the role based form,it is difficult to understand the purpose of it, hence you get confused,
Another reason for confusion is, the 'per node access control setting' check box when checked does two things.
1. it enables per node control
2. it enables per user control
these two are linked obviously if the user do not have access control permissions for the node then he cannot control per user access control. It is nice realm logic.

if you have ACL then only the field set list is displayed below the role based form with view access update access and delete access, collapsible forms with a auto complete field where you can select user.
here another confusion may arise. when you add a user to whom the permission is to be given the user name appears with a check box the check box only should be used to delete the user the appearance of the user name is sufficient. after you add the users then save .This depends on the permissions the author has .
When per node control is enabled then only the user(author) will get the access control page other wise no.

What I did not understand is how to "add a user to ACL" through rules.
We have the event 'user added to ACL' which will help in linking up further actions on the user. but not "Add user to a access control list '.
How to add a user to a User access control list? can some one help me in this

jamescarvin’s picture

I don't have ACL but in attempting to update Content_Access for Basic Pages I get the following error repeatedly ... Notice: Undefined index: type in content_access_admin_settings_submit() (line 180 of .../public_html/sites/all/modules/content_access/content_access.admin.inc).

marianojp’s picture

I've installed content_access and acl module using Drupal 7.34. I set the permissions and enabled PER CONTENT NODE ACCESS CONTROL SETTINGS
/admin/structure/types/manage//access.

Am I missing something?

gisle’s picture

Version: 7.x-1.2-beta1 » 7.x-1.x-dev
Issue summary: View changes
Status: Active » Closed (outdated)

This issue has not received any updates in the previous 5 years. If you believe it to still be relevant, you are encouraged to reopen the issue and update it.

If you got an email about this Issue status update, it is because you at one time (possibly a very long time ago), subscribed to it. To learn how to unsubscribe yourself, please visit: https://www.drupal.org/project/webmasters/issues/3142987