> For the complete documentation index, see [llms.txt](https://support.senterasensors.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.senterasensors.com/home/fieldagent-web/fields/share-a-field.md). # Share a field Share one field, or every field in your list, with someone by email. Share one field, or every field in your list, with someone by email. The person you share a field with can see its boundary, map layers and zones, and download the data those layers hold. They don't need to be in your organization. {% hint style="warning" %} A share made from FieldAgent Web lasts 365 days, and you can't end it from FieldAgent Web. {% endhint %} {% hint style="success" icon="headset" %} If a share has to end before it expires, contact . {% endhint %} *** ## Share one field {% stepper %} {% step %} #### Open the field Open the field you want to share. {% endstep %} {% step %} #### Click the share icon Click the share icon

next to the field name. The field header with the back arrow, the field name and the share icon

The **Share Field** form opens.

The Share Field form with an Email address box and a SHARE button, next to the field boundary on the map

{% endstep %} {% step %} #### Enter the email Type the recipient's **Email address**. The **SHARE** button becomes clickable once you've entered an email. Click **SHARE**.

{% endstep %} {% endstepper %} *** ## Share every field in the list The share covers the fields in your field list. To share only some of them, search or filter the list first. {% stepper %} {% step %} #### Open the field list Click **Fields** in the navigation bar. Filter the list with **Search** or **Crop Season** to narrow which fields get shared. {% endstep %} {% step %} #### Click the share icon Click the share icon

at the top of the Fields list. The top of the Fields panel with the share and plus icons

The **Share Fields** form opens and tells you how many fields you're sharing, such as "You're about to share 17 fields." Verify the number of fields is correct before you move on. {% endstep %} {% step %} #### Enter the email Type the recipient's **Email address** and click **SHARE**.

{% endstep %} {% endstepper %} *** ## How the recipient gets the field The recipient gets an email saying that fields have been shared with them. The next step depends on whether they have a FieldAgent account. * With a FieldAgent account, they find the fields under **Fields Shared With Me** in the **Select Organization** list. They can open the fields, add map layers and download data. * Without an account, they open the field from the link in the email and can only view it. *** ## Share a field with yourself If you imported imagery into a field outside your home organization, such as a partner organization's field, share that field with yourself. It then appears under **Fields Shared With Me**, where you can view its mosaics and analytics and create reports. *** ## Related pages {% content-ref url="/pages/tJhdYg1p7iVXeYvA3CW2" %} [Organizations and Fields Shared With Me](/home/fieldagent-web/account-and-organizations/organizations-and-shared-fields.md) {% endcontent-ref %} {% content-ref url="/pages/NbXwipivNBx5sLB8YHDx" %} [Download and export data](/home/fieldagent-web/export-and-share/download-and-export-data.md) {% endcontent-ref %} --- # 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://support.senterasensors.com/home/fieldagent-web/fields/share-a-field.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.