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

For example: I want to give someone access to creating a new Chatflow, however, to do so, they would have access over Deal Pipeline configuration and setting up the property views for all record types.   There are already some on/off switches under Accounts Access, e.g. for user permissions, please could there be a full breakdown of all the areas that Accounts Access gives access to so that more control can be given. ...その他を表示

At the moment the access controls are quite limited, and entirely on the user side, rather than the content side. The only controls are whether a user can see their contacts, their team's contacts, or all contacts.   Sometimes you want a contact/company/deal to only be visible to certain people (e.g. their owner), and currently there is no way of doing that. You can utilise teams to make it so that all contacts assigned to a person or team are only visible to that person or team, but there is no way for this to be set on a per contact basis.   This feature would make it much easier to control access and improve security and compliance. When combined with email logging, it will also help avoid people seeing emails that they shouldn't. ...その他を表示

There needs to be more granular ways to grant account rights to specific users, for example, when providing 'export' rights to support staff in order to enable them to export service hub reports, we're forced to grant them the ability to export everything within Hubspot. It's tricky to give entry-level support staff the ability to export key data like deals or customers info, they should only be given access to Service Hub data and not Sales or Marketing. ...その他を表示

Currently, a user can be a 'primary' member of only one team. The user can be added to other teams as an 'additional team member', but many team features are unavailable to these 'additional' users (see list of restrictions below).   This is problematic and causing us considerable pain because some users need full access to multiple teams, e.g. an individual who is multi-role, or management/supervisory staff who need to monitor what goes on in the team. This is particularly true in smaller businesses. The one primary team restriction seems unjustifiable .   Restriction's on 'additional team members': https://knowledge.hubspot.com/account/assign-users-additional-teams These users will not be included in any team reports, routing rules (e.g., conversation routing rules), team notifications (e.g., form submission email notifications to a team), or workflow rotation actions. They will also not be able to view any custom records views set up for the team.   The solution is to allow users to be primary members of multiple teams.   Any feedback? ...その他を表示

Hello!   I would like to suggest a new feature called Private Properties. With HubSpot Enterprise we can limit permissions for editing some properties based on team/user, but we can't limit who has access to view it! In my company, we want to have a sensitive property to store the user login link (that will be used to send transactional emails). My Support team need to have access to all contacts and deals, even if they aren't owners, but we can't have this property available for them to see or search when they click at "View all properties" (limit the record sidebar isn't enough). Would be great if we could limit some properties to team/user view only (not only editing, but just view), regardless of being a record owner or not. ...その他を表示

As a Super Admin, I receive email notifications every time a user initiates a large data export from our HubSpot account. It would be perfect to have functionality allowing to immediately block the export in case it looks unfamiliar and we can't reach the user who initiated the data export straight away (considering the number of users we have). The best way would be having a "block export" button embedded directly in the email.    This would allow us to have an extra layer of security of our account & be more proactive.  ...その他を表示

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 ...その他を表示

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 ...その他を表示

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. ...その他を表示