My client created a new worker (role) account for special flow and he realized the worker role had access to several pages they should not have. I inherited this app, so I don’t intuitively have a catalog of all the login permissions in my memory. Thus I needed to audit which roles can access which pages in knack.
I didn’t see a good solution to summarize the role-based access, so I added a new feature to Knack Sleuth to generate a review of all role based page permissions.
Key points:
- The tool will spit out high-level summary to screen and generate a CSV
- By default it will include all scene’s in your application
- if you use the
--summary-onlyflag, it’ll only includemenuitems orloginitems
Here’s my example usage (with the summary-only flag):
Here is sub-set of what is in the CSV. First the summary results:
Hopefully it’s all self-explanatory, but two profiles have access to the Announcements pages.
The “root_nav” = “Announcements” means that Announcements is a menu (also noted in the nav_level column)
Here are the same row, but showing the 1 child scene that had been summarized above with the --summary flag.
Again, two roles have access to the related announcement pages.
Just FYI, my previous posts on Knack-Sleuth:
- YAKET - Yet Another Knack Exploration Tool … except I called it knack-sleuth … and it’s Command-Line / for the terminal.
- Export your knack database schema to JSON-Schema, YAML, DBML, Mermaid ERD
Let me know if you have any questions or feature requests.
Happy Holidays everybody!