Las grandes mentes piensan igual

To ensure that our portals follow data protection best practices, we would like to be able to make a user inactive and essentially revoke access after x number of days. So if a user hasn't logged in for 90 days then their access should become inactive and require an admin reset. This would assist us in managing user access and protect our data. This allows team members who shifted role or left the business to have their access expire in case they were not removed and seems to be good practice on secure platforms. ... Mostrar más

I have a use case where the sales manager is handling replies while his team members are on holiday. So we are force to give him Super Admin rights so he can log in. But then he has Super Admin rights which is a problem. I think there is value in allowing users apart from super admin to be able to log in as their team member.   ... Mostrar más

Background: Objects are owned by/assigned to users.   Permissions are set at the user level and restrict access to objects (contacts, deals, tickets). Available permissions: Everything Team only (user can see all objects it owns AND objects owned by other users in the user's teams) Owned only None The problem: The 'team only' permission is flawed when a user is a member of 2 (or more) teams This is because members of the 2 teams can see all objects assigned to the user. This is problematic because some objects owned by the user should be visible to 1 team only Pracitcal example: An EU-based user is a memebr of 2 teams Team 1: consists solely of EU-based users who process tickets for EU clients (data protection laws & client contracts mean EU client data can only be accessed by EU-based users) Team 2: consists of both EU-based and non-EU-based users who process tickets for non-EU clients (there's no restriction on EU-based users accessing non-EU client data, meaning the EU-based user can be a member of Team 1 and Team 2) The 'team only' permission fails because any object assigned to the EU-based user is visible to all users in Team 1 (EU) and Team 2 (non-EU). This means non-EU used see EU-onlu data, so breaches data law & contractual commitments   The solution: The solution is to allow objects to be owned by teams. The 'Team only' permission would need to look at which team an object is assigned to and grant access to users who belong to that team.   It would still be possible for a user to own an object, as this is useful in other scenarios. However, it would not be possible for an object to be owned by a user and a team simultaneously, they would be mutually exclusive. ... Mostrar más

I would suggest that the pixels somehow be linked to the original email address(s) they where sent to and need to be filtered hubspot server and our preference settings as to what gets pushed out to our phones or PC apps and if its a bot doing a virus scan opening or just someone that has left my mail at the top of their inbox and it get opened each time they look at email I only want to see 1 notification every hour ... Mostrar más

Bulk edit team permissions ... Mostrar más

Hi!  I am looking at setting up user access based on few properties. For eg - If I have product as a deal property, all deals with product value as "PD1" needs to be viewed only by managers of "PD1" and so on.  Although deal owner property helps us set this up, there are multiple scenarios where we want users from teams other than the deal owner, to view and access certain objects.   ... Mostrar más

When this setting is turned on, three workflows are created to automate this approval process. Further, turning off the setting will delete the WFs. This does not let HubSpot administrators to customize the WF unless the setting is on.    Huge limitation in that every use case may be vastly different and this timing does not allow for adequate planning/documentation/execution.    ... Mostrar más

Hi, It would be interesting to be able to restrict access to the "goals" page, accessible via "parameter" and then "reports". From the user rights management page for example. This would prevent everyone from being able to consult each seller's revenue targets. These objectives are often confidential. Do you think this could be possible? Thank you in advance. Best regards. Yoann ... Mostrar más

Hi there,   We recently configured SCIM with Okta for our organization. Previously we had roles & rights assigned manually, including 3 of our Super Admins that also had a Sales Enterprise seat. In configuring SCIM, I assigned each of our Super Admins the corresponding role 'Super Admin'. However, once the provisioning was activated, they lost access to their sales enterprise seat. According to support, there is currently no way for a user to have both the super admin role assigned in Hubspot, as well as access to a paid sales enterprise seat, when SCIM is activated. Therefore my request is:   - Please create a super admin role that includes a sales enterprise seat or allow super admins to toggle the sales enterprise seat on or off for the role ... Mostrar más