Gute Ideen sollten geteilt werden

Custom objects should have granular permissions based on each custom object, instead of the "umbrella" approach today where access is granted across all custom objects ... Mehr anzeigen

It should be possible to give different levels of access to Workflows.   I would like to be able to give my reps access to view workflows, but not edit them. Some reps I would want to give edit access, but not access to run them.   My ideal scenario would be:   READ: - See workflows   WRITE: - Edit non-live workflows   REVIEW: - Edit, review, and run all workflows ... Mehr anzeigen

We have multiple locations with salespeople that have different "lead" days and overlapping schedules. We would love to be able to have more functionality added to Meetings so that we could set the following:   Employee Schedule (for example, Employee 1: Mon-Fri; Employee 2: Tue-Sat) Employee Lead days (for example, Employee 1: Monday, Wednesday, Friday; Employee 2: Tuesday, Thursday, Saturday) We want this all to be utilized in a Team Meeting, and assign meetings round-robin based on the above criteria. ... Mehr anzeigen

Currently it's not possible to lock a user account to prevent them from accessing the HubSpot instance. It's only possible to "Remove from account". The issue with this is if someone leaves the company, and they are the Owner for many records, it takes a while to ensure the right people are updated on those records. If we remove the user account then we lose all the information about what they previously owned to be able to then reassign. However, if we don't remove them, then the user can continue to access HubSpot after they have left.   Firstly, have I missed any existing options that are in place to ensure we continue to see a past employee's ownership of records, for reassigning, without them continuing to have access to HubSpot?   Secondly, if I haven't missed some config, please would you introduce a "lock out of HubSpot" option at user-level.   Many thanks Anne Marie ... Mehr anzeigen

Set unique permission levels on Projects. For the moment, when users have access to the Projects tools, they are able to see all of the projects within the tool.   We need a way to restrict the access levels of users so that they can only access the projects that they own. ... Mehr anzeigen

When i want to know a HubSpot User ID for a spesific user it's getting difficulat to load all users.   I follow "settings>properties>contact owner>search " . It doesn't work majority of times essipecially when a new user joined to HubSpot. The user i search doesn't appear. It would be great if you add HS User ID to users&teams. ... Mehr anzeigen

Hi,   For security reasons I need to find who is deleting contacts in our base. Once is not possible define in users configuration who can or can't delete contacts. The only configuration that exists is if the user can edit or not, and I would like some users could be able to edit, however never delete.   Would be great to have some configuration to don't allow to delete or be able to see who deleted the contact.   Thank you ... Mehr anzeigen

I know that we have the ability to see a rough "Last active" value in the users and teams page per user, and we also have the ability to export login logs for all users as well as security and content activity history: https://knowledge.hubspot.com/account/export-account-activity-history?_ga=2.76327253.1702593517.1597070381-2072000083.1596752279 This is marked as resolved in this other idea: https://community.hubspot.com/t5/HubSpot-Ideas/Track-Account-User-Activity-Tracking/idi-p/2378 However, we still do not have the ability to report on the amount of time that each user spends logged into their HubSpot account per an indicated time period, such as per month. This would be extremely helpful to be able to report on amoun of time that employees spend logged into HubSpot for accountability purposes. Thanks! ... Mehr anzeigen

I'd love to see more granular control over import/export limits at the user and profile level.   As it stands, a person with import and export permissions can import a small amount, or an enormous amount.   The same for exporting. A user could export the list of people that got a specific email, or they could export the entire contact database.   It'd be great to have row limiting at a minimum at the user and/or profile level.  ... Mehr anzeigen