Gute Ideen sollten geteilt werden

Hi, I would love to see the ability to mark certain properties as Read only to manage complinace and CRM hyigene.There is a work around with creating a new field and using the "assign to users/teams" feature. Unfortunately this is not available to professional license users. The ability to cordon off certain fields for edit is a requirement at all levels and is not an "enterprise" level usecase :).  ... Mehr anzeigen

Hi, As a security measure businesses need to be able to lockdown who can receive hubspot system emails as well locking down who can recieve previews of any marketing emails. Hubspot users with access to email marketing tools are free to create preview recipients at any email domain. This current list needs to be editable, but ideally this should either be an approved list of emails or email domains. Echoing another ideas post, currently when sending out test emails in marketing tools there is no way to audit who sent or received test emails. Given the need for business to maintain security and confidentiallity around unreleased materials, Hubspot needs to be able to restrict sending of emails to an an approved list of email addresses or email domains. Ideally this would be a allowlist section available in the setting section of Hubspot. Google Ads has a similar mecahnisum for restricting access to the portal. Additionally to this, using the above allowlist would make it far much easier to allow distribution of notifications, such as form submission notices. The current set up requires users to be added to Hubspot, when in fact they only need to be made aware of submissions, but do not need access to the platform. The recent policy update requiring all users is combersome and adds complexity in adding unecessary users to a hubspot portal. https://community.hubspot.com/t5/Releases-and-Updates/Sunset-Adding-non-user-emails-to-form-submissions-email/ba-p/629372 Use of this allowlist could be extended futher to help remove internal/staff, third-party partners and development activities from being included in real stats and reporting. It would provide much greater accuracy. Thanks ... Mehr anzeigen

I want my entire company to be able to see the range of partners or leads we're working with, but I don't want every employee to see every email that's sent and received.  There should be functionality that allows admins to specify which users can see email records.  Hopefully that's enough information - I've seen community posts about this request dating back to 2020. This is potentially a dealbreaker for my team's use of Hubspot in the long term.  ... Mehr anzeigen

A team or channel can have multiple shared inboxes within it. Why can't we direct a chat bot enquiry to one of these inboxes rather than the whole team? ... Mehr anzeigen

While using the sales meeting page links, I discovered functionality that will be undesired as well as present a security issue. I believe this could be an issue for forms in general.   When a form includes a field like "email" which is tied as a unique property to a contact, all associated property fields in the form will be overwritten for a contact if the email they entered exists. This means that if a 3rd party has a list of emails from the database, they could overwrite or erase information in the database.   There should be an option to save or not save certain properties of a form to the database (and non-saved entries get logged as responses somewhere else).   Additionally, a feature where the user has to validate their email with a code sent to them prior to form responses going directly to the database would be appreciated.   ... Mehr anzeigen

Aujourd'hui les autorisations ne sont actuellement pas prises en charge pour les propriétés Soumission de feedback contrairement aux propriétés contacts ou entreprise.   La confidentialité de certains questionnaire nécessite de pouvoir gérer une confidentialité des accès à ces propriétés afin de pouvoir contrôler leur accès à des équipes ou personnes en particulier.     ... Mehr anzeigen

I have different level agents that can handle specific tickets. I can assign certain rules to label the tickets coming in as level 1 or 2 but if I have agents in both level 1 and 2 they will be assigned more tickets than agents in just one level. I would like to be able to set a rule that once an agent hits a certain number of tickets in their backlog then they cannot be assigned new tickets via the round robin. The system would look for the agent with the next available backlog space. This would incur a queue if all agents have reached their max number of tickets in their backlog (open tickets). Once an agent solves a ticket then the queue would assign the next ticket to them automatically.  ... Mehr anzeigen

This feature would be for users with the permission to create permission sets.   The goal is to be able to create session-based permission sets: starting the moment it is created and assigned AND a finish date could be also added: like one week time interval from today.    This way we could be sure that we don´t forget removing user permissions from users who are only visitors or who take part in a campaign only seasonally.   How? When assigning permission set to a user, a box would be there to tick if you want this feature. Also you could set the time interval there if you tick the box.   This feature can be found in Salesforce and is used there frequently.     ... Mehr anzeigen

Emails from HubSpot (with GDPR enabled) include a link to unsubscribe. If you click on the link, you get a web page which asks you to input the email address to be unsubscribed. Here's the thing: the website will allow you to input ANY email address.. and if that address is in our database, the address will be unsubscribed.   I don't understand why HubSpot would make the feature this way, so open to abuse. Why not simply use a unique key from the original email .. so we are pretty sure that the person unsubscribing is indeed the true owner of that email address. ... Mehr anzeigen