Welcome! This forum has a treasure trove of great info – Scouters helping Scouters! Just a heads up, though - all content, information, and opinions shared on this forum are those of the author, not the BSA.
I am my troop’s unit advancement chair. Until recently I have been able to use the New Custom Roster Report in ScoutBook Plus. I use that for individual and patrol reports for the Senior Patrol Leader, Scoutmaster and committe.
Beginning this week when I try to access the New Custom Roster Report I receive the following message in red font:
Access to report is denied. You do not have required positions/permissions to run this report.
Why is this happening? I cannot perform the needed tasks for the troop with access to Report Builder.
When will the custom reports permissions issue get fixed? I cannot run reports by patrol like I was able. I cannot creat my own custom reports. I am useless to the Scoutmaster and SPL and PLs without the ability to provide them the information they need to make decisions.
When I try to creat a report as I always have done in ethe past I keep getting the message:
Access to report is denied. You do not have required positions/permissions to run this report.
be interested to hear if anyone found an update. I am aslo an advancement chair and relied heavily on my custom reports. We have a large Troop and doing manul checks of each Scout is not scalable.
Came here today looking for information on why I can’t run a roster report. I guess I’m not the only one. I’m posting to let everyone know that I am having the same issue as the Unit Adv Chair. Hope it’s fixed soon.
Scoutbook is a great tool. I appreciate that Scouting America is working to upgrade.
However, having the Individual Permissions granting one action to users while Registered or Functional Positions give a Group of Permissions to specific users is bureaucratic, unhelpful and exceptionally counterproductive.
The custom report function was not broken in the past. Why is there a need to “fix” what was not broken?
Each unit has a different set of circumstances unique to their organization. Vetted adult volunteers may have one registered functional role but fill several other unique or functional roles as well. Having an unknown entity decide for thousands of people how we process information and what functions we’re permitted in a cookie cutter system is exceptionally unhelpful to everyone.
Following the new position specific permissions rules, Scoutmaster and Committee Chairs need to go back and forth with every single volunteer granting individual permissions for each person to do a very specific function. This is a huge drain on their time with each volunteer. “Does it work now? How about now? “ This is beyond the realm of excessive uselessness.
We need the ability for everyone to create reports in the way they comprehend and use the data. Limiting custom reporting is a waste of precious volunteer time. How information is presented to one person is unique and understandable to them alone. Custom reports are as varied as each of the individuals who uses them.
I recommend restoring the custom report functionality to all committee members and position specific vetted volunteers. Scoutmasters and Committee Chairs then could restrict specific function by exception instead of having to grant permissions individually.
I’m our troop merit badge coordinator - I provide lists of in-troop MBCs to our Scouts. Without the ability to generate the report, we’re dead in the water. I have some older lists I can query, but obviously they can’t be counted on to be up-to-date.
@StevenSheldon- well a merit badge co-ordinator is not a real position so your rights and permissions would need to be adjusted based on you registered position. Watch the change log for an update for custom report access.
Yup, just adding my voice to the others to raise the importance of the issue. Gotta squeak if you want the oil. I don’t bother watching the change log, just the functionality.
It can sometimes make a difference when still trying to identify a root cause or if your issue broadens the original issue. I appreciate it being reported again if you aren’t sure.
