Les grands esprits se rencontrent

At the moment permissions on Forms is a simple on/off toggle. Whilst turning this off provides a lot more control to the admin team on forms being created/edited by other team-members, it also takes away a lot of functionalities related to forms for other users (reporting on forms, creating lists based on forms, etc.). Is there anyway we could have more granularity on form permissions as we do for other functions on Hubspot? ... Afficher plus

I would love to give sales managers access to create templates for their team, however i don't want to give them super admin permissions for our whole account! Please amend the permissions functionality to allow this. ... Afficher plus

There are some features/tools/capabilities within Hubspot that we do not use as a result of SOP's or necessary process within our ERP. There are others that we simply do not use for no real reason other than they aren't necessary for our business. To avoid confusion among our users and to simplify, it would be beneficial to be able to turn these features off in the menu/navigation.    For example, we do not use the Quoting capability because we create quotes in our ERP system so if/when they are approved/accepted, that quote can simply but associated to a PO and all the qty's, products, services, etc... are already there for order entry.   However, having the feature visible to our sales team causes confusion as to where they should create the quote.    Another feature that we are not currently using is Forecast. Our forecasting process is a little more complicated and detailed than what Hubspot's forecast feature offers so we do that externally.    In short, would be nice to be to remove certain tools/features from the menu/navigation to avoid confusion, declutter, and simplify. ... Afficher plus

We use goals to enter a monthly quota for sales reps.  Unfortunately, there is not a way to import a spreadsheet of 30 sales reps into goals.  I have to manually enter each month for them.  Would love to import the whole spreadsheet. ... Afficher plus

Hi    The current export permission simply provide on/off functionality, you can either export everything or nothing.    It would be great to break this into more granular levels such as    - by object (including individual custom objects)  - by level i.e. can export all records / can export filtered records etc.    This would be a feature that many security teams would be pleased with, it allows us to restrict access in line with other business systems. Currently everything needs access to everything when most user just need reports or some need contacts etc.   Hoping this gets looked at!   Thanks ... Afficher plus

I'd like to be able to control who (which team) can merge certain records. For example, an integration we have will break if two records are merged. The team using the integration should obviously be able to edit the records they are assigned but shouldn't be able to merge the records. ... Afficher plus

With more businesses now moving to cloud apps and businesses looking to secure these SSO should be available on some of the lower tiers not just the Enterprise tier. With the likes of Azure Active Directory, G Suite, Okta etc more midsized businesses are also implementing SSO not just top tier enterprises. The price difference between professional and enterprise is to prohibitive for a SME to use enterprise with Hubspot. Hubspot also feature on https://sso.tax as one of the worst offenders for price to enable SSO. ... Afficher plus

The New Lead Object is fantastic however the lack of granular settings is a massive roadblock when it comes to team adoption of the tool.  For example; we can only give users access to all prospecting workspaces or only their workspaces - what about global companies with multiple team levels Example 2; we cannot create custom lead properties that are only visible & editable to specific teams (important for multibrand companies). With any custom property created, when cannot customise the lead area display to ensure teams are looking at the core set of properties for this object  Example 3; when it comes to properties there is no setting to restrict which properties are editable and which are not - the system will preset some of these properties and should not be editable by the individual sales users There are many more instances where the default functionality within other objects has not yet been brought into the lead object. Teams are used to the set-up and functionality within HubSpot being mirrored across objects, and this stark difference with leads results in frustration towards a fantastic tool. ... Afficher plus

I want to suggust to the HS product team that you address some of the limitations to Team membership.    I recently learned that if a user is listed in a team as an 'Extra' team member, that this limits certain functions. For one thing, they cannot be included in round robins.    I was excited by the potential for adding nested teams/subteams to larger teams, and adding users as 'extra' team members, as I felt this would provide several benefits.    Example A: Regional sales team round robins.    We have a team for our Enterprise Sales Department called "Enteprise Sales" the team includes any and all enterprise sales staff.    I went and created 2 subteams: Enterprise East, and Enterprise West, since certain staff are assigned to west coast leads, and some are assigned to east coast leads. However, the sales reps had the East/West teams as their 'extra' team membership, and so when I went to add those nested teams to the round robin I discovered I wasn't allowed to because 'extra' team members do not show up in round robins, and the east/west teams consisted entirely of 'extra' team members.   At first I thought this was a simple fix and I could just make the 'parent' departmental enterprise sales team to their 'extra' team membership (since it isn't as important from workflows.)    However, that ultimately did not appear to be an option, since 'extra' team members are not included on reports that are filtered by teams, and we have many dashboards/reports that are filtered on the primary, departmental, 'enterprise sales' team.    2.) Workflow maintenance   Another reason I was excited for subteams and 'extra team' memberships was because I thought it would make workflows much easier to manage moving forward, especially as our company continues to grow and expand.    For example: the average sales rep with a HS user account is incorporated into dozens of workflows. In the event that a sales rep leaves the company, or changes positions, we have to remember the 12+ workflows that need their steps and branches to be edited and updated whenever a staff person needs to be added or replaced.    A HUGE improvement would be to create subteams that only include 1 single user (for example: creat a Subteam called "Regional Sales Manager: Florida" and then assign the Florida regional sales manager as the one and only team member.)  Then our plan was to edit all of our workflows so that no branch is ever based around a specific user account, but rather steps and branches are based around that user's unique subteam. That way, if our Florida Regional Sales Manager leaves the company or changes roles, and somebody new is placed in that position, the only thing I need to edit is that new user's HubSpot Subteam, as opposed to spending tons of time editing dozens of workflows, and risking forgetting or neglecting to update one or two.  I'm honestly not certain what the function or utility is to subteams and 'extra VS main' team membership if users are limited to 1 main team and 'extra team' membership limits reporting, round robins, routing and notifications. Freeing it up so that people can be on multiple teams and still have all of the available features of a 'main team member' seems like it would 10x the value of having users on multiple teams.    I hope this feedback is helpful.  ... Afficher plus