> 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/activities/general-settings/project.md).

# Project

<figure><img src="https://2238918414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FatQfu0bk7aRHUPp2fz19%2Fuploads%2FB9tHUYmSRzqvluRqzRBc%2FScreenshot%202025-03-26%20at%201.23.51%E2%80%AFPM.png?alt=media&amp;token=f31845e1-cc83-43b7-be3c-fb3d134bade6" alt="" width="563"><figcaption></figcaption></figure>

IN THIS ARTICLE

FieldDoc Portfolios are organized with Project Folders and Site Sections. Check, edit, and delete the configuration within the Project view.

***

## Projects

Activity records are the base unit in the FieldDoc system. Standard user Portfolios include two levels of organization so that you can more clearly organize these records. Project folders and sub-folders called, Sections, allow users to segment the activity records and roll up analytics for the contained records. This view allows you to add, edit, or remove the organization of each activity record.

{% hint style="success" %}
**Best management practices for organizing your activity records.**

Activity records can only be organized within a single Project and Section.&#x20;

Activity records do not need to be associated with a Project or Section.

{% 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/activities/general-settings/project.md?ask=<question>&goal=<user_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.