> For the complete documentation index, see [llms.txt](https://help.fielddoc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fielddoc.org/essentials/portfolio/sections.md). # Sections IN THIS ARTICLE Sections are optional sub-folders within Projects that allow for further organization of activity records. *** ## Sections **Sections** allow you to create subfolders within your project to further organize activity records. Each section has its own summary overview page, similar to the main Project Overview, offering a clear way to parse, manage, and share subsets of your data. This is especially helpful for organizing updates or segmenting work by geography, implementation phase, or project team. Sections can only be added within an existing project. {% hint style="info" %} In Legacy FieldDoc, Sections were referred to as ***Sites***. The name was updated to provide a more generic and flexible naming structure that better reflects the wide range of ways users organize their nature-based work in FieldDoc. {% 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://help.fielddoc.org/essentials/portfolio/sections.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.