> 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.md).

# General Settings

Edit Activity modal contains a lot of editable fields associated with the Activity record.

<figure><img src="https://2238918414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FatQfu0bk7aRHUPp2fz19%2Fuploads%2FcvstQJczYvPnOfa6H77G%2FScreenshot%202025-03-25%20at%202.24.05%E2%80%AFPM.png?alt=media&amp;token=bd7fc6fe-45a9-4237-8e69-3a874dc0428f" alt="" width="563"><figcaption></figcaption></figure>

IN THIS ARTICLE

This tutorial walks you through the fields in the Edit Activity > General Settings view. Each field is tied to a single activity record and helps track progress toward installation and ecosystem outcomes.

***

## General

In this view, you can enter in a unique name for your activity record. We recommend making sure that you're name is unique so that you don't end up with multiple records with the same name.&#x20;

<table><thead><tr><th width="179.27734375">FieldDoc Field Name</th><th>Import Field Name</th><th>Description</th><th>Tips</th></tr></thead><tbody><tr><td>Name</td><td>practice:name</td><td>This name appears throughout the system and is visible to anyone who can see the record.</td><td>Make your name unique! If your organization has a unique identifier, you can use that; otherwise, make sure you avoid having seven records named "Forest Buffer - Narrow"</td></tr><tr><td>Description</td><td>practice:description</td><td>The description is a text field that allows you to add a narrative about your activity.</td><td>Your description field may be useful for collaboration and for any program managers that you share the record with. Think, what would our future selves want to remember about this record?</td></tr></tbody></table>


---

# 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.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.