TL;DR: can I use/view/see company properties in a Deal Pipeline?
I'm building up a cross-/upsell pipeline for my company.
Let's say we have 3 business units (BU): AWS, Salesforce, Cisco.
When a BU closes a deal, that is defined as the Company | Primary Practice, (1 BU selection only) by a workflow. Now, we want to define Target Practices; could be either or both of the other BU practices.
In the new pipeline, we imported potential upsell / cross-sell data from a spreadsheet. The deals have a property, Type of Business (Cross-sell) assigned, plus Company name, contacts, etc.
Where I'm stuck:
The view in the pipeline is fine - the Deal Name shows Company Name | Practice, but I want to be able to see the Active Practice and Target Practice(s) to filter and sort.
Example: a new deal might be Lenovo (Company) AWS (Practice). I want to see that Lenovo is a Cisco practice too.
Yes definitely, because there aren't relational fields it's important to design each object correctly based on what you need to see on each object. Also, you can limit which fields can be seen by each user or team using this feature: https://knowledge.hubspot.com/account/restrict-view-edit-access-for-properties
Currently you can't see related object fields on the deal pipeline, you will only be able to see/filter by deal fields.
However, if you are automatically creating the deal through a workflow you can copy the company property to the deal when creating the deal. You would have the same property on the company and the deal, and then use the "Copy a property to a deal property" when creating the deal through the workflow.
If the information is being changed on the company, and you need to see this in real-time on the deal pipeline - you could run a workflow to automatically update the deal when the company property changes.
This is more of a thought exercise question: if Hubspot has compartmentalized data from Deals / Companies etc., it seems like data mapping / design for all this is critical, right? Thinking forward about who and what needs to see and have access to which information?
Yes definitely, because there aren't relational fields it's important to design each object correctly based on what you need to see on each object. Also, you can limit which fields can be seen by each user or team using this feature: https://knowledge.hubspot.com/account/restrict-view-edit-access-for-properties