Skip to content

Instantly share code, notes, and snippets.

@debborafernandess

debborafernandess/spike_discover_sales_permissions_throught_codebase.md

Last active April 21, 2025 20:48
Show Gist options
  • Save debborafernandess/3e45a2f814fa05fccaf77ca5a65ef1af to your computer and use it in GitHub Desktop.
Save debborafernandess/3e45a2f814fa05fccaf77ca5a65ef1af to your computer and use it in GitHub Desktop.
Download ZIP
[INC-2654] Spike - Discover sales permissions throught the codebase
Raw
spike_discover_sales_permissions_throught_codebase.md

Check if there is any code directly referencing sales permission roles in code base

https://runway.powerhrg.com/backlog_items/INC-2654

Summary

There is currently an effort going on right now to migrate to a new role permission structure that is hierarchical that will replace the current permission. So, the goal of this spike, is to identify if any part of Nitro is directly referencing the following sales permission roles that would be impacted by the permission migration:

1. Remodeling Consultant and variations

No permissions occurrencies found throught the codebase for these titles/roles:

  • Remodeling Consultant
  • Remodeling Consultant Team Lead
  • Remodeling Consultant Mentor
  • Remodeling Consultant Sr Mentor
2. Director of Sales

No permissions occurrencies found throught the codebase for Director of Sales titles/roles.

3. VP of Sales

No permissions occurrencies found throught the codebase for VP of Sales titles/roles.

4. Remodeling Consultant and variations

No permissions occurrencies found throught the codebase for these titles/roles:

  • Quality Assurance PPM Trained
  • Quality Assurance Mentor
  • Quality Assurance Senior Manager
  • Director of Quality Assurance

Conclusion

It's possible to found the above titles/roles on queries or verbiage variations, but there's no occurrencies for none of them directly applied to permissions. That said, it seems safe to migrate to the new hierarchical role permission structure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment