Skip down to the research record

Report visibility checks across 4 tools before the call

Quota Forecast Editorial Team · Published · 11 min read

A report can show only the deals that person is allowed to see, as Close notes that visibility restrictions apply across the entire app.

A report can show only the deals that person is allowed to see

In the Lead Visibility section of the Close Help Center, the documentation states that visibility restrictions apply across the entire Close app, including search results, reports, Opportunities, and Pipelines, according to Close. This means a user who cannot see specific leads will not see those leads in any of those four areas. The same page provides a specific example to illustrate how this affects data aggregation. It states that for example, their reports would display only 60% of the total statistics if they are only able to see 60% of the leads, potentially resulting in incomplete reports if this is not taken into consideration, according to Close. This 60 percent figure is an example on that help page, not a measured result for your team or a quota target. It serves to show that if a user’s visibility is limited, the totals in their reports will reflect only that limited subset of data.

Key takeaways for who a sales report includes before the weekly call

Verify your visibility group assignment before the call. Check if you hold deals admin access. Users who have deals admin access will have full visibility of all deals and leads regardless of the visibility group setting, according to Pipedrive. Review Close's report example. Note that this 60 percent figure is an example on the help page, not a measured result for your team. Confirm whether your report includes the whole team or only your owned deals. Do not change permissions or pay for a seat to see the full pipeline.

A filled reference table of who can see and edit deals by publisher

The table below summarizes how each publisher handles deal visibility and editing permissions, using only the specific rules documented in their respective help centers. These definitions clarify whether a user sees a subset of records or the full account data, and whether their editing rights are limited to owned items or extend across the team.

PublisherView RuleEdit/Access Rule
PipedriveVisibility groups dictate what information users can view in Pipedrive, while permission sets determine what actions they can perform, according to Pipedrive.Permission sets decide whether a user can edit all deals, or just the ones they own, according to Pipedrive.
CloseEach role can have up to three fields controlling lead visibility, providing flexibility to match your team’s workflow, according to Close.The source does not specify a separate edit rule in this fact; visibility is controlled by role fields.
HubSpotUsers automatically gain view access for any deals in which they've been set as a collaborator, according to HubSpot.Users automatically gain edit access for any deals in which they've been set as a collaborator, according to HubSpot.
MicrosoftDynamics 365 Sales uses the Opportunity Sales Access Team to provide access to the opportunity record to all users connected under the Sales team connection role category, according to Microsoft.This allows the sales team member users to access and work with the opportunity record in Dynamics 365 for that specific record, according to Microsoft.

Pipedrive separates the concept of seeing data from the concept of changing it. The platform uses visibility groups to control which information is visible to a user, while permission sets control the actions that user can take. This distinction means a user might see a deal but lack the permission to modify it. The permission set specifically addresses the scope of editing, determining if a user is restricted to their own deals or granted the ability to edit all deals in the account.

Close structures lead visibility through role-based fields. Each role can have up to three fields controlling lead visibility, which allows the system to match the specific workflow of the team. This setup determines which leads are visible to users assigned to that role, ensuring that visibility aligns with the team's operational structure rather than being a single global setting.

HubSpot grants access through collaboration. When a user is set as a collaborator on a deal, they automatically gain both view and edit access to that specific record. When a user is set as a collaborator on a deal, they automatically gain view and edit access to that deal.

Microsoft Dynamics 365 Sales manages access through the Opportunity Sales Access Team. The Opportunity Sales Access Team provides access to the opportunity record for all users connected under the Sales team connection role category. This access allows sales team members to work with the opportunity record in Dynamics 365 for that specific opportunity.

Before the weekly call, verify which of these models your organization uses to determine if the report reflects the full team or a limited view.

Pipedrive separates what a user can view from what a user can do

In Pipedrive, the system distinguishes between what a user can see and what a user can do. While permission sets in Pipedrive determine what actions users in your account can perform, visibility groups dictate what information your users can view in Pipedrive, according to Pipedrive. Conversely, a user might see a pipeline but lack the permission set to modify the deals inside it. You must check both settings to understand a user's full scope.

A Pipedrive user can only be associated with one visibility group at a time, according to Pipedrive. This single-group limit means you cannot assign a user to multiple visibility groups simultaneously to combine their access. A Pipedrive user can be in only one visibility group, and a visibility group without access to a pipeline cannot see that pipeline or its deals. You cannot split a user's visibility across separate groups.

Visibility groups that don’t have access to specific pipelines won’t be able to see any trace of the pipeline nor deals inside that pipeline in Pipedrive, as the pipeline will be completely hidden from their accounts, according to Pipedrive. This is not a partial view where the pipeline name appears but the deals are blank. The pipeline itself is invisible. If a visibility group lacks access to a pipeline, the user assigned to that group will not see the pipeline in their list of available pipelines. This complete hiding prevents users from knowing that a specific pipeline exists if they are not authorized to view it.

Close's three visibility fields and the 60 percent report example

The Lead Visibility page in the Close Help Center defines how roles control which leads appear to users. Each role can have up to three (3) fields controlling lead visibility, providing flexibility to match your team’s workflow, according to Close. These fields determine the scope of data a user can access within the application. The visibility restrictions apply across the entire Close app, including search results, reports, Opportunities, and Pipelines, according to Close.

When a user attempts to access a Lead without appropriate visibility, the system displays a blocked access page, according to Close. This mechanism prevents unauthorized viewing of specific records. The help page includes a specific illustration of how this filtering affects reporting metrics. For example, their reports would display only 60% of the total statistics if they are only able to see 60% of the leads, potentially resulting in incomplete reports if this is not taken into consideration, according to Close. This 60 percent figure is an example provided on the help page to demonstrate the impact of visibility limits; it is not a measured result for your specific team or a quota target.

An important exception exists for inbox items. Inbox items are not filtered based on Lead visibility, and a restricted user could potentially see a Task assigned to them on a Lead they do not have access to, according to Close. Therefore, a task appearing in a user's inbox does not imply that the user has full visibility into the associated Lead record. Before the weekly call, check that role's lead-visibility fields, since each Close role can have up to three lead-visibility fields. Do not assume that seeing a task in the inbox grants access to the underlying deal details. Check the specific field configuration for your team's roles to understand the exact scope of visible data.

A collaborator does not get dollar credit

When you review the forecast report before the weekly call, you must distinguish between who can see the deal and who receives credit for the win. In HubSpot, deal collaborators do not receive credit for the amount of the deal, so if any collaborators need monetary credit, you should add them to a deal split, according to HubSpot. A user can be included both in a deal split and as a collaborator for the same deal, according to HubSpot. This dual role allows a person to have view and edit access without automatically receiving monetary credit unless a split is configured. Users automatically gain view and edit access for any deals in which they have been set as a collaborator, according to HubSpot. Therefore, adding a collaborator changes their visibility and editing rights on that specific record, but it does not change the attribution of the deal amount.

In Dynamics 365 Sales, the mechanism for access is tied to the sales team connection. Dynamics 365 Sales uses the Opportunity Sales Access Team to provide access to the opportunity record to all the users connected under the Sales team connection role category, according to Microsoft. This allows the sales team member users to access and work with the opportunity record in Dynamics 365 for that specific record, according to Microsoft. Before the call, verify that the people who need to edit the deal are correctly set as collaborators or sales team members, and verify that the people who need credit are in the deal split. Do not assume that visibility implies credit.

A blank access check for one report

The goal is to identify whether the report reflects the entire pipeline or only the subset of deals your user profile is authorized to view. Do not alter any system permissions or purchase additional seats to complete this check. Instead, observe the current state of the report and record the boundaries of its data set.

If a field is not applicable to your specific tool configuration, leave it blank or mark it as "Not Applicable." This record serves as a reference point for your team to verify that the data presented during the call matches the intended scope.

For example, if the report is filtered by a specific revenue threshold, record that threshold. Microsoft documentation illustrates a filter where "Est.Revenue Is greater than or equal to 1,000,000," which serves as an example of how a specific value can define the boundary of visible data according to Microsoft. Do not interpret this example as a rule that excludes smaller deals from your own quota; it is merely a demonstration of a filter mechanism. Your own report may use different criteria, such as ownership, stage, or date range.

Report access FAQ

What is the difference between a Pipedrive visibility group and a permission set?

Visibility groups dictate what information users can view within the system. Permission sets determine what actions users can perform, such as editing all deals or just owned ones. According to Pipedrive, these two mechanisms operate separately to control data access and user capabilities.

Can one user be in two visibility groups?

No, a Pipedrive user can only be associated with one visibility group at a time. According to Pipedrive, this single-group limitation applies to every user account within the platform. A Pipedrive user can only be associated with one visibility group at a time, and users who have deals admin access have full visibility of all deals and leads regardless of the visibility group setting.

What does Close's 60 percent example actually say?

The example illustrates that reports display only 60% of total statistics if the user can only see 60% of the leads. According to Close, this is a page illustration showing how visibility limits affect report completeness. It is not a measured result for your specific team or a quota target.

Does a HubSpot collaborator get credit for the deal amount?

Deal collaborators do not receive credit for the amount of the deal. According to HubSpot, monetary credit requires adding the person to a deal split. Simply being a collaborator does not assign financial attribution for the win.

Does removing a Microsoft sales team member remove access to that deal?

Dynamics 365 Sales uses the Opportunity Sales Access Team to provide access to the opportunity record for users connected under the Sales team connection role category. According to Microsoft, this allows sales team member users to access and work with the opportunity record specifically.

Sources