Les grands esprits se rencontrent

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 would like to create a firm Calander that everyone at the firm has acess to. When there is a new meeting or event created, then that said meeting or event would also directly link to the asscoiated contact/company. It would also need to be a calendar that everyone at the firm has acess to, not only one person.  ... Afficher plus

This idea is for any company that manages multiple teams or business units within a single portal. Currently, assigning a team to a page only restricts editing rights, not viewing rights. This means all users can see all pages in the portal, even those not relevant to their team. For instance, a user on "Marketing Team A" can see every page created by "Sales Team B," which clutters their workspace. We propose a new permission to restrict page visibility based on team assignment. This would allow an admin to configure the portal so that users can only see pages assigned to their specific team. Key Benefits: Clean Workspace: Prevents a cluttered page list for users. Increased Efficiency: Teams can find their content faster without sorting through irrelevant pages. Better Scalability: Essential for large organizations managing multiple teams in one portal. Granular Control: Gives admins true control over who sees what, not just who edits what. This feature would be invaluable for any company focused on organization and scalability. We hope other users agree and will upvote this idea. Thanks! ... Afficher plus

We've noticed that when creating different custom Deal Record Views, while it allows you to assign the views to Team(s), it only applies to members for which that is their Main Team, not Extra Team. The issue with this is that I have a user who is a member of our "Master" team, and has "DPA" set as the extra team. We wanted them to have the general "Master" deal record view for most of our pieplines, but for one pipeline, the DPA pipeline, a view with different fields and Cards assigned to the "DPA" Team . But because his Main Team is "Master", they are viweing the exact same properties set for the Master Team, eventhough he is also a memeber of DPA. It would be great to have an option to assign Record Views not only to different teams, but also in general by Pipeline, since we don't always want the same Fields to be shown for different types of Pipelines. ... Afficher plus

Hi All,    For those of you who are not aware, HubSpot will be moving all existing customers to seats-based pricing in September if you were working with a partner. If you bought direct you might have already been migrated.   While for the most part there is no feature loss, a number of our customers are very concerned with this transition as they will be losing a feature that has been very important for their Management teams and Operations teams.   People who are transitioned to View Only or Core Seats will no longer be able to view deal and ticket tags.   This might affect customers who rely on their management or operations teams to see deal/ticket status without needing to manage them directly as is the case with a number of our customers.   Ideally, our customers would really appreciate it if deal tags and ticket tags could be visible for View Only and Core Seats as this feature adds a lot of value to customers who are not in a sales or support roles but not enough value to justify purchasing sales or service seats for these users.   Regards, Bryan ... Afficher plus

Currently, HubSpot allows us to create permission sets and assign them to individual users. However, as organizations grow, managing permissions for each user becomes time-consuming and prone to errors. I propose implementing team-based permission sets to streamline this process.   Key Benefits: Time-saving: Admins can set permissions once for an entire team rather than individually. Consistency: Ensures all team members have the appropriate access levels. Scalability: Easily onboard new team members with pre-set permissions. Flexibility: Allows for quick adjustments to team-wide permissions as roles evolve. Proposed Functionality: Create permission sets at the team level Automatically apply team permission sets to new team members Option to override team permissions for specific individuals if needed Ability to view and manage permissions at both team and individual levels This feature would significantly enhance HubSpot's user management capabilities, especially for larger organizations with multiple teams and frequent onboarding.   I believe this addition would greatly improve efficiency and security in permission management across the platform. ... 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

Currently HubSpot limits user session timeout length to a max of 1 day.   As a user: I may take a single day off or find myself not utilizing the HubSpot interface for a day, resulting in the requirement to login again. As an admin: I am not in HubSpot every day, but I might be in it 2-3 times a week, each of them requiring me to log in again. As an SSO/SCIM admin: I am annoyed that HubSpot's limited options block me from properly managing security in a way that best suits my organization. Earlier this year HubSpot did not provide control over this and sessions were indefinite. Now it seems the pendulum has swung to anothe extreme. (e.g. it is difficult to imagine anyone wanting 15 minute session inactivity timeouts)   Please give admins the ability to set a more reasonable session timeout length! ... Afficher plus

Currently, a user can be a 'primary' member of only one team. The user can be added to other teams as an 'additional team member', but many team features are unavailable to these 'additional' users (see list of restrictions below).   This is problematic and causing us considerable pain because some users need full access to multiple teams, e.g. an individual who is multi-role, or management/supervisory staff who need to monitor what goes on in the team. This is particularly true in smaller businesses. The one primary team restriction seems unjustifiable .   Restriction's on 'additional team members': https://knowledge.hubspot.com/account/assign-users-additional-teams These users will not be included in any team reports, routing rules (e.g., conversation routing rules), team notifications (e.g., form submission email notifications to a team), or workflow rotation actions. They will also not be able to view any custom records views set up for the team.   The solution is to allow users to be primary members of multiple teams.   Any feedback? ... Afficher plus