Gute Ideen sollten geteilt werden

I am surprised there's no way to mark contacts as test records.   For the purposes of reporting and testing, I expect to be able to exclude test records (for example, team members who have contact records to test emails, forms, workflows etc.). Other use cases could be only sending test records through a workflow, or adding test records to a list for testing purposes.   Salesforce has a simple way of doing this, from memory.    The manual workaround of creating a simple yes/no or tickbox property isn't practical, as we would have to amend every workflow and list setting manually. ... Mehr anzeigen

Currently for Task Permissions, I can set them to be either View/Edit either All, Their Team's or Theirs only.   I would like to be able to grant certain teams within my organization the ability to view/edit tasks from other Teams without having to give them access to ALL tasks.   The specific use case for my company, is that we have three separate Sales teams. I would like these teams to be able to view the tasks from the other teams, while preventing them from seeing my own tasks (my tasks are usually for administrative functions and don't need to be clogging up another user's screen) ... Mehr anzeigen

Hi we are adding new users to our system every month and we are leveraging presets quiet heavily. It's really easy for our IT team to miss giving someone a preset therefore I would like to create a report or even better a workflow based on whether the user has a preset but there is no property which tells us which preset the user has.   Is it possible somehow to get a preset property ?  ... Mehr anzeigen

Would it be possible to automatically populate fields related to a user's team based on a custom user property? HubSpot allows access to the team of the user selected in native properties like hubspot_owner_id, but not for new custom user properties. ... Mehr anzeigen

The new Home page Beta and the new Meetings index page beta got me thinking. What I'd really like my users to have is an index home page. Think "My Index Views" that is a cross-object index page where each tab is, by default, the "my [object records]".    As you can see in this mock up, that would be an index page where the user can quickly tab over and view/filter records for: my contacts my companies my deals my open tickets View and filter records ... Mehr anzeigen

We need to hide some confidential information from groups of persons in the company. We did not find a way to do this. Defining general access rights for all notes, emails, etc. is Ok but we need to make exceptions. I mean we want to define per note or email that this note / email in not visible for a certain group of persons. ... Mehr anzeigen

I uploaded a custom template as a Document to our Library and used our Marketing email as the attribution email to attach a shareable link. The idea is that potential leads will select the link and provide their email address to download it. However, when a person selects the link, it displays my name as the owner. It would be useful to be able to change the owner name to our company and not to me as an individual HubSpot user.   HubSpot support tested this internally and determined that it is not configurable (it retrieves the name from the HubSpot user only). The solution provided would be to share the document without requiring an email to open it, which defeats the original purpose of providing gated material in the first place.    With all the neat personalization touches HubSpot has available, this added customization would be advantageous. Thank you. ... Mehr anzeigen

The goal is to restrict the dropdown options for Owner properties (Contact Owner, Deal Owner, Task Assigned To) based on the connected user’s team—or even better, based on their specific permissions.   Example: If a user belongs to Team X and has permission to edit only tasks and contacts within that team, then when selecting "Assign To" or "Contact Owner," they should only see members of Team X. If a user has permission to edit all contacts and tasks, they should see all users in the dropdown options. Thanks! ... Mehr anzeigen

Feature request: Currently, HubSpot allows deal assignment via round-robin or basic workflow rules, but it does not provide a way to limit the number of deals a user can have per pipeline stage — nor does it offer intelligent fallback assignment when that limit is reached.   Problem: In complex sales operations, each pipeline stage requires different levels of effort. Users should not always handle the same number of deals in all stages. For example: up to 10 deals in Qualification, 20 in Proposal Sent, and 30 in Negotiation. Without this control, a single user can be overloaded in a critical stage, which affects SLAs and overall productivity.   Suggested solution: Allow HubSpot to set deal capacity limits per user and per stage. If a workflow tries to assign a deal to a user who has reached their limit for that stage, HubSpot should automatically reassign the deal to another available user — based on custom logic. It is essential that this fallback assignment is configurable. Users should be able to define: Which team the reassignment can go to (e.g., only SDRs) A custom list of users (e.g., user A, B, and C) Or a defined order of fallback priority   Workarounds we've tried: Manual tracking with custom properties and workflows Using calculated fields to estimate user workload Round-robin workflows without per-stage limits None of these alternatives address the issue in a scalable and automated way.   Expected benefits: Balanced workload across pipeline stages Improved SLA and lead response time Reduced risk of user overload Increased efficiency and fair deal distribution Smarter, more strategic use of workflows ... Mehr anzeigen