Answers.Body: <p>Obviously, the CiviSEPA extension messes with the menu for users without administrative permissions. Disabling this extension in the ACL for the non-admin groups solves the problem</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-19T19:29:37.233Z
Answers.LastActivityDate: 2018-12-19T19:29:37.233Z
Answers.UserDisplayName: Andreas Klein
Body: <p>I am using CiviCRM 5.8.1 (update to 5.8.2 will be done shortly) on Wordpress 5.0.1 with German localization. For extended permission management on WP, I use Advanced Access Manager.</p>
  
  <p>I created a group for the office users and granted them access in CiviCRM - Administration - User and Roles - Access control and granted them all necessary permissions including CiviCRM access.</p>
  
  <p>Wordpress and CiviCRM user are properly matching (the WP user ID is listed the respective contact of the CiviCRM user).</p>
  
  <p>Nevertheless, except for users with the WP Administrator role, all menu items of the CiviCRM backend except for search, contacts and CiviSEPA Dashboard keep invisible. </p>
  
  <p>I tried it with different groups and also ensured that on the WP side, all capabilities in AAA with relation to CiviCRM are enabled.</p>
  
  <p>To exclude side effects I removed all previously existing CiviCRM specific permission configurations (except for the administrator), including CiviCRM groups, allocations between WP and CiviCRM groups and ACL.</p>
  
  <p>Anybody an idea where else to look? I tried to find hints by searching but presently I am stuck. Thanks!</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-19T16:31:40.723Z
Comments.Text: After some further tries, I disabled the CiviSEPA permissions for these WP roles and the other menu entries appeared.
Comments.UserDisplayName: Andreas Klein
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-19T19:01:41.407Z
Comments.Text: Hi Andreas - it sounds like this is an 'answer'. perhaps you don't have enough reputation yet, but when you do, pls add it as an Answer and 'accept' it. thanks.
Comments.UserDisplayName: petednz - fuzion
Tags: <wordpress><groups><permissions><acl>
Title: CiviCRM access for Wordpress custom group users
ThreadText: # CiviCRM access for Wordpress custom group users
  
  (Asked by: username_0 on 2018-12-19)
  
  I am using CiviCRM 5.8.1 (update to 5.8.2 will be done shortly) on Wordpress 5.0.1 with German localization. For extended permission management on WP, I use Advanced Access Manager.
  
  I created a group for the office users and granted them access in CiviCRM - Administration - User and Roles - Access control and granted them all necessary permissions including CiviCRM access.
  
  Wordpress and CiviCRM user are properly matching (the WP user ID is listed the respective contact of the CiviCRM user).
  
  Nevertheless, except for users with the WP Administrator role, all menu items of the CiviCRM backend except for search, contacts and CiviSEPA Dashboard keep invisible.
  
  I tried it with different groups and also ensured that on the WP side, all capabilities in AAA with relation to CiviCRM are enabled.
  
  To exclude side effects I removed all previously existing CiviCRM specific permission configurations (except for the administrator), including CiviCRM groups, allocations between WP and CiviCRM groups and ACL.
  
  Anybody an idea where else to look? I tried to find hints by searching but presently I am stuck. Thanks!
  
  **Tags:** wordpress, groups, permissions, acl
  
  > **Comments:**
  > **username_0**: After some further tries, I disabled the CiviSEPA permissions for these WP roles and the other menu entries appeared.  
  > **username_1**: Hi Andreas - it sounds like this is an 'answer'. perhaps you don't have enough reputation yet, but when you do, pls add it as an Answer and 'accept' it. thanks.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-12-19. Score: 1
  
  Obviously, the CiviSEPA extension messes with the menu for users without administrative permissions. Disabling this extension in the ACL for the non-admin groups solves the problem
  
  
  ---
  
  