Answers.Body: <p>We had the same issue and same resolution, but agree, it doesn't feel right. I opened an issue in the lab but couldn't find anything else: <a href="https://lab.civicrm.org/dev/drupal/issues/45" rel="noreferrer">https://lab.civicrm.org/dev/drupal/issues/45</a></p>
  
  <p>EDIT: Maintainer/owner "colemanw" replied to the issue: </p>
  
  <blockquote>
    <p>Looks like "access CiviCRM" was recently renamed "access CiviCRM backend and 
    API" I assume to enhance clarity but it seems to have caused some confusion.
    But it's true, you should only allow trusted users to access your CRM.</p>
  </blockquote>
  
  <p>EDIT2: More info from colemanw:</p>
  
  <blockquote>
    <p>Right, "access CiviCRM" or whatever it's called now is the gatekeeper, the minimum permission needed to access any part of CiviCRM. It is required to have that permission before doing anything.</p>
  </blockquote>
  
  <p>Looks like we had the right idea!</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-22T18:38:51.120Z
Answers.LastActivityDate: 2019-01-22T18:54:17.323Z
Answers.LastEditDate: 2019-01-22T18:54:17.323Z
Answers.UserDisplayName: joegl
Answers.Body: <p>I solved this with trial and error.  I had to grant access to : </p>
  
  <p>CiviCRM: access CiviCRM backend and API
  Master control for access to the main CiviCRM backend and API. Give to trusted roles only.</p>
  
  <p>I'm having trouble believing that this is really a basic setting for access to CiviCRM, since it's flagged as 'trusted roles only'.  I'm not clear what's covered by the term 'CiviCRM backend and API'.  What function(s) within CiviCRM require this Permission?</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-16T16:51:01.127Z
Answers.LastActivityDate: 2019-01-16T16:51:01.127Z
Answers.UserDisplayName: Kenneth Baumann
Body: <p>IDs that previously were able to use CiviCRM now get 'Access denied - You are not authorized to access this page.'.  (i.e. /civicrm/dashboard) These Ids can log in to Drupal. I may have caused this with some Role permission changes.  I've fiddled with many of the Role permissions to no avail.  We use ACLs to limit access to contact records.</p>
  
  <p>What's the necessary subset of Drupal Role permissions to gain access to CiviCRM?</p>
  
  <p>Drupal 7.61
  CiviCRM 5.9.0</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-01-22T20:27:27.093Z
Comments.Text: by IDs did you mean Users?
Comments.UserDisplayName: petednz - fuzion
Tags: <drupal><permissions>
Title: Access denied for specific role
ThreadText: # Access denied for specific role
  
  (Asked by: username_0 on 2019-01-16)
  
  IDs that previously were able to use CiviCRM now get 'Access denied - You are not authorized to access this page.'. (i.e. /civicrm/dashboard) These Ids can log in to Drupal. I may have caused this with some Role permission changes. I've fiddled with many of the Role permissions to no avail. We use ACLs to limit access to contact records.
  
  What's the necessary subset of Drupal Role permissions to gain access to CiviCRM?
  
  Drupal 7.61
  CiviCRM 5.9.0
  
  **Tags:** drupal, permissions
  
  > **Comments:**
  > **username_1**: by IDs did you mean Users?  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2019-01-22. Score: 8
  
  We had the same issue and same resolution, but agree, it doesn't feel right. I opened an issue in the lab but couldn't find anything else: <https://lab.civicrm.org/dev/drupal/issues/45>
  
  EDIT: Maintainer/owner "colemanw" replied to the issue:
  
  > Looks like "access CiviCRM" was recently renamed "access CiviCRM backend and
  > API" I assume to enhance clarity but it seems to have caused some confusion.
  > But it's true, you should only allow trusted users to access your CRM.
  
  EDIT2: More info from colemanw:
  
  > Right, "access CiviCRM" or whatever it's called now is the gatekeeper, the minimum permission needed to access any part of CiviCRM. It is required to have that permission before doing anything.
  
  Looks like we had the right idea!
  
  
  ---
  
  ### Answer by username_0 on 2019-01-16. Score: 6
  
  I solved this with trial and error. I had to grant access to :
  
  CiviCRM: access CiviCRM backend and API
  Master control for access to the main CiviCRM backend and API. Give to trusted roles only.
  
  I'm having trouble believing that this is really a basic setting for access to CiviCRM, since it's flagged as 'trusted roles only'. I'm not clear what's covered by the term 'CiviCRM backend and API'. What function(s) within CiviCRM require this Permission?
  
  
  ---
  
  