> For the complete documentation index, see [llms.txt](https://docs.sylvera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sylvera.com/excel-add-in/project-lists.md). # Project lists Keep named lists of projects and see when their Ratings change Lists are named groups of projects, such as "To buy" or "Mexico IFM". Use them to track a pipeline or a portfolio and see Rating changes. ## Add projects to a list * **From a preview:** select **Add to list** and tick one or more lists * **From search or Screen:** tick projects, or use all matches, then select **Add to list** * **From the sheet:** select cells holding registry and ID, then select **Add to lists** on the ribbon A project can be in many lists. Each add takes up to 1,000 projects. ## Rating-change alerts The **Lists** view shows when a project in any of your lists has a new Rating, a higher or lower Rating, or has been placed On Watch. Alerts are checked when you open the pane or select **Check now**. Select **Mark all as seen** to clear them. ## Put a list in a sheet Open the list, choose how the rows behave, then select **Insert table**. Use **Columns** to choose the fields. * **Current projects:** one fixed row per project, with live data. Works for anyone who opens the workbook. * **Follow this list:** inserts `=SYL.LIST("To buy", …)`. Rows update as you add or remove projects in the list. Lists over 10,000 projects always use this option. {% hint style="warning" %} **Lists are saved on this device.** They follow you across workbooks on the same computer, but not to another computer, and they aren't shared with colleagues. A colleague who opens a workbook using `SYL.LIST` sees an error in its place. Use **Current projects** when you plan to share the file. {% endhint %} --- # 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.sylvera.com/excel-add-in/project-lists.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.