> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/farm-user-and-access-setup/farms-sharing-between-accounts-and-organizations.md).

# Farms Sharing between Accounts & Organizations

On the **Farms** page, in the **My Farms** tab, you can manage your farms and share them with external users or users from your organization.

{% embed url="<https://www.youtube.com/watch?v=NP6vU0rX2OU>" %}
How to share farms, fields, and underlying data — 30-second video
{% endembed %}

<figure><img src="https://i0.wp.com/help.geopard.tech/wp-content/uploads/2022/04/image-1.png?resize=1024%2C394&#x26;ssl=1" alt=""><figcaption></figcaption></figure>

1. Create a new farm from this page.
2. Open the **Organizations** page. Only users with the **Admin** or **Advisor** role can see it.
3. Use search to quickly find any farm in the list.
4. In the **Action** column, you can share or stop sharing any farm with external users or users from your organization.
5. Use the controls for bulk sharing and unsharing.
6. Rename or delete the farm here.

### Choose the right access level

Select access based on the collaborator’s relationship to your business.

* **Advisor** — for colleagues or business partners. Advisors can access every farm in the organization.
* **User** — for clients who need selected farms only. Share each required farm explicitly.

Adding someone to an organization does not share farms with a **User**. Open **Farms → My Farms**, find the farm, and share it with that user.

{% hint style="info" %}
Use **Advisor** only for trusted internal collaborators. They receive access to all organization farms, including new farms.
{% endhint %}

### If fields are missing in the mobile app

1. Confirm the user accepted the organization invitation.
2. Check their access type in **Your Account → Organizations**.
3. If they are a **User**, confirm every required farm is shared on **Farms → My Farms**.
4. Ask them to sign out and back in to refresh their available farms.

The mobile app shows only fields from farms the account can access. Verify access first in the web app to prevent missed scouting and sampling work.

On the **Farms** page, in the **Shared with Me** tab, you can manage other users’ farms that were shared with you. You can re-share them with external users or users from your organization, or stop sharing them.

<figure><img src="https://i0.wp.com/help.geopard.tech/wp-content/uploads/2022/04/image-3.png?resize=1024%2C411&#x26;ssl=1" alt=""><figcaption></figcaption></figure>

1. Use search to quickly find any farm in the list.
2. The **Shared with Users** column is visible only to users with the **Admin** or **Advisor** role.
3. In the **Action** column, users with the **Admin** or **Advisor** role can re-share or stop sharing any farm with external users or users from their organizations.
4. You can remove the farm from the list here. This removes the farm only for you. It will still be available to the owner and to other users it was shared with.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/farm-user-and-access-setup/farms-sharing-between-accounts-and-organizations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
