Totally agree. There is definitely a need for this as our sales, and various support teams should be restricted to view only their projects they are working on. Just like the inboxes, contacts and companies, tickets should have the ability to limit what users have access to view/edit these -WITHOUT the necessity to ASSIGN all tickets.
Hi there,
this would represent a clear improvement in our privacy model.
It could be great that each team has the access ONLY to their pipelines, instead of being able to check the other’s pipelines, even if they can’t see the deals.
Thanks!
We love pipelines. They would be an even better tool if we could give specfic users the ability to see different pipelines, on a pipeline to pipeline basis.
An example: We have one pipeline in Service Hub for our Tech Support. We have another pipeline for our GDPR requests. We have a third pipeline that helps us track feedback/complaints for ISO. Some users shouldn’t have access to all three pipelines when their main responsibility is tech support.
Thanks!
Absolutely need this.
I would like to limit permission to some agent. Hope this subjet solve soon.
Thanks
We also need this feature. There must be the possibility that multiple users can edit a pipeline. Please do that for us.
I completly support adding this functionality. We had this functionality when we used Salesfore and it’s missing from hubspot. Pipelines and deals should be defined by sales user groups so two different vertical sales teams are not able to access and see deals of other teams if determined by sales opps.
This was a great idea when it was first posted in 2017. Having this feature is essential when dealing with multiple teams.
I have the same requirement as above. I need to segregate access to pipelines ideally for specific compliance requirements and geographic sales territories.
We need this desperately…we are considering leaving because of that.
100% agree - a number of our partners need to have permissioned views on pipelines. Ideally through filtering properties - but worst case selected views on Pipelines. Surely something on the roadmap as data handling regulations keep updating?
This is something we also definitely need to implement for our charity organisation!
+1
We need this as well
We would love to have this! It’s a must-have.
We want the ability to assign specific teams to pipelines and only show the corresponding views when creating tickets so there are no chances of the agent choosing the wrong pipeline. We only want the agent to see the information for their team, hide all other pipelines and properties from their view.
We are using 2 pipelines for our Service board today: Support, and Service Delivery.
This would be very useful in my B2B company
It could be great that each team has the access ONLY to their pipelines, instead of being able to check the other’s pipelines, even if they can’t see the deals.
We are a law firm, experts on data protection, and we love Hubspot. Adding the possibility to customize pipeline access would add a great deal to GDPR compliance of Hubspot. Hopefully, it shall be put to the production roadmap soon.
Agreed. This is needed for privacy. Even blocking stage names for some users.
I believe having permissions for pipelines in ServiceHub would be helpful too. We are dealing with a lot of different processes and some information is not relevant to front end teams using the sales/deals/contacts features. If would be great to have permissions based on pipelines to keep some of this information available to the teams that need to see that ticket information.
Hey,
Thank you for submitting the idea. Im a PM at HubSpot and the idea you submitted is aligned with a plan the team is currently working on.
As I understand your request: you need to be able to give your sales team access to their sales pipelines while restricting their access to the claims pipelines. Is this correct? Do you have a need to allow the claims team to see the sales pipelines but not edit them? The product team is seeking to validate how common is the use case of granting one user/team edit access in pipeline A, for exampe, while granting view only access in pipeline B.