Is it correct that you need Super Admin rights to access the CRM Development Tools? I've just had a developer who needed to generate a personal access key. He's not a Super Admin, and while he was able to tick all other scopes, the Developer Projects one was greyed out.
I manage portals for clients, and limiting this access to super admins only seems counterproductive. Most of my clients get very nervous when we put a developer (who comes from one of our partners) into the account as a super admin. I'd very much prefer it if they were limited in their access to other parts of Hubspot, but could still do all of the work with CRM Development Tools.
Provisioning a developer with Super Admin access is needed to access the CRM development tools (dev sandboxes, projects, and personal access key). We plan to allow much more granular control with permission settings to these tools so they can be provisioned without needing Super Admin access.
We have a private beta running for a new developer permission set, which grants users access to developer tools without having to make them a super admin. The beta also includes a developer permission template, which includes a set of pre-selected permissions that a developer should need to do their work.
The developer tools access permission can be applied to a user account by manually enabling the toggle, by assigning the 'Developer' template above, or by adding it to a custom permission set and assigning this set to the user.
The steps to join the beta can be found inthe KB here(name: 'New Developer Permission Set')
Please feel free to reach out to me with any feedback on this feature!