> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-saved-searches.md). # How to use Saved Searches Struct PIM's Saved Searches help you save, organize, and quickly reuse searches across the PIM. ## What are saved searches? Saved Searches are a powerful way to streamline your daily work in Struct PIM. Whether you're keeping track of products missing important information, monitoring specific brands, or reviewing products that require attention, Saved Searches give you quick access to the information that matters most without recreating the same search criteria each time. You can organize searches into folders, keep them private for personal use, or share them with your team. This guide covers the basics of creating and managing Saved Searches, as well as how to use them with Dashboard and Timeline widgets ### Guides * [How to create and use Saved Searches](/tutorials/guides/how-to-use-saved-searches/how-to-create-and-use-saved-searches.md) * [How to use Saved Searches on Dashboards](/tutorials/guides/how-to-use-saved-searches/how-to-use-saved-searches-on-dashboards.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.struct.com/tutorials/guides/how-to-use-saved-searches.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.