Answers.Body: <p>If this is problematic it could be easier to provide these as Webforms which have fine grained access settings</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-23T19:37:39.067Z
Answers.Text: Note that unless you use some other level of acl in drupal the webform 'node' itself will be visible to anon, just the 'form' part which can be hidden via the webform settings
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-23T19:55:09.513Z
Answers.Text: Yep. I'm using Nodeaccess in this case I think to control which roles get to see which nodes.
Answers.UserDisplayName: Graham
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-22T20:03:37.633Z
Answers.LastActivityDate: 2015-09-22T20:03:37.633Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>I want to set up some profiles that are visible and editable only to Drupal users with a given role. However it looks like regardless of the permission settings I use, all users can see the profiles in their user account. Is this expected behaviour?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-09-22T20:03:31.820Z
Comments.Text: Can you explain how you think you have fine grained control over permissions to see a Profile?
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-09-23T08:33:58.753Z
Comments.Text: The approach I've taken is to turn off all the profile-related permissions and custom field access permissions in Drupal's permissioning, and then set up Civi ACL's to enable relevant groups of users to view and access given profiles and custom fields. It sort of works, but what I'm seeing is, that regardless of the user's role, when they edit their user account they can see the tabs with the names of the profiles. If they click on one of the tabs they get an error message. I guess I could hide the tabs with CSS, but I shouldn't need to do that. Am I doing it wrong?
Comments.UserDisplayName: Graham
Tags: <drupal><permissions><acl><user-account><roles>
Title: Can I control visibility of CiviCRM profiles that are used for "View/Edit Drupal User Account" using permissions and/or ACLs?
ThreadText: # Can I control visibility of CiviCRM profiles that are used for "View/Edit Drupal User Account" using permissions and/or ACLs?
  
  (Asked by: username_0 on 2015-09-22)
  
  I want to set up some profiles that are visible and editable only to Drupal users with a given role. However it looks like regardless of the permission settings I use, all users can see the profiles in their user account. Is this expected behaviour?
  
  **Tags:** drupal, permissions, acl, user-account, roles
  
  > **Comments:**
  > **username_1**: Can you explain how you think you have fine grained control over permissions to see a Profile?  
  > **username_0**: The approach I've taken is to turn off all the profile-related permissions and custom field access permissions in Drupal's permissioning, and then set up Civi ACL's to enable relevant groups of users to view and access given profiles and custom fields. It sort of works, but what I'm seeing is, that regardless of the user's role, when they edit their user account they can see the tabs with the names of the profiles. If they click on one of the tabs they get an error message. I guess I could hide the tabs with CSS, but I shouldn't need to do that. Am I doing it wrong?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-09-22. Score: 1
  
  If this is problematic it could be easier to provide these as Webforms which have fine grained access settings
  
  > **Comments:**
  > **username_1**: Note that unless you use some other level of acl in drupal the webform 'node' itself will be visible to anon, just the 'form' part which can be hidden via the webform settings  
  > **username_0**: Yep. I'm using Nodeaccess in this case I think to control which roles get to see which nodes.  
  
  ---
  
  