Linked deal logic and user visibility constraints define how activities attach to deals in Pipedrive, according to Pipedrive.
Activities link to deals through specific relationship types
An activity linked to only a deal is automatically linked to the contact person and organization linked to that deal, according to Pipedrive. This automatic linking behavior applies specifically when the activity is connected to a deal without other direct associations. The system extends the relationship from the deal to its associated contact and organization records.
To see an activity, a user must have visibility into all items linked to it, according to Pipedrive. This visibility requirement means that access to the activity depends on the user's permissions for every connected record. If a user lacks visibility into any linked item, the activity itself remains hidden from that user's view.
These two rules work together to determine both the structural connections and the access permissions for activities in the pipeline. The automatic linking creates the relationship structure, while the visibility rule controls who can see the resulting activity. Revenue leaders should verify that their team members have appropriate access rights to all linked records to ensure accurate pipeline visibility. Check your current pipeline to identify activities that are linked to deals but missing from the associated contact or organization timelines.
Key takeaways for how to link activities to deals in crm
Pipedrive automatically links an activity to the contact and organization when it is linked only to a deal, according to Pipedrive. Users must have visibility into all items linked to an activity to see it, according to Pipedrive. HubSpot stores activity properties separately from CRM object properties, excluding calls, meetings, and tasks (BETA), according to HubSpot. HubSpot tracks the first level of detail on how an activity was created as Record Source Detail 1, according to HubSpot. Microsoft defines collection-valued navigation properties as representing one-to-many or many-to-many relationships between entities, according to Microsoft. Microsoft records the date and time when an activity was created, according to Microsoft.
A filled reference table of activity linking rules by publisher
The table below maps the eight specific rules governing activity linkage, visibility, and storage to their respective publishers.
| Publisher | Rule Type | Specific Behavior or Definition |
|---|---|---|
| Pipedrive | Linking logic | An activity linked to only a deal is automatically linked to the contact person and organization linked to that deal, according to Pipedrive. |
| Pipedrive | Visibility rule | To see an activity, a user must have visibility into all items linked to it, according to Pipedrive. |
| HubSpot | Creation path | Record Source Detail 1 defines the first level of detail on how the activity was created, according to HubSpot. |
| HubSpot | Record Source Detail 2 | Record Source Detail 2 describes the second level of detail on how the activity was created, according to HubSpot. |
| HubSpot | Property storage | Activity properties, excluding calls, meetings, and tasks (BETA), are stored separately from CRM object properties, according to HubSpot. |
| HubSpot | Property editing | These properties cannot be edited from the property settings, according to HubSpot. |
| Microsoft | Relationship type | Collection-valued navigation properties represent collections of entities which may represent either a one-to-many (1:N) or many-to-many (N:N) relationship, according to Microsoft. |
| Microsoft | Creation timestamp | The field records the date and time when the activity was created, according to Microsoft. |
Verify that your pipeline data aligns with the specific storage and linking behaviors of each tool.
How Pipedrive handles automatic deal and contact linking
Pipedrive defines the creation path for activities within the contacts timeline. To start the process, a user clicks the “+” icon and selects Add activity on the right side of the screen when hovering over a contact’s timeline, according to Pipedrive. This specific interaction initiates the activity scheduling window. Within this window, the user can select the owner and link the activity to a deal, organization or person, according to Pipedrive. The platform provides distinct logic for each relationship type. When an activity is linked to an organization, it isn’t automatically linked to its deals or people contacts, according to Pipedrive. The reason provided is that there can be multiple deals and people contacts linked to each organization, according to Pipedrive. This prevents unintended visibility across unrelated records.
For leads, the creation path differs from the contact timeline. A user opens a lead from the Leads Inbox and clicks on the “Activity” tab at the top to create and link an activity to it, according to Pipedrive. This direct link ensures the activity attaches to the specific lead record. The distinction between linking to a deal, organization, or person determines where the activity appears. Linking to a deal attaches it to that specific opportunity. Selecting a person as the link target connects the activity to that person record. Selecting an organization as the link target connects the activity to that organization record without automatically linking it to the organization's deals or people contacts.
Revenue leaders should verify the link target before saving an activity. If the goal is to track a specific negotiation step, link the activity to the deal. If the goal is to track a general company update, link it to the organization. If the goal is to track a personal follow-up, link it to the person. Checking the link target prevents activities from appearing in the wrong timeline. This manual verification step ensures accurate pipeline visibility. The platform does not automatically cascade organization-level activities to deals, so explicit linking is required for deal-specific tracking.
HubSpot activity properties and storage separation
HubSpot's default activity properties track the origin of an activity through three distinct levels of source detail. The first level, Record Source Detail 1, defines the initial layer of information regarding how the activity was created, according to HubSpot. The second level, Record Source Detail 2, provides the second layer of detail on the creation method, according to HubSpot. The third level, Record Source Detail 3, offers the third layer of detail on how the activity was generated, according to HubSpot. These three levels allow revenue leaders to trace the specific path an activity took to enter the system.
Storage for these properties operates under a specific separation rule. Activity properties, excluding calls, meetings, and tasks (BETA), are stored separately from CRM object properties and cannot be edited from the property settings, according to HubSpot. This separation means that the data structure for activities is distinct from the data structure used for standard CRM objects like contacts or companies. The exclusion of calls, meetings, and tasks (BETA) from this specific storage note indicates that these particular activity types may follow different storage or editing protocols, or that the note applies strictly to the remaining activity types.
When users create or edit calls, emails, meetings, notes, and tasks manually or through import, they can set or update properties, according to HubSpot. This capability allows for direct manipulation of the activity data during the creation or editing process. Users can make these property changes while creating or editing activities, whether manually or through import.
The values stored in these properties serve a functional purpose beyond simple record-keeping. You can use values of these properties when filtering records in other HubSpot tools such as segments, reports, or workflows, according to HubSpot. This filtering capability allows revenue leaders to isolate specific activities based on their source detail levels. For example, activity property values can serve as filters for records in reports, helping users narrow the records they review. The integration of these property values into segments, reports, and workflows ensures that the source detail data is actionable within the broader HubSpot ecosystem.
Microsoft relationship definitions and creation timestamps
In the phonecall EntityType (Microsoft.Dynamics.CRM) documentation, Microsoft defines collection-valued navigation properties as representing collections of entities which may represent either a one-to-many (1:N) or many-to-many (N:N) relationship between the entities, according to Microsoft. This definition clarifies the structural link between the activity record and other entities within the system. The relationship type determines how the data connects across different object types. Understanding this distinction is critical for interpreting how activities attach to broader pipeline records.
Microsoft also specifies a creation timestamp field for the activity, defined as the date and time when the activity was created, according to Microsoft. This field records the specific moment the activity entry was generated in the system. The timestamp serves as a fixed point in time for the activity’s origin. Revenue leaders can use this timestamp to verify the sequence of actions taken on a deal. Comparing this creation time against other deal events helps establish a chronological history of engagement.
The combination of relationship definitions and creation timestamps provides the foundational data structure for activity tracking. Collection-valued navigation properties describe collections of entities in one-to-many (1:N) or many-to-many (N:N) relationships. The creation timestamp records the date and time when the activity was created. When auditing pipeline data, check that the creation timestamp aligns with the expected workflow for the activity type. Verify that the relationship type matches the intended connection between the activity and the deal. Ensure that the collection-valued navigation properties are populated correctly to reflect the actual business interaction. These checks help maintain accurate pipeline visibility and support reliable forecast calculations.
For further context on how deal attributes interact with pipeline stages, consider reviewing Open, won, and lost stage rules in 4 sales tools.
Visibility rules and user access constraints
User access rights directly control whether an activity appears in a user's view. According to Pipedrive, to see an activity, a user must have visibility into all items linked to it. This rule establishes a strict dependency: if a user lacks access to even one associated record, the activity itself remains hidden. The platform does not provide partial visibility for activities that connect to multiple objects. A user cannot view the activity if they do not have visibility into every single item linked to it.
This constraint applies specifically to the items connected to the activity record. If an activity links to a deal and a contact, the user needs visibility into both the deal and the contact to see the activity. If the user has access to the deal but not the contact, the activity will not be visible. The visibility check is comprehensive regarding the linked items. It is not enough to have access to just the primary object or the activity record itself. The user must hold the necessary permissions for each linked entity.
Revenue leaders should audit their team's access permissions to ensure visibility gaps do not hide critical pipeline interactions. Check which users have access to the specific deals and contacts associated with high-value activities. If a user is missing visibility on a linked contact, they will not see the activity, regardless of their access to the deal. Verify that sales representatives have the required visibility into all linked items to maintain accurate pipeline visibility. This prevents situations where activities exist in the system but are invisible to the users responsible for those deals. Ensure that access rights align with the linking structure of your activities.
Can users see an activity if they do not have visibility into the linked deal?
No. According to Pipedrive, to see an activity, a user must have visibility into all items linked to it. If the user does not have visibility into the linked deal, they cannot see the activity. The requirement applies to every item linked to the activity, including the deal. Lack of visibility into any single linked item results in the activity being hidden from that user.
Related guides
FAQ: How to link activities to deals in crm
Does linking an activity to a deal in Pipedrive automatically link it to the contact?
Yes, according to Pipedrive, an activity linked to only a deal is automatically linked to the contact person and organization linked to that deal. The automatic association applies when the activity is linked only to a deal. The system handles the association with the contact and organization without requiring manual linking to those separate records.
Can users see an activity if they do not have visibility into the linked deal?
No, according to Pipedrive, a user must have visibility into all items linked to an activity to see it. If a user lacks access to the deal or any other linked record, the activity remains hidden from their view. This constraint ensures that activity visibility aligns with the user's access rights to the underlying data.
Are activity properties stored separately from CRM object properties in HubSpot?
Yes, according to HubSpot, activity properties, excluding calls, meetings, and tasks (BETA), are stored separately from CRM object properties. These specific activity properties cannot be edited from the property settings. This separation distinguishes how activity data is managed compared to other CRM object fields.
What does a collection-valued navigation property represent in Microsoft Dynamics?
According to Microsoft, collection-valued navigation properties represent collections of entities which may represent either a one-to-many (1:N) or many-to-many (N:N) relationship between the entities. This definition applies to the phonecall EntityType in the Microsoft Dynamics data platform. The property type indicates the nature of the relationship between the linked records.
How many levels of record source detail does HubSpot track for activities?
According to HubSpot, Record Source Detail 1 is the first level of detail on how the activity was created. The platform tracks three levels of record source detail for activities. These levels provide increasing granularity on the origin of the activity record within the system.