> 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/integrations/connect-with-climate-fieldview.md).
# Connect with Climate FieldView
Connect Climate FieldView to FieldAgent Web, import its fields and link your growers' FieldView accounts to their own grower organizations.
With Climate FieldView connected, you can import your field boundaries, field names and farm names into FieldAgent Web. FieldAgent sends map layers back to FieldView.
***
## Connect your own account
You connect on the FieldAgent administration site, admin.sentera.com, with your FieldAgent sign-in.
{% stepper %}
{% step %}
#### Open Connections
In FieldAgent Web, open **Account** and use the Manage Connections button:
The administration site opens on its Connections page .
Climate FieldView not connected
{% endstep %}
{% step %}
#### Connect to Climate FieldView
In the Climate FieldView row, click **Connect to Climate FieldView** .
{% endstep %}
{% step %}
#### Sign in and allow
Sign in to Climate FieldView with your FieldView credentials, then click **Allow**.
The permissions FieldAgent asks for
* Retrieve application, harvest and planting activities.
* Retrieve farm organization and field information.
* Retrieve basic account information.
* Send imagery to FieldView.
You return to the administration site, where the Climate FieldView row shows **Connected** and its Expires On date.
{% endstep %}
{% endstepper %}
Reload **Account** in FieldAgent Web to see the new connection status there.
***
## Import your FieldView fields
{% stepper %}
{% step %}
#### Start a new field
In FieldAgent Web, open **Fields** and click the plus icon .
{% endstep %}
{% step %}
#### Choose Climate FieldView
In the Partner Fields module, open **Choose a Partner to Import Fields** and select **Climate FieldView**.
{% endstep %}
{% step %}
#### Select the fields
Use the Select Fields for Import button:
The panel lists the fields of the connected FieldView account, each with its farm. Search the list or filter it by **Crop Season** to find a field, then select the ones to import.
{% endstep %}
{% step %}
#### Import
Click **IMPORT**. The button counts your selection, for example **IMPORT 1 FIELD**. A success message appears when the import is complete.
{% endstep %}
{% endstepper %}
The imported fields appear in the **Fields** panel of the organization you had selected.
{% hint style="info" %}
Importing a field again updates its name, boundary and farm name to match FieldView, without duplicating it. Its contents, including its map layers, stay in place.
{% endhint %}
***
## Connect a grower's account
Advisors and retailers connect each grower's FieldView account to its own [grower organization](/home/fieldagent-web/account-and-organizations/grower-organizations.md). The grower's fields then import under that organization and stay separate from other customers' fields.
{% stepper %}
{% step %}
#### Name the grower organization
Open **Grower Management** and use the Add Grower Organization button:
Enter the **Grower Organization Name**.
{% endstep %}
{% step %}
#### Send the connection invite
Use the Send Connection Invite button:
Set **External Partner** to **Climate FieldView**. Set **Send To** to **Add Climate FieldView Account Holder**. Enter the grower's first name, last name and email address.
If the grower is with you and can sign in to FieldView on your screen, choose **Myself** under **Send To** instead.
{% endstep %}
{% step %}
#### Add the organization
Click **ADD GROWER ORGANIZATION**.
{% endstep %}
{% endstepper %}
The grower receives an email with a link. After they open it, sign in to Climate FieldView and click **Allow**, their account is connected to the grower organization. Their FieldView fields are imported into FieldAgent under it.
{% hint style="info" %}
The new organization appears in **My Growers** on **Grower Management**. Select it in **Select Organization** to see its fields.
{% endhint %}
***
## Renew the connection
A connection expires on its **Expires On** date, and you renew it on the Connections page. Once Climate FieldView is connected, its row has actions to renew and disconnect, like the Operations Center row in the Connections page figure.
1. Open **Account** and click **MANAGE CONNECTIONS**.
2. Use the renew action.
3. Sign in to FieldView and click **Allow** again.
***
## Related pages
{% content-ref url="/pages/9QAEYl2FGHBGUXwZJosg" %}
[Account settings](/home/fieldagent-web/account-and-organizations/account-settings.md)
{% endcontent-ref %}
{% content-ref url="/pages/joIptcgqiAlgayUP3DRn" %}
[Account administration](/home/fieldagent-web/account-and-organizations/account-administration.md)
{% endcontent-ref %}
{% content-ref url="/pages/uXRyz5qMoN5XbGTlwttn" %}
[Grower organizations](/home/fieldagent-web/account-and-organizations/grower-organizations.md)
{% endcontent-ref %}
{% content-ref url="/pages/coc3JMK3CQEMMwBxAaDk" %}
[Create a field](/home/fieldagent-web/fields/create-a-field.md)
{% endcontent-ref %}
{% content-ref url="/pages/ouJZuSAbyJ2zygINZwuw" %}
[Connect to John Deere Operations Center](/home/fieldagent-web/integrations/john-deere-operations-center.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/integrations/connect-with-climate-fieldview.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.
.
.
.
{% endstep %}
{% step %}
#### Choose Climate FieldView
In the Partner Fields module, open **Choose a Partner to Import Fields** and select **Climate FieldView**.
