Les grands esprits se rencontrent

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? ... Afficher plus

We're locking down our internal communications and it would be great if there was a way to lock down the specific "from address" users can send from.   So being able to designate which "from" addresses users are able to send from. ... Afficher plus

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. ... Afficher plus

Currently all users with even the lowest level permission can access all the connected apps under integration. This is very bad since some connected apps carry many leads that are not supposed to be available to users. (Such as Mailchimp app) If we can add a permission settings for users to not have viewing permission to connected apps that would be awesome. ... Afficher plus

Hi there,    As the HubSpot admin within the company, I am interested in receiving notifications regarding any errors related to users' connected accounts, such as email or calendar disconnections, calendar sync errors, and so forth which I believe this feature has the potential to streamline our administrative operations.   Thank you! ... Afficher plus

When exporting the list of users from your settings ("user table"), there are several properties that are available as filters, but are not included in the exported file.   Specifically, I would like to request that the "Invite Status" user property be included in the user export file.   We are a large organization with many HubSpot users, and therefore automate our user provisioning. Due to variable onboarding schedules, we often have many users at once who are in the "invite pending" status. This becomes a problem, of course, when a user is in a pending status for more than a few weeks.   As part of our adoption metrics, we look to determine the percentage of weekly/monthly/etc. active users. Since the user analytics tools cannot do this in the UI (yet!), we export the user list and report via Excel.    There are two key problems with the export function, as it doesn't behave in the way a list or index page export does:   1. All records will be exported, even if you have filters applied. For example, when you export a filtered index page, you can export just those records in your filtered view. So if I apply a filter to only show users with an "Invite Status = pending," that will not be reflected in the export. This is problematic for us because it will falsely inflate our total number of users when I'd like to only report on accepted users.   2. There is a lack of consistency between the properties shown in the UI filters and the properties being exported. The following properties are not included in the exported file:   Invite status (ironically, this is the very first filter listed on the page, and yet it's not included in the export) Access (this is included, but in the export it's called "Permissions") Calendar status Calendar sync Email status Extra teams (this is included, but in the export it's called "Additional teams") Main team (this is included, but in the export it's called "Primary team") Partner Scheduling pages Seat (the export does include a "Paid seat" property, but it does not specify which paid seat the user holds - it simply says "yes/no")   Additionally, when you generate an export, the shown properties are the same each time (and not comprehensive). It should beave similar to an index page or list export where you're asked if you'd like to include all properties or just those in your current view.   While gaining export acess to the "invite status" property is my primary objective here, I imagine it is quite frustrating for other customers to not have access to properties like "Scheduling pages" or "Seat" in their exports as well.   Please update the user table to behave more like an object index page, and more specifically, update the file export to align with the properties shown in the UI filters.       ... Afficher plus

The new beta update for Business Units is great, because you can now select from Navigation which Business Unit you are working on when in your portal. However, it gives access to all users.   There should be a way to filter or manage who can see the Business Units depending on the team or unit they actually work on: ... Afficher plus

We have multiple business units in our account, but our marketing team for example works for all business units.      We would like to be able to set users standard to 'all business units': Currently this is only cookie based.  On a new device it opens up the main account again. Side note:  Before you could just handle this in a view, why this has been removed is a mystery to me and I honestly would also like to see that option back too. ... Afficher plus

One common challenge faced across business units and teams is the limitation of having only one default value for properties in HubSpot.   Essential properties such as names and [object] owners are shared among various teams within an organization. However, assigning a single default value for these properties poses significant constraints and inefficiencies.   HubSpot Enterprise Account with Business Units still has only one Default value for properties used across teams   Our current workaround: Currently, teams often resort to reaching a consensus on generic default values for shared properties. While this works in some cases, it becomes problematic when teams have divergent needs.   For instance, the "Contact Owner" property might require different default values for different business units. This forces teams to create custom properties for each unit, duplicating efforts and complicating data management. To address this challenge, I propose expanding HubSpot's property management capabilities to allow for customizable default values on a per-business-unit and -team basis. This improvement would empower teams to tailor default property values according to their unique requirements without resorting to creating redundant custom properties. ... Afficher plus