Save a deal review view, confirm ALL or ANY logic, and check who can see that saved list.
Key takeaways
- In HubSpot, views you create are private to your profile and Super Admins only, according to HubSpot.
- Logical grouping defines the record set. Pipedrive allows you to create precise filters using ALL and ANY filter groups, according to Pipedrive.
- Condition counts have documented limits. Pipedrive notes that while the maximum number of filter conditions is 16, they recommend using fewer conditions to maintain optimal loading speed, especially if your account contains a large number of items, according to Pipedrive.
- Private searches remain isolated. In Close, your private searches/reports will show in your list, but other team members’ private searches will remain private to them, according to Close.
Save the review filters, check their logic and confirm who can see the view
Building a reusable deal review list requires saving a specific configuration of how records display in a table. To ensure the list functions correctly for a small B2B software firm, you must verify three elements: the saved state, the logical grouping of conditions, and the visibility scope.
The first step is confirming the view is saved as a distinct configuration rather than a temporary filter. A saved view persists the display settings so the same record set appears in every subsequent review. Without this saved state, you would manually reapply filters each week, risking inconsistencies in the data you analyze. A view is a saved configuration of how records display in a table (also called a grid), according to Microsoft.
Start by confirming which logical group matches your review intent before saving the view.
A filled reference table of saved views and limits
The table below summarizes documented visibility rules and filter limits for HubSpot, Pipedrive, and Close. Use this reference to verify that your saved view configuration aligns with the documented behaviors before sharing it with your team.
| Publisher | Visibility default | Documented limit or behavior |
|---|---|---|
| HubSpot | Views you create are private to your profile and Super Admins only, according to HubSpot. | Once opened, up to 5 tabs automatically remain pinned on the index page unless you close them, according to HubSpot. |
| Pipedrive | When creating a new filter in Pipedrive, you can choose whether the filter will be shared with other users or remain private, according to Pipedrive. | The maximum number of filter conditions is 16, according to Pipedrive. |
| Close | Your Private searches/reports will show in this list, but other team members’ Private searches will remain private to them, according to Close. | All Smart Views can be managed in your Saved Views, according to Close. |
Note that the Pipedrive source recommends using fewer conditions to maintain optimal loading speed, especially if your account contains a large number of items, according to Pipedrive. Do not infer a Microsoft limit from the other rows; each row reflects only its own source.
For Close, verify that your Smart Views are accessible within the Saved Views area. This table serves as a quick check before you finalize your weekly deal review setup.
Use ALL and ANY conditions for the intended record set
When building a filtered record list in Pipedrive, the logical grouping of conditions determines which records appear in the results. Advanced filters allow you to create precise filters using ALL and ANY filter groups, according to Pipedrive. These groups function as distinct logical operators that you must select intentionally to match your review criteria.
The ALL condition acts as a strict gate for the record set. When you use ALL conditions in a filter, an item will only appear in your results if it meets every condition listed, whether it’s one, two or ten, according to Pipedrive. This logic requires that every single criterion in that specific group is satisfied for a record to be included. If you are defining a review list where every deal must meet multiple specific criteria simultaneously, such as a particular stage and a specific owner, the ALL group ensures that no record is returned unless it satisfies each of those requirements.
The ANY condition provides a broader inclusion rule that can operate alongside the stricter ALL group. When you use ANY conditions in a filter (alongside any ALL conditions), an item will appear in your results if it meets at least one of the ANY conditions, according to Pipedrive. This allows you to define a set of alternative criteria where a record qualifies if it matches any one of the listed items.
Separate personal views from shared configurations
Visibility rules differ by system, so confirm who sees a saved view before relying on it in a recurring review. In HubSpot's "Create and manage saved views," views you create are private to your profile and Super Admins only by default HubSpot. Changes you make are automatically saved for your user profile HubSpot. This means your adjustments stay within your profile scope unless shared through other mechanisms not described here.
In Pipedrive's "Advanced filtering - Knowledge Base," you can choose whether a new filter is shared with other users or remains private when creating it Pipedrive. This choice determines the initial visibility of the filter at creation time.
In Close's "Lead Filtering and Smart Views," your Private searches and reports show in your list, while other team members’ Private searches remain private to them Close. This confirms that private items do not automatically appear to colleagues.
Do not assume that editing a shared configuration updates every user’s view. HubSpot’s documentation states changes are saved for your user profile HubSpot, not that they propagate to all users. Pipedrive requires an explicit choice to share a filter Pipedrive, implying private filters do not become shared automatically. Close explicitly states private searches remain private to their creator Close.
For your weekly deal review, check the visibility setting of your current view. If you need teammates to see the same filtered list, you must explicitly share it where the system allows that choice.
Check documented tab and filtering limits
HubSpot’s “Create and manage saved views” documentation specifies that once opened, up to 5 tabs automatically remain pinned on the index page unless you close them HubSpot. If you have more than 5 tabs open, the 6th will be automatically closed HubSpot. This behavior applies specifically to the saved views index page described in that documentation.
For record filtering, HubSpot’s “View and filter records” page notes that if the object has more than 2 million associations, cross-object filtering will be unavailable HubSpot. This limitation is tied to the association count of the specific object being filtered, not the total number of records in the system.
Pipedrive’s “Advanced filtering” documentation states that while the maximum number of filter conditions is 16, they recommend using fewer conditions to maintain optimal loading speed, especially if your account contains a large number of items Pipedrive. The same source adds that there is also a company-wide limit of 5000 filters for each user Pipedrive. These limits define the structural boundaries for building complex filter logic within Pipedrive.
Microsoft’s “Create and customize views” documentation provides an example of a view that shows only high-priority opportunities with expected close dates within the next 30 days, sorted by revenue potential Microsoft. This example illustrates a possible configuration but does not establish a recommended time window or best-practice threshold for deal reviews. The 30-day period is part of the illustrative example, not a mandated setting.
When building your recurring review list, verify that your filter logic does not exceed the condition limits documented for your specific system. If you are using HubSpot, confirm that your object’s association count does not trigger the cross-object filtering unavailability threshold. If you are using Pipedrive, keep your condition count well below the 16-condition maximum to align with the loading speed recommendation. These documented limits are structural constraints, not performance targets or accuracy guarantees.
Illustrative example of a weekly filter set
A weekly review can use 4 conditions written before you touch the view. Put 3 conditions in the ALL group: the deal is in the chosen stage, the expected close date falls inside 10 days, and the record meets 1 extra requirement you wrote on the sheet. A record then appears only when all 3 are true. Put 2 owner names in the ANY group so the record can match either name. You then have a clear split between required matches and alternatives, and you save the view only after that split is written down.
Write today's review criteria before changing a view
Before adjusting any columns, sort order, column widths, or filters in your CRM, capture the specific conditions for this week’s review on a physical sheet of paper. This step forces you to define the logical group for your record set before the software interface constrains your thinking. For each condition, mark whether it must be true together with the others or serves as an alternative option. This distinction is critical because it determines whether you are building a strict intersection or a broader union of records.
If you will change many records, read Bulk-edit sales records: 4 checks before saving changes before you save. For stage names, read Open, won, and lost stage rules in 4 sales tools. For a date that moved, read Close date change log: why the date moved.
When you move from paper to the system, you are applying the specific modification capabilities documented for your tool. According to Microsoft, you can modify views by adjusting columns, sort order, column widths, and filters. This capability allows you to align the visible data grid with the criteria you just wrote down. If your paper list specifies that a deal must have a specific stage and a specific close date range, you apply those filters directly. If your list specifies that a deal can have either of two specific owners, you structure the filter logic to reflect that alternative.
Saved review view FAQ
Should these conditions use ALL or ANY?
Use ALL when every listed condition must be true for a record to appear. In Pipedrive’s Advanced filtering, an item appears in results only if it meets every condition listed, whether that is one, two, or ten conditions, according to Pipedrive. Use ANY when you want records that meet at least one of the listed conditions. Write your criteria on paper first and mark each condition as a required match or an alternative before saving the view.
Will changing my view change a teammate's view?
In HubSpot’s Create and manage saved views, your changes are automatically saved for your user profile, according to HubSpot. This scope applies to your profile.
Who can see a private view?
In HubSpot’s Create and manage saved views, views you create are private to your profile and Super Admins only by default, according to HubSpot. This visibility rule is specific to HubSpot. Check your system’s documentation to confirm who else can access saved views in your environment.
What happens when too many view tabs are open?
In HubSpot’s Create and manage saved views, if you have more than 5 tabs open, the 6th will be automatically closed, according to HubSpot. This limit is specific to HubSpot.
Are documented filter limits recommended team targets?
In Pipedrive’s Advanced filtering, the maximum number of filter conditions is 16, but the documentation recommends using fewer conditions to maintain optimal loading speed, especially if your account contains a large number of items, according to Pipedrive. This is a performance recommendation from Pipedrive, not a universal team target. Do not treat this limit as a best-practice threshold for all systems.
Evidence register
Found an error in this note? The correction record explains how to report it.