> 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/it/tour-del-prodotto-app-web/managing-crop-season-information-with-tags-labels/case-managing-fields-for-several-clients.md).

# Caso: gestione di appezzamenti per più clienti

Se utilizzi GeoPard per gestire aziende agricole o campi per più clienti, puoi creare etichette per distinguere i campi in base ai valori dei nomi, come mostrato nella tabella seguente per ciascun cliente:![](https://lh4.googleusercontent.com/5GkL9QURQ4xPDeX75GrIwpdlActGWuh3cy-risWkICmKyE3xfq-ZjROs0tJqZmAhjCtVY4UbZYJFGrkv05yCXtno-qbwUDUzVNQ9_5kGv3lCOSDI9RF6V0Q1b9dJbXQwEch7lc17)

<figure><img src="https://lh6.googleusercontent.com/zTuxzS7BVUQXlqmFAsAZvSuM8g06MxGI9Y-EJTlUUBzMGaPPryI5SA7ME79wdXAiRQdY1fdE0M0ngJJ4plQaggerc72bYRlaTXfGpDfdEDtexVOM_aYYFhmQdURZCihSE7ieiZSl" alt=""><figcaption></figcaption></figure>

Puoi configurare la gerarchia descritta in due modi:

1. Manualmente: crea tutte le etichette (coppie chiave-valore) tramite l’interfaccia e assegnale con un’operazione in blocco. Fai clic sul pulsante **Modifica campi** e seleziona i campi a cui vuoi assegnare un’etichetta, quindi fai clic sul pulsante **Aggiungi etichette** per assegnare le etichette selezionate, quindi fai clic sul pulsante **Termina modifica** per uscire dalla modalità di modifica.
2. Automaticamente: carica insieme i confini dei campi nei file .shp e .dbf; il file .dbf contiene gli attributi con i dettagli della gerarchia.

<figure><img src="https://lh3.googleusercontent.com/3Ov8eCEa2FUAj4zTt9AlKygOVUKUhf5FOEag3LBwvs9Zy2dLt2-UPcCcI-5VPrBzlhpuNWph1QdGBLJvU3Ltpzsii1-aWFaKDazVv9Fi-ah_6ZseFw6f6RdZeQ0BH54xBGCq3Bu8" alt=""><figcaption></figcaption></figure>

Fai clic su **Carica** nel menu a sinistra, seleziona l'azienda agricola in cui caricare i confini, seleziona il file .dbf e fai clic sul pulsante **Carica** .

Attendi la finestra di conferma, che indicherà che i confini sono stati caricati correttamente:

<figure><img src="https://lh3.googleusercontent.com/nlGv5apThqj41M-5fW0GUe2Nntju-RKcuAaGH-UwwzxoeIHRoCoghIcBPq-HtkTgrQOIUAGtayx13Qt8Vh-sGLmkpm2d7PQLpZxUeRXKP2iAaRYEeQbAGyXfIgqYhgtfKaXaFfx_" alt=""><figcaption></figcaption></figure>

Se il file .dbf conteneva le etichette, le vedrai nella vista Campi:

<figure><img src="https://lh5.googleusercontent.com/mn42M7lb6Ylt9CYx7kEup0QRfS5lXuNky-fA9OplSIEmx-S9j2HqsDtOwa2e4J98VB-SDhGdbldr9TEWKV7jReaesyq24Z7W5NCUqkKf3F6te1DrJ-Q30GG4yVvJJukydx9umtPt" alt=""><figcaption></figcaption></figure>

Per filtrare l’elenco dei campi, puoi usare le etichette create: fai clic sul filtro e seleziona «Nome cliente» -> «John Smith» per visualizzare solo i campi del tuo cliente John Smith:

<figure><img src="https://lh6.googleusercontent.com/ZcJ24Zk5Qxh8FDbwsHIhn_7f1zWiGAU2VBt0Z934NOm6AN4ySZUHnHuzDmzURI6q-u_Ft6oJfdcMy8M2OBtYtgzyf64_aNRJDGqtqToabP0bJevk9IIqUzHAE0o20sOGGJlWJGJk" alt=""><figcaption></figcaption></figure>

Ricorda che puoi applicare più criteri di filtro in base alle etichette che hai creato:

<figure><img src="https://lh3.googleusercontent.com/ODKBw5rgDtuFflGHhVyfY--kl0AhcMD1TfznC1kSmNWCIMJXSKnClfzithacEIbR7p99rLSfljQYbToYeJkFgxT0EPRyJ7nvkiIC-Boz7KvS7R7Gibnoxjb118aNQrf35T6mX7Ic" alt=""><figcaption></figcaption></figure>


---

# 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://docs.geopard.tech/geopard-tutorials/it/tour-del-prodotto-app-web/managing-crop-season-information-with-tags-labels/case-managing-fields-for-several-clients.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.
