Las grandes mentes piensan igual

At the moment, all users who have the permissions to edit and publish a page can also delete it:     Similar to workflows, it would be great to have the additional option of deletion permissions:     Without this additional permissions, admins have to always live in fear that landing pages are deleting without them finding out about it.   Not all users who delete a landing page necessarily think about required follow-up actions - like setting up a redirect. And even if they do, they shouldn't necessarily have the permissions to set up redirects indiscriminately.   Landing page deletion permissions would add another level of control in big organizations and help admins avoid catastrophes. ... Mostrar más

HubSpot admins need to be able to prevent users from accessing the "edit columns" (see below) button while working in the Line Items editor / in the Quote tool.   Currently, users see the button "edit columns" and they are free to take advantage of making the tool suitable for their personal needs. This, in turn, complicates the lives of their colleagues and HubSpot admins.  As a CRM aimed at scaling businesses & enterprise customers, HubSpot should prioritize such an update with high priority.     ... Mostrar más

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

Currently, anyone with assigned sales or service seats (and their teams) will appear in the forecast tool. I would love a way to exclude users/teams who do not need to be reported on in the tool, as not all of our paid users have a quota. It would be a bit easier for our senior leadership team to digest the information that includes the teams that actually matter to our revenue goals.   Thank you! ... Mostrar más

There seems to be a setting that can restrict a user from creating access groups (I have not bothered identifying it), but there isn't one to keep users from adding individuals to existing access groups. That is a bit counter-intuitive. Currently, any and all users can grant any of their contacts access to restricted content. Please add a permission to restrict this! ... Mostrar más

My team are struggling with the space the new sidebar takes up when it is hovered over, as it blocks a lot of their view.  Is there anything we can do to change this? ... Mostrar más

Is it possible to have multiple register cards (like in the contacts view) and add those cards a saved filter?   Usecase: A salesrep has an assistance, who is also working in the leads at the backoffice. In the current version the assistance has to load all leads and create a filter. And  the assistance should do this every time. ... Mostrar más

User permissions and pipelines access currently act as two seperate layers. A user's deal/ticket permissions will apply to all sales/service pipelines they have access to. It would be great to have a little more flexibility and be able to upgrade/downgrade a users permissions based specific pipelines.   Currently, a user whose deal viewing permissions are set to 'Deals their team owns' will be able to see all their teams' deals in any pipeline they have access to. I'd like to be able to give a user 'Everything' view access to one pipeline while giving them 'Deals their team owns' view access to another. ... Mostrar más

Hi,   Our marketing permission set use to allow our marketing team to create their own simple workflows / automations as a follow-up for emails or form submissions.   Now, simple workflows and complex workflow access seem to be merged. This means our marketing team either: Contact admin to set up simple workflows per email/form Receive access to all workflow capabilities However, we want to minimise the access for the latter to admins only.   Can we separate permissions for simple workflows away from workflows in general?   Kind regards,   Jason ... Mostrar más