> 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/account-and-organizations/organizations-and-shared-fields.md).
# Organizations and Fields Shared With Me
Switch organizations and find the fields other people have shared with you.
Fields, along with their surveys and map layers, each belong to one organization. FieldAgent Web shows you the fields, orders and tasks of the organization you're working in.
***
## Select an organization
Open the **Select Organization** dropdown, and pick the organization with the fields you want to work on. An organization with sub-organizations has a chevron that shows or hides them.
The organization you pick also decides which flight tasks, orders and [grower organizations](/home/fieldagent-web/account-and-organizations/grower-organizations.md) you see.
{% hint style="info" %}
A parent organization shows its own fields together with the fields of its sub-organizations. Select a sub-organization to see only its fields.
{% endhint %}
Imagery you import and orders you place are stored on the field, under the organization selected at the time.
***
## Find fields shared with you
Select **Fields Shared With Me**, the first entry in the **Select Organization** list. It holds the fields other FieldAgent users have shared with your user account.
Fields Shared With Me highlighted
You can view these fields, add map layers and download data just as you would with your own. Their orders and flight tasks don't show on the Orders and Flight Tasks pages. A share made from FieldAgent Web [lasts 365 days](/home/fieldagent-web/fields/share-a-field.md).
{% hint style="info" icon="lightbulb" %}
If you need a field from an organization you can't access, ask someone with access to that organization to share it with you. It then appears under **Fields Shared With Me**, with its imagery and results.
{% endhint %}
***
## Related pages
{% content-ref url="/pages/2trXtXqotc0MLnG2h4uR" %}
[Find a field](/home/fieldagent-web/fields/find-a-field.md)
{% endcontent-ref %}
{% content-ref url="/pages/iVojQbg4PvArC7gkYtzw" %}
[Share a field](/home/fieldagent-web/fields/share-a-field.md)
{% endcontent-ref %}
{% content-ref url="/pages/9QAEYl2FGHBGUXwZJosg" %}
[Account settings](/home/fieldagent-web/account-and-organizations/account-settings.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/account-and-organizations/organizations-and-shared-fields.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.
