Las grandes mentes piensan igual

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. ... Mostrar más

Our sales team does not have access to export contact records, but they do need the ability to export reports. The current permission is all or none, so now we (marketing admins) have to pull the reports and send it to them. It would be great to modularize these permissions. ... Mostrar más

Feature Request:   All team members, regardless if they are primary or secondary team members should be included in the reporting tool. There are many times when a Deal Owner may play a fundamental part in two different teams, and should therefore not be excluded in the reporting for that team.    At the moment, it is a limitation that almost defeats the purpose of having teams. It would be brilliant to see in a future product rollout 🙂 ... Mostrar más

As a HubSpot Partner, we're often charged with building out email templates, snippets, chat flows, deal pipelines, service pipelines, etc. as part of a client engagement.   Yet, unless, as a Partner Employee, we do not have proper "Seat" access to one of the paid plans, we are unable to execute these tasks on behalf of our clients.   This hinders our ability to deliver solid service and creates inefficiencies in our processes.   Please create a way for Partner Employees to bypass the "Seat" requirements to access certain features of paid Sales Hub and Service Hub plans. We're not the ones actually using these tools, but end up not being able to help our clients use them better because we don't have access without a paid seat.   Thanks!   EDIT: I know there's a form we can fill out to request access, but that's an unnecessary step. As Partners, it should come with the territory and be default for all partner employees on a client portal: paid seats are not required. ... Mostrar más

Hey HubSpot,   We'd love to see something in the way of adding conditional logic as to WHEN somebody can edit a property rather than just WHO can edit/see etc   E.g When the Deal is Deal Stage "Pending Approval", properties such as "Conditions", "Amount", "Submission Date" cannot be updated.   This would allow for greater confidence and control around time crititcal processes and ensuring that information is not being incorrectly updated after a submission where details must remain the same for verification purposes etc   Ideally this would be similar to, but is not quite the same as User Permissions on Properties.   Thanks! ... Mostrar más

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. ... Mostrar más

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? ... Mostrar más

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 ... Mostrar más

This issue has been brought up a few times in the Community, but it doesn't look like it was added as an Idea.   When an employee leaves, we deactivate their account in HubSpot. This allows us to preserve historic detail. This is great and something that we want.   However, the deactivated user is still available to be assigned as an owner of stuff. It should be possible to prevent a deactivated user from being assigned to anything after they are deactivated. ... Mostrar más