Les grands esprits se rencontrent

Be able to manage permission based on a specific field and not only by team/permissions.   Example:   As-is: Managers who are multi teams and owner of records give visibility of their records to the teams they belong To-be: by managing visibility & permission with a field, we could solve issue. ... Afficher plus

The left-hand sidebar is cluttered with many elements that we do not use. Users are finding this confusing and frustrating. Some can be removed by denying permission to those features, but only a very limited subset have permission controls. This barely makes a dent in the clutter.   I should be able to completely customize what options are available to make the experience very simple.   ... Afficher plus

The issue I am seeing is that unless a user has the permission to Add and Edit Users in the Account permissions, they cannot edit their own Away and Available hours manually. I have been looking in a bunch of other places they can adjust but our Reps cannot change their status manually and require either access to the Availability Management permission (which enables every user to change all the user statuses) or Add and Edit User (which is a very sensitive permission as they could change roles and such).   Giving the ability for the user to change their own status seems like an easy win for managing their availablity in Working Hours. ... Afficher plus

When creating a new team in HubSpot, the team currently has no access to any properties that use the “Assigned to users and teams” permission. Currently, the only options are: Updating each property manually, or Performing a bulk update, which overwrites existing permission settings. Since there are no filtering options for access, it’s also difficult to select the correct properties together. With hundreds of such properties—necessary due to shared HubSpot usage across departments with different access needs—manually updating each one is not feasible. I would therefore suggest adding an option to “copy access” from an existing team when creating a new team. This would automatically grant the new team the same access level on all properties with “Assigned to users and teams” permissions as the selected team, streamlining setup and reducing the risk of errors. ... Afficher plus

Submitting on behalf of a client, it would be very helpful to be able to customize the User Availability status options within Availability Management settings.    They are currently using HubSpot <> Aircall for their Support team, and in Aircall they can customize and set the reasons they're away (out to lunch, training, on a break) but HubSpot has much more limited options (Away, Available) so they cannot see or report on reasons their team is away for other channels such as email or chat support. Having customizable availability would allow for granular reporting and other helpful insight for management  ... Afficher plus

Currently, it is not possible to create and test users along with the permissions, permission sets and seats assigned to them in a sandbox portal and then sync these to the production portal. The new feature from https://knowledge.hubspot.com/account-management/deploy-sandbox-changes-to-production allows this for assets but not for users.   Suggestion: allow syncing users and their set up from sandbox to production portals ... Afficher plus

Hi everyone, I’m seeing an issue where required properties + conditional field visibility prevent users from other teams from updating our main brand property. We use conditional fields that appear when a specific brand is selected. Some of these dependent fields are marked as required and only editable by the team that owns that brand. What happens: Users cannot select a brand if its dependent required fields belong to another team (they don’t have permission to edit them). Users also cannot change the brand away from that value if the required fields were never filled in — changing the brand re-triggers the requirement. Inline edits bypass required fields, but this is not a reliable solution. As a result, the brand property becomes effectively locked for users outside the brand’s team. My question: Is this expected behaviour, or a limitation in how required properties interact with permissions and conditional fields? And is there a recommended best practice or future improvement for this scenario? Thanks! ... Afficher plus

Hi HubSpot Community,   We operate a large, global support organization with teams spread across multiple countries. Our structure relies heavily on nested teams, which has always been one of HubSpot’s strongest features for enterprise-level operations. It allows us to segment responsibilities, manage permissions, and route work with clarity while keeping everything unified in one CRM.   As we’ve adopted the Help Desk, nested teams continue to be important for maintaining clean ownership and reporting. The challenge we have run into is with default reply-from settings at the team level. Now that our Help Desk is fully configured with teams assigned to different spaces, we’ve discovered that we cannot set a default “Send From” email for any team that is nested. Because of this limitation, our agents must manually choose the correct reply-from address for every single email they send. We manage hundreds of conversations per day. This manual step slows down response time and increases the risk of sending from an incorrect address. We have identified a workaround. We temporarily unnest the teams, add them to the appropriate Help Desk spaces to establish a default “Send From” address, and then re-nest the teams afterward. While this does technically work, it is fragile and unnatural. It also does not scale well for organizations with large, complex team structures.   Given how central nested teams are for enterprise users, being able to set default reply-from emails for them in the Help Desk feels like a core need rather than an edge case. It would improve efficiency, reduce manual errors, and align Help Desk functionality with the way HubSpot already supports teams throughout the platform.   We would greatly appreciate consideration for enabling default “Send From” settings at the nested team level. This would remove the workaround and significantly improve usability for global support organizations like ours.   Thank you for your time, and happy to provide more insight into our configuration if helpful. ... Afficher plus

The user permissions setup experience is always doing inexplicable things that I have to find creative workarounds for, because it just doesn't work properly.   With the Partner Admin seat + permission set, there's no reason why I should be restricted from editing most other users' permissions in HubSpot, but I'm constantly running into obstacles.   This has been happening for months across many different client accounts and in different scenarios, but these are just some examples that I ran into today.    1. When setting up a custom permission set and attempting to start with a template, ALL of the user permissions templates are greyed out and they say "You don't have the required permissions to apply this template" (see screenshot)- I am a Partner Admin so I absolutely do have the required permissions.    2. Under Commerce in the permissions, it doesn't allow me to turn on the permission to give people approval access on Quotes and says that I must be authorized. As far as I know this isn't an Account Access related setting, and so there's no reason that I know why I wouldn't be authorized to set up Quote Approval permissions for other users.    3. I created a custom view-only permission set that gives them access to view only CRM records owned by their team, whereas the default "seat permissions" for view only users is actually to only view records owned by themselves. I'm getting an error message in the user creation interface that I can't apply any permission sets to these view-only users. Going through the permission set in great detail, there's not a single setting in there that would require a Core seat over a View Only seat, but it doesn't allow me to apply the permission set.    I think we can do a lot better with the overall functionality of the users setup!  ... Afficher plus