HubSpot Permissions Need Greater Flexibility & Navigation Should be Universal

Status: Idea Submitted

As our organization works to implement HubSpot Service Desk module as a replacement for our internal global ITSM application, there are many elements within the system which have become substantial obstables, from permissions and security to team usability.

  1. Separation of functional components from one another in HubSpot, as required by different functional groups --

With the tool handling more than one group function, it is critical that any organization be able to silo functions and permissions for those functions from other groups and teams. Help Desk, as an example, should not be visible to our full end-user base, regardless what tickets the users can see. Nor should service desk configuration be grouped with sales or marketing configuration elements. Security is a big part of any ITSM tool you can find on the market.

  1. Lack of control over user permissions and visibility of system pages/areas --

If needed for any user roles, an organization must have the ability to completely turn off every component and component permissions should include each navigation element independently. There are many main nav elements which share permissions in HubSpot - this should not be the case. Also, most of the component toggles in place throughout permission sets are disabled and cannot be turned off even by a super admin. HubSpot should in no way dictate to their customer what our end users should and should not have access to. This flexibility must be given to the org system admins so an organization has full control over permissions for each component in the HubSpot system.
Secondly, if a component is completely turned off for any permission set, those components and pages should no longer be visible to users assigned to that permission set. This means, those items should no longer appear in the user’s navigation. As it is, even when locked down, there are pages all over the system users can access and hit a “you do not have permission” or an empty page. This is against general best practices for any UI / UX.
These points are also imperative to lock down visibility of active development (config) which has to take place in production since we cannot build in sandbox and push changes to the live environment. Currently, our users can see various areas of config in progress, which is poor practice.

  1. Main navigation usability is confusing for non-Sales/Marketing teams --

System navigation (including main nav and settings) seem to be created by sales and marketing minded people for sales and marketing users only. Finding components which will be used for IT and security is difficult when buried in menus for marketing, CRM, Content (catchall for randon items not all specific to “content”), especially on the settings side. With other functional groups now accessing the HubSpot system for various needs, such as service desk to start, HubSpot needs to adapt the navigation organization and verbiage to be more universally compliant and understood among any user type or function.

We very much need to see some major improvements in these areas. Permissions especially should be 100% opened up to an organization for proper control and security across components for independent group functions. This is causing many problems for us in consideration of security and insurance audits for a service desk implementation. Thank you