Cannot Access Agile Board Backlogs, users get message "You do not have access to this backlog"Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Despite having the correct role assigned (scrum_user), users are no longer able to view backlogs under "Agile Development" >> "Agile Board" >> "Backlog". Steps to reproduce: 1. Login to the ServiceNow instance as User with scrum_user role2. Navigate to the Agile Board > Backlog tab 3. Notice that it's now empty when there should be some backlogs on there. You see the message below: You do not have access to this backlog Ask the backlog owner to share it with you Release All Cause In your instance you have activated the REST API ACL. Access Control: Table API /nav_to.do?uri=sys_security_acl.do?sys_id=9ef8bc918733320025fbd1a936cb0bdd Note: The sys Id may differ in your instance ACL's on rest api tables(Table API) are deactivated OOB by default. However if the REST API ACL is activated, a user must have the snc_platform_rest_api_access role to make a request to that REST API. Resolution When the 'TABLE API' ACL is activated, if a user does not have the snc_platform_rest_api_access role, he cannot access the Agile board. This is the expected behavior. Please refer to the documentation REST API ACL's in https://developer.servicenow.com/app.do#!/document/content/app_store_doc_rest_integrate_kingston_c_RESTAPISecurity?v=kingston As possible solutions try either of the below that meets your requirement 1. Give your users the role 'snc_platform_rest_api_access' 2. Alternatively to change the default behavior you can Modify the TABLE API ACL as following: - Remove requires role 'snc_platform_rest_api_access' -Add Advanced script as below: answer = (gs.isInteractive()) || gs.hasRole('snc_platform_rest_api_access'));