If a saved search is useful enough to run repeatedly, placing it in the NetSuite Reports tab gives users a more familiar and accessible way to find it. NetSuite supports this through the Available as a Report setting on the saved search record, combined with a selected report category and appropriate audience permissions.
To display a saved search in the Reports tab in NetSuite, open or create the saved search, go to its Available as settings, select Available as a Report, choose a Report Category, and save the search. The saved search then appears under Reports in the selected category for users who have permission to access the search and its underlying record data. If it does not appear, check the report category, audience restrictions, role permissions, search owner, and whether the saved search is available to the relevant users.
Why display a saved search in the Reports tab?
The Reports tab is a central navigation point for financial, operational, and management reporting in NetSuite. Users who already look there for standard reports are more likely to discover a saved search when it is placed in the same menu structure.
This approach is particularly useful when a saved search has become an established report rather than a temporary working query. Examples include an open order report, an approval backlog, a customer activity report, or a transaction exception report. The report can continue using the flexible criteria and formula capabilities of a saved search while becoming easier to access from the NetSuite reporting menu.
Displaying a saved search as a report also avoids requiring every user to navigate through Lists, Reports, or the global search bar to find it. That improves consistency, especially when several roles need to run the same report with the same columns, filters, and summary logic.
However, adding a saved search to the Reports tab does not automatically make it visible to everyone. Menu placement and access control are separate considerations. The search must be configured correctly, and the user's role must have access to the relevant saved search and record type.
For a broader view of how Saved Searches compare with other NetSuite reporting options, see our guide to choosing among NetSuite reporting tools. This article focuses specifically on making a saved search visible and usable from the Reports tab.
How to display a saved search in the Reports tab in NetSuite
The process consists of creating a report-ready saved search, enabling the report option, assigning the search to a category, and validating access from the intended role.
1. Open an existing saved search or create a new one
Start by navigating to the saved search record. Depending on your role and NetSuite account configuration, this is typically available through Reports > Saved Searches > All Saved Searches or through the relevant saved search menu option.
You can also create a new saved search from the record type you want to analyze. For example, a transaction saved search might report on invoices, sales orders, purchase orders, or cash sales. The selected record type determines the data available in the Criteria, Results, and formula fields.
Before publishing the search in the Reports tab, verify the basic report design:
The criteria return the intended population.
The results include the columns users actually need.
Summary types such as Group, Sum, or Count are applied deliberately.
Date filters use the correct relative or fixed date logic.
Formula fields return meaningful values and do not create unnecessary performance overhead.
The search title clearly describes the report's purpose.
A report menu should not contain several searches with nearly identical titles. A naming convention such as “Open Sales Orders by Customer” or “Invoices Due in 30 Days” is more useful than a generic title such as “Sales Search.”
2. Open the Available as settings
On the saved search definition, locate the Available as section or tab. NetSuite places several publication options in this area, including settings that allow a saved search to function as a list view, dashboard view, or report.
Select Available as a Report. This tells NetSuite that the saved search should be exposed through the report navigation structure rather than remaining available only through saved search menus.
The exact placement and appearance of fields can vary by account, feature configuration, and NetSuite interface version. If you do not see the option, confirm that you are editing the saved search itself rather than viewing its results, and check whether your role has permission to edit saved searches.
Selecting Available as a Report changes the search's navigation behavior. It does not convert the search into a standard financial report or replace the underlying saved search engine. The report still uses the saved search's criteria, results, joins, formulas, sorting, and summary configuration.
3. Choose a report category
After selecting Available as a Report, choose the appropriate Report Category. This category determines where users find the saved search under the Reports tab.
Choose a category that matches the report's audience and subject. A transaction exception report might belong under a sales or operational category, while a receivables-focused search might fit under a financial category. The category should help users predict where the report belongs.
If the account includes custom report categories, use an existing category where possible rather than creating a new category for every saved search. Excessive custom categories make the Reports menu harder to navigate and create maintenance work for administrators.
The category is a menu-location setting, not an access-control setting. Assigning a saved search to a category does not grant users permission to view the search. Access is controlled through the saved search's audience and the role's permissions.
4. Configure the saved search audience
Go to the saved search's Audience settings and define who should be able to access it. Depending on the reporting requirement, access may be limited by role, department, subsidiary, employee, group, or other audience values available in the account.
A saved search can be available as a report but still absent for a user because that user is outside the configured audience. This is one of the most common reasons an administrator can see a report while another employee cannot.
Use the narrowest audience that meets the business requirement. A report containing sensitive financial, employee, customer, or subsidiary information should not be made broadly available simply because the Reports tab is convenient.
Also review whether the search is marked Public, if that setting is being used. Public availability and audience restrictions work together with role permissions. They should be designed as part of the report's governance model, not treated as an afterthought.
5. Save the search and test the report menu
Save the saved search after applying the report setting, category, and audience. Then open the Reports tab and navigate to the selected category.
The report may not appear immediately in the exact location you expect if the account uses customized navigation, role-specific menus, or category-specific permissions. Test the search from the role that will use it, not only from an administrator role.
Run the report and verify more than its menu location. Confirm that:
The returned records match the intended criteria.
Users see the correct columns and summary values.
Date filters behave as expected.
Links open the correct NetSuite records.
The report does not expose fields or records that the audience should not access.
The search performs acceptably with the account's real data volume.
A report that appears in the correct menu but returns incomplete data for a role is not fully configured. NetSuite data visibility rules, subsidiary restrictions, employee restrictions, and field-level permissions can affect the results.
Why is my saved search not showing in Reports?
The most likely cause is that Available as a Report is not enabled or that no valid report category has been selected. Open the saved search and inspect the publication settings first.
If those settings are correct, check the following areas:
The search is not saved. Changes made to a saved search form do not affect the menu until the record is saved. If another administrator created a copy or edited a different search with a similar title, confirm that you are working on the correct search.
The report category is incorrect. A saved search appears under the category assigned to it. Look through the selected category rather than assuming it will appear at the top level of the Reports tab.
The user is excluded from the audience. An administrator may see the search while a standard role cannot. Review the Audience tab and test with the actual role.
The role lacks permissions. The role needs appropriate permission to the saved search and the record type used by the search. A report menu entry cannot bypass NetSuite's access controls.
The search is inactive. An inactive saved search will not function as an available report. Confirm that the saved search itself is active.
The role's center or navigation differs. NetSuite roles can use different centers, dashboards, and menu configurations. A report category available to one role may not be presented identically in another role.
The account's reporting features differ. Some options depend on enabled features, role permissions, and account configuration. If the Available as a Report option is missing entirely, review the role's ability to create and edit saved searches or ask a NetSuite administrator to confirm the account setup.
How do report categories affect saved search navigation?
Report categories control organization, not data logic. They determine where the saved search is listed, while the saved search record continues to control filters, joins, formulas, sorting, and output.
This distinction matters when an administrator changes a report category. Moving a saved search from one category to another does not change its results. It changes where users look for it. That means category changes should be communicated when a report is already part of a team's regular process.
A practical category structure should reflect how users think about reports. Categories based on business purpose are more useful than categories based only on the person who created the search. For example, “Order Management,” “Accounts Receivable,” and “Inventory Control” give users clearer navigation cues than “Admin Reports” or “Custom Searches.”
NetSuite's native reporting menu also includes standard reports, so avoid naming custom saved searches in a way that makes them appear to be official standard reports. Adding a prefix such as “Custom” is useful only when it improves clarity. The title should still state what the report shows.
Can users customize the displayed saved search?
Users can interact with a saved search report according to the permissions and configuration assigned to them, but they should not be expected to modify the underlying definition. The saved search's owner or an authorized administrator controls permanent changes to criteria, results, formulas, and audience settings.
If users need flexible analysis, consider whether the search should expose useful filters or whether a separate search is more appropriate. A single report with too many optional filters can become confusing and slow to run. A small collection of purpose-built reports is easier to understand and govern.
The Available as a Report setting is also different from dashboard publication. A saved search can be configured for a dashboard portlet, a list view, scheduled email, or report navigation. Each destination serves a different use case:
| Publication method | Best use |
|---|---|
| Reports tab | Repeatable reports users run from a shared menu |
| Dashboard view | At-a-glance monitoring and role-based visibility |
| List view | Working directly with records in a list |
| Scheduled email | Delivering recurring results without manual navigation |
| Reminder or KPI use | Surfacing action items or summarized metrics |
A saved search published in the Reports tab does not automatically become a dashboard KPI or scheduled email. Configure each use separately when the reporting process requires it.
How should we secure a saved search report?
Secure the report at three levels: saved search audience, role permissions, and data visibility. These controls work together, and the most restrictive applicable rule determines what a user can see.
First, limit the audience to the roles or users who need the report. Second, verify that those roles have permission to view the record type and relevant transactions. Third, review NetSuite restrictions such as subsidiary, department, location, employee, and accounting period access.
Do not assume that hiding a report from the Reports tab protects its data. A user who can access the saved search through another route may still find it if the search is public or available through a dashboard, list view, URL, or other navigation path.
Saved search formulas also deserve review. Formula fields can expose calculated values that are not obvious from the report title. Avoid including sensitive fields unless they are necessary, and document any formula that affects a financial or operational decision.
For organizations with many custom searches, establish ownership and review dates. A simple inventory should record the search name, purpose, owner, audience, source record type, report category, and last review date. This prevents outdated searches from accumulating in the Reports menu.
Performance considerations for saved searches displayed as reports
Making a saved search available as a report does not improve its performance. Query efficiency still depends on the record type, criteria, joins, formulas, result columns, sorting, and dataset size.
Start with selective criteria. A search that scans every historical transaction each time a user opens it places more demand on the account than one restricted to an appropriate date range or status. Remove columns that users do not need, especially fields from multiple joined records.
Be cautious with formulas and summary searches. Complex SQL formulas, nested functions, and multiple joins create additional processing work. A formula should solve a defined reporting requirement, not compensate for unclear criteria or unnecessary columns.
Test the search using realistic data. An administrator working in a small test set may not notice performance issues that appear in a production account with years of transactions. If a report is slow, simplify the criteria and results before considering a custom SuiteScript solution.
A Suitelet is appropriate when the reporting interface requires custom controls, a specialized layout, or logic that a saved search cannot support. It is not required merely because a saved search needs to appear in the Reports tab. For a general explanation of when custom development is justified, see our article on when a NetSuite Suitelet makes sense instead of a Saved Search.
Common mistakes when publishing saved searches as reports
The most frequent mistake is treating menu placement as the entire configuration. A report needs a clear purpose, reliable criteria, appropriate access, and a defined owner in addition to the Available as a Report setting.
Another mistake is publishing a working search before reviewing its title and output. Saved searches often begin as personal analysis tools. Their criteria may contain temporary filters, their names may be unclear, and their columns may reflect the creator's needs rather than the intended audience.
Administrators should also avoid copying a saved search repeatedly to solve every reporting request. Duplicates create conflicting definitions and make it difficult to determine which version is authoritative. When the requirement is materially different, create a separate report with a clear title and documented purpose. When only the audience differs, review the access configuration instead of creating another copy.
Finally, do not use a saved search as a substitute for a formal financial report when accounting requirements call for period controls, financial layouts, consolidated reporting, or standard accounting presentation. Saved searches are powerful for record-level and operational reporting, but they are not the best tool for every reporting need.
Conclusion
Displaying a saved search in the Reports tab in NetSuite is a straightforward way to make recurring operational reporting easier to find. The key configuration is Available as a Report, followed by selecting the correct report category and validating the audience.
The technical setup is only one part of a reliable reporting process. We recommend testing the report from the intended role, reviewing its security, limiting unnecessary joins and formulas, and assigning an owner for future maintenance. If your saved search requirements involve complex reporting logic, access rules, or performance concerns, contact Versich to discuss your NetSuite reporting needs.
