📘 Screen: Company/Crop Settings
This is the screen that decides how upCampo behaves in that company: whether the work order requires a storage location, whether fueling asks for the hour meter, whether the field is called "field" or "block", how many decimal places a hectare has, which measurements the technician takes in each crop and which reports go out by e-mail every morning.
When an article in this Help Center says a behavior "depends on the company settings", this is what it is talking about. It is a setup screen: it is changed rarely, but each checkbox changes the routine of everyone.
📍 Location in the system
Menu: File > Company/Crop Settings
At the top of the screen you choose a company and a farm before anything else: that pair defines whose settings you are looking at.
🧩 Main function
Adjust how the web portal and the app behave for the company, set up what is measured in each crop during scouting and schedule automatic report delivery by e-mail.
🗂 The three tabs
- General company settings: how the system behaves, in blocks
- Crop Settings: what is measured in each crop
- Automatic sending: reports and alerts by e-mail
⚙️ General company settings tab
The settings come in blocks that open and close. After making changes, click Save: it applies to the whole screen, not per block.
Pest Scouting
The first three fields are about vocabulary: Display name for 'Quadra', for 'Variedade' and for 'Setor' change the name shown on the screens and in the app. If the farm says "block", type "Block" there and the system starts talking the way the farm does.
In the same block: Dynamic mode when adding pests, Manual Point (APP), Show pest scientific name (APP), Show point opening (APP), Show disabled fields (APP), Do not send data automatically in the APP and Observation updates last scouting date; the last one makes an observation count as a visit, for the purpose of the field's last scouting date.
Crop & Fields
- Allow multiple active seasons: for those who have the main season and the second crop running at the same time
- Show grouping column: shows the Grouping field on the Field screen
- Allow changing Bale during collection
- Decimal places for Ha: how many decimals the area carries in calculations and on screens
- Generate fallow automatically when finishing season planting and the Fallow Crop to be used in that case
Stations & Rain Gauges
The ranges for Low, medium and high rain level, in millimeters. You type only the start of each range: the To field of each one is filled in automatically from the start of the next range. This is what colors the rain gauge on the dashboards.
Operations
The largest block on the screen, divided into six:
| Sub-block | What it controls |
|---|---|
| W.O. Show | Show the Border area option on the order (APP), the Equipment column on the W.O. and the team technical lead column. |
| W.O. Header | Single numbering for orders, allow changing the number and the area of a W.O. with products, clear the fields when leaving the order, require approval of the field work order and send a WhatsApp notification. |
| W.O. Short Identification (Subtype) | Whether the short identification is required and whether it can be changed later. |
| W.O. Execution - Auxiliary Qty | In which executions the auxiliary quantity appears (soil preparation, fertilizing, planting, application, harvest) and how it is captured: by GPS location or QR Code. |
| W.O. Inventory | Inventory Issue Type (required): Average cost or Last cost; this decides at what value the product goes out. Also: show receiving control, require a storage location when creating and when finishing, and Service Order - Show only products with stock, which keeps in the order's product list only those with a balance in some storage location, even before choosing the location (services always appear). |
| Products & Integration | Require a product class and integration ID in the product record, show the integration column in lists, what to do when the dose departs from the label instructions (Warn only or Block) and which ERP the company integrates with. |
Other blocks
| Block | What it controls |
|---|---|
| Purchase order (approval) | Require approval of purchase orders and require double approval. |
| Finance | Require approval to settle. When on, no account payable is paid outside an approved payment batch, on any screen, and the payment window in Accounts Payable/Receivable starts offering Add to batch. Accounts receivable are not affected. When off (the default), nothing changes: anyone who wants to keeps settling installments directly in Accounts Payable/Receivable. See the two caveats below the table. |
| Field history - QR Code | Whether the field's QR Code shows the orders and the products applied. |
| Bale collection | Tracking capture format (Barcode, QR Code or Camera), automatic location capture and automatic opening of the capture screen. It applies to Bale collection. |
| Fleet | Require a fleet classification, require the maintenance work order number and Require hour meter to finish maint. W.O. Without the last one, the finishing of a maintenance work order only asks for the hour meter/km on preventive maintenance; when checked, it also asks on corrective maintenance, whenever the machine has an hour meter in its record. It applies per farm, and takes effect after switching farms or logging in to the portal again. |
| Maintenance work order | Maintenance W.O. cost type: Manual or Calculated automatically. Defines who fills in the Total amount of the maintenance work order: in manual, the user enters it when finishing; in automatic, the system adds up the hours logged, the parts issued from inventory and the parts purchased for the order. It applies to the whole company. |
| Fueling | Generate a fueling number, show the ticket field, skip the hour meter/km check and require an employee. |
| Requisition | Do not allow filling in a requisition without a product. |
| Default reports | Which report the Print button produces on each screen: harvest load ticket, outbound, stand-alone, work order, transfer between locations and field W.O. inventory issue. |
Two fields may appear without a translation, showing the internal key instead of the name
(!pt: bloquear_totan, in the W.O. Inventory block, and
!pt: relatorio_padrao_coliteras, in Default reports, which is the default report for bale
collection). It is a label issue, not a functional one: if you do not use these features, ignore them.
🌱 Crop Settings tab
This is where you define what the technician measures in the field, per crop. On the left, the list of the company's crops (Code and Description); choose one and the form appears on the right. Each crop has its own settings: soybeans do not need the same measurements as cotton.
At the top: Default plants/meter, Manual point and Show 'Number of plants' field for phenology. Below comes the list of measurements, each one with a checkbox to turn it on:
Height · Number of Nodes · Distance between Nodes · STAND · Number of Stems · Number of Pods · First Pod Height · Grains per Pod · No. of squares · No. of Small Bolls · No. of Medium Bolls · No. of Large Bolls · Ht. 1st to 5th node · No. of Bolls Pos. 1 to 5 · Rotten Boll · Open boll · Plants/meter · No. of Bolls · Boll weevil.
Once a measurement is on, its settings open, always the same ones:
| Field | Description |
|---|---|
| Occurrence | How often the measurement is requested: First point, Every point, Fixed interval or Specific points. |
| Every (interval) | Only appears with Fixed interval: every how many points to measure. |
| Points (separate with ,) | Only appears with Specific points: at which points
to measure, for example 1,5,10. |
| Set by Days after Planting | When checked, the Minimum Days After Planting and Maximum fields open: the measurement is only requested within that window of the crop. This is how you ask for plant height only between 30 and 60 days, for example. |
| Optional | The technician can leave it blank and close the point anyway. |
| Per meter (1) | The measurement is recorded per meter, not per plant. |
| Show in details (APP) | On some measurements: shows the value on the app's details screen. |
When you are done with the crop, click Save Crop Settings. The button saves the crop that is open: each one is saved separately.
📧 Automatic sending tab
This is e-mail scheduling: the rain report that reaches the manager at 7 a.m., the list of work orders by sector that goes out every morning, the alert for fields without scouting. The list at the top shows what is already scheduled, with Type, Category, Subject, Report, Hour, Minute, E-mails, Active and Last immediate send date.
| Field | Description |
|---|---|
| Type | Required. Send report by E-mail (the common case), E-mail alert, Base for immediate sending or Immediate E-mail sending. |
| Hour · Minute | What time the sending fires. |
| Email (recipients) | Who it goes to. Separate several with commas. |
| E-mail (blind copy) | Blind copy, same rule. |
| Email Subject · E-mail body | What the recipient reads before opening the attachment. The subject is what identifies the sending in the list, so make it count: "Rain on the Last day - EMERSON" says more than "Report". |
| Active | Uncheck to suspend the sending without deleting the schedule. |
| Send only new records | Sends only what came in since the last sending. |
| Send only 1 per day | Avoids repeats on the same day. |
| Every day · days of the week | Checking Every day checks all seven days at once; uncheck the ones you do not want. |
| Report | Required. Which report is attached. |
| Fixed parameters (name) · (value) | Fixes a report filter for the sending: this is how one report becomes one e-mail per technician or per sector. |
| Category | Common for scheduled sending. The others are event triggers: order for approval, approved, rejected; purchase order for approval, approved, rejected; maintenance plan generated. If you choose one of them, the day-of-week schedule disappears: the event is what drives it. |
| Notes | Internal note about the schedule. |
The buttons are Save, Cancel, Delete, New and Clear last sending; the last one resets the last-sending marker, so that the next run sends everything again (useful when the e-mail got lost or the only new records option blocked the sending).
- The screens speak the farm's language: field, block, plot, whatever it is
- The system requires what management wants required at the right moment, and stays out of the way otherwise
- Each crop asks in the field only for the measurements that make sense for it
- The report reaches the decision-maker's e-mail without anyone having to remember to send it
❓ Frequently asked questions
How do I make the system call a "block" a "field"?
On the General company settings tab, in the Pest Scouting block, type the name you want in Display name for 'Quadra' and save. The same goes for variety and sector. It is a name change on screen: nothing changes in the data already entered.
Why is the technician being forced to enter a storage location on the work order?
Because the Service Order - Require 'storage location' checkbox is on, either in the W.O. Inventory block on this screen, which applies to the company, or in that user's settings, which apply only to them. Check both places.
The automatic report stopped arriving. What do I check?
Open the Automatic sending tab and check, on the schedule's row: whether Active is checked, whether today's day of the week is checked and what time the sending is scheduled for. If everything is right and it still did not arrive, click Clear last sending and wait for the next run.
Do I need to set up crop by crop?
Yes: each crop has its own settings, and that is on purpose: what is measured in cotton (open boll, boll, boll weevil) is not what is measured in soybeans (stand, pod, grains per pod). Set up first the crops the farm actually plants.
I changed a setting and nothing happened. Why?
Two common causes: you did not click Save (the button is at the top of the tab and applies to the whole tab), or the company/farm selected at the top of the screen is not the one you are using. On the crops tab, the button is Save Crop Settings, and it saves only the crop that is open.