CiviCRM Community Forums (archive)

I get so confused about how there's no "deny to everyone except" option with CiviCRM Access Rules.

I have created a profile that shows up under a logged in user's Drupal User Account Profile to that he/she can update it.  It's a volunteer application and I only want it to show on the Drupal user profiles of Drupal Users with the role of "Volunteer Applicant".  I've created a synced "volunteer Applicant" GROUP AND ACL ROLE in CiviCRM and then an ACL rule granting them access to the Volunteer Application.

But what's the point?  If an ACL can't DENY everyone ELSE the ability to see a profile, then what good is it?  what good are CiviCRM access rules?

Or am I missing something?  The Volunteer Application shows up for EVERYONE, which can be confusing for non-applicants.

How do I create an APPLICATION profile and set it so that ONLY VOLUNTEER APPLICANTS can see it? 

Thanks in advance.

OK, forget it!  I figured it out finally.  You have to remove profile view permissions in Drupal from authenticated users.  this also removes the name and address view from "My Account" in Drupal, so then you have to add that profile to an ACL giving VIEW access to everyone.

The rule I didn't get was/is:

Drupal handles ALL DENIAL of access and OVERGRANTS access when you allow CiviCRM features.
To use CiviCRM ACLS at ALL with Drupal, you need to turn OFF more Drupal permissions so that the CiviCRM ACLS can "give them back".