クリエイティブな才能を開花させよう

When a user's permissions are set to private (own only) this should apply across the board (marketing emails, segments, dashboards). It's unrealistic to expect a user to manually go back in and set everything to private everytime they create something new.    The same applies to team only permissions. Why can't the default visability features tie in with the permission set? ...その他を表示

(Posting on behalf of a customer)   We request the feature to restrict the manual sending of WhatsApp messages based on the value under a property X.    Use Case:    Our Sales team has a strict process for using WhatsApp. They are only allowed to contact a prospect via WhatsApp once the associated Deal has reached the "Qualified" stage.   Currently, manual sending is available on the Contact/Deal record without any property-based restriction. This creates a risk of sales reps prematurely sending messages to contacts who have not yet passed the necessary qualification stages, which can negatively impact the prospect's experience and the credibility of our process.   Proposed Implementation:   Add permitions to record activities or send messages, mails, etc. based on record properties. For example, if property "stage" is "client", action to send emails and WhatsApp messages is available. If not, activity is greyed out.    Thanks! ...その他を表示

I am a CSM who has a customer that wants to manage their Helpdesk team by creating specific standardized views that an Admin can create (manager of a team) in which support team members are not able to edit or change these views.  ...その他を表示

To be able to search "marketing" in permissions and be able to see the information under the "marketing tab". Instead we have to click on the tab Marketing, to see all the information that's under Marketing. It would make it more clear for customers.  ...その他を表示

Super Admins need to have the ability to add, modify, and delete users' personal email signatures. Now personal email signatures are only available through the individual user's login. It would make sense for some companies to have that managed from a super admin's view, so individual users don't have to manage. To me it makes sense under the User's section of the super admin's view. And these would be individual html email signatures, not global where everyone has the same signature. ...その他を表示

If you are a sales admin or you're a marketer you will get asked to build out a sequence for the sales team.   Currently, you would have to purchase an additional sales seat to make that happen.  The idea is that with a core seat you should be able to view, create, and edit sequences but not enroll contacts.  Imagine how frustrating it is to wait for the sales team to write a sequence that needs to be included in your marketing studio campaign. It's not a big leap to make this change because it's already possible for a core seat user to enroll and unenroll contacts in sequences via Workflows (for Sales Ent accounts).  Let's make it possible to create and edit sequences too. ...その他を表示

The "Create and associate Companies with Contacts" setting is great in a lot of situations, but it can be risky in other portal configurations. Currently, anyone can enable and disable this, even with an accidental single click, and little warning about what they just did. We simply need the ability to limit who can control this setting, ideally limited to only Super Admin or as a more granular account-level setting. ...その他を表示

Currently, there is no way to restrict whether or not users can mention other users in a note/comment. If they have note permissions, then they have the ability to mention other users in the note/comment by default. It would be great if HubSpot added a separate permission just to manage a user's mention capabilities! ...その他を表示

Problem Today in HubSpot, it’s not possible to fully hide a property. You can set field-level security to “private to super admins only”, but this only hides the field content — the property label (name) is still visible to end users. As a result, users often see property names that are irrelevant to them, which clutters their interface. This problem grows when multiple teams are using HubSpot across different pipelines. Proposed Solution Allow super admins to completely hide a property from end users, either globally or at the team level. This would provide: The ability for admins to create private properties and still use them for reporting in the background. The possibility to hide a property before archiving it. If it’s forgotten, end users will naturally flag it, and field-level security can be reopened if needed. Cleaner views for sales reps: today, when they build lists or views, they see countless variables that don’t apply to them. With multiple teams working on different pipelines (each with its own set of properties for deals and companies), being able to display only the properties relevant to their team would bring real clarity and efficiency. Impact Less clutter for end users Better adoption of properties that actually matter Easier management of multi-team setups and pipelines More intuitive experience for sales and service teams ...その他を表示