Why two administrators can see different data
In Agronavica, seeing less information does not always mean data is missing. Often it means the account is working inside a narrower operating scope: a field, an advised client, or a permission set assigned by the organization.
This matters for administrators, advisors, and field teams. If another administrator created a season and you do not see it, the first thing to check is not who created it. Check which field it belongs to, which advised client is active, and which permissions your user has.
The operating idea is simple: each person should see what they need to work well, without mixing fields or clients that are outside their responsibility.
The field is the operating boundary
The organization is the commercial and administrative frame. The field or operating unit is the daily work frame.
That is why a season, work order, field record, or metric can be visible to one administrator and not another. It does not depend only on the “admin” role. It also depends on assigned operating access.
| Situation | What may happen |
|---|---|
| Ana manages North Field | She sees North Field seasons, orders, and records |
| Bruno manages South Field | He sees South Field seasons, orders, and records |
| Ana creates a season in North Field | Bruno does not see it if he lacks North Field access |
| An owner reviews the organization | They can see the full set when their permission allows it |
This reduces accidental edits or closures across unrelated fields.
Seasons: why a campaign may not appear
Seasons group crops, work, dates, and production. If an expected season is not visible, check:
- that you are in the right field;
- that your user has access to that field;
- that the screen filter is set to active, closed, or all as needed;
- that, in advisor mode, the right advised client is selected;
- that the season is not closed if you are filtering only active seasons.
“No seasons” should be read as “no seasons visible in this context.” It does not automatically mean nothing exists in the organization.
Advisor mode: separation between clients
Advisor mode is designed for professionals working with several advised clients or organizations. The basic rule is that clients do not mix with one another.
When you select an advised client, the app works inside that context. Seasons, work orders, metrics, reports, and evidence belong to that client. If you switch clients, the visible information changes.
In practice, an advised client or managed unit is an operational scope inside one Agronavica organization; it is not a separate legal tenant. The advisor keeps the same account and professional permissions, while new actions are saved under the active managed unit rather than in a shared bucket.
This means the advisor is not manually filtering one global view. They are changing context. When they enter an advised client, only the fields, seasons, work orders, inventory, reports, metrics, and evidence for that client or operating unit should appear.
It also means one advised managed unit does not see records outside its authorized scope just because the same professional supports both. If two legally independent farming companies require separate contracts or data-controller boundaries, each must use a separate Agronavica organization.
This protects:
- confidentiality between clients;
- traceability for each operation;
- control over who can view or edit records.
For an advisor, this separation is part of the product. It is not a visual error.
What changes for the advisor
The advisor can move from one client to another without creating a separate account for every relationship. The important habit is to check the active context before creating seasons, uploading evidence, planning work orders, or reviewing metrics.
If the active context is the wrong client, information may look incomplete or appear to be missing. Before assuming there is a data problem, confirm that you are inside the correct advised client and the correct field.
Advisor mode does not replace each organization’s internal permissions. It complements them. A client may allow the advisor to review, plan, or manage certain areas while keeping other fields, records, or actions outside their scope.
Roles and field teams
In public communication we use “field team”, “field staff”, or “operational collaborators”. The internal word “worker” may appear in technical systems, but it does not describe how Agronavica is used in a real operation.
Field teams usually see assigned tasks, instructions, requested evidence, and allowed actions. An administrator can plan, review, and close workflows according to their permissions. An owner can manage configuration, users, and broader scope.
The role matters, but it does not work alone. Field scope and active context matter too.
What to check before assuming data is missing
If someone says “I cannot see the season”, “the order is missing”, or “that field is not listed”, check in this order:
- Active field or active advised client.
- Screen filter.
- User permissions for that field.
- Record status: active, closed, pending, or archived.
- Whether the user is working as an advisor or inside the main organization.
This sequence resolves most confusion without changing data.
Good administrator habits
Before inviting a new administrator or team member, define what they need to operate:
- every field or only selected fields;
- read-only access or management access;
- access to seasons, work orders, inventory, metrics, or reports;
- a specific advised client, when relevant;
- responsibilities for the field team.
Clear configuration prevents surprises. Once people understand their scope, the app stops feeling “incomplete” and starts feeling like what it is: a view filtered by operating responsibility.
Summary
Agronavica does not show everything to everyone by default. It shows information according to role, field, advised client, and active context.
If something is not visible, check scope and permissions first. With seasons especially, remember: a campaign created by another administrator can exist correctly and still be hidden from you if it belongs to a field or client outside your scope.