Answers and step-by-step help for your whole operation.

1. 1Open Create account and enter the requested account information.
2. 2Verify your email if FieldForge asks you to do so, then sign in.
3. 3Open Membership, compare monthly and annual pricing, and start the one-time 14-day Pro trial without a card.
4. 4Add payment through secure billing before the trial ends to continue Pro; otherwise it cancels automatically.

Field tip: Beta accounts marked by the FieldForge owner receive Business-level access without normal feature limits.

1. 1Open Command Center after signing in.
2. 2Review equipment, livestock, inventory, work-order, and readiness cards for items that need attention.
3. 3Check current conditions, the forecast, and U.S. severe-weather alerts before scheduling outdoor work.
4. 4Select a reminder or record to open the related feature and complete the next action.

Field tip: The Command Center becomes more useful as equipment hours, due dates, feed minimums, breeding dates, and work orders are kept current.

1. 1Complete Guided Setup and select every operation type and priority that applies to you. FieldForge uses those choices to recommend your navigation, Command Center cards, and quick actions.
2. 2Open Settings and find My platform view.
3. 3Choose Automatic for my operation to keep recommendations synchronized with Guided Setup, or choose My custom view for direct control.
4. 4In a custom view, select features to add them, clear features you do not use, and use the arrow controls to arrange the sidebar order.
5. 5Save the platform view. Use All tools in the sidebar whenever you need to temporarily reveal the complete feature catalog.

Field tip: Hiding a feature only removes it from your focused navigation. It does not delete records, cancel membership access, or stop you from restoring the feature later.

1. 1Open the Install page on the device where you want FieldForge.
2. 2For the installable web app, use the browser’s Install or Add to Home Screen option.
3. 3For Android beta distribution, download the APK and approve installation from this trusted source when Android asks.
4. 4Sign in with the same FieldForge account to access your farm records across devices.

Field tip: Keep the app and browser current for the best GPS, microphone, camera, and offline support.

1. 1Find Theme near the top of the FieldForge sidebar.
2. 2Choose Light for a bright background, Dark for reduced brightness, or System to follow the device’s current appearance setting.
3. 3Continue using FieldForge normally. The selected appearance applies across supported signed-in screens on that device.
4. 4Return to the same Theme menu whenever you want to change it again.

Field tip: Appearance is separate from My platform view. Theme changes colors; the platform view controls which features appear and in what order.

1. 1Install FieldForge before going into a low-service area and sign in while connected.
2. 2FieldForge automatically refreshes its complete farm-record copy. In Beta Readiness, choose Refresh offline access before an important trip into a dead zone.
3. 3Open records, scan saved tags, and add, edit, delete, photograph, or attach files normally. The top banner shows how many changes are waiting.
4. 4When service returns, FieldForge replays changes in order. Leave the app open briefly or choose Sync now in the banner.
5. 5If a change needs attention, sign in again and use Sync now. FieldForge keeps the unsynced copy on this device until it succeeds.

Field tip: Live weather, advanced cloud AI, payments, and connecting or refreshing third-party accounts require internet. Saved maps, records, the built-in offline advisor, and scanner record lookup remain available.

1. 1Open Equipment and select Add equipment.
2. 2Enter the name, type, manufacturer, model number, year, serial number or VIN, hours or mileage, condition, status, value, and location that you know.
3. 3Save the record, then add available photos, manuals, receipts, notes, and documents.
4. 4Open the equipment detail later to update hours, review history, schedule maintenance, or link work orders.

Field tip: Accurate current hours or mileage are essential for useful maintenance reminders and Forge Intelligence recommendations.

1. 1Open Maintenance or choose Maintenance from an equipment record.
2. 2Create a maintenance item, choose the related machine, and select a service type from the grouped menu. Choose Other service type only when the provided list does not describe the work.
3. 3Complete the service-specific fields that appear. For example, an Engine Oil & Filter Change asks for oil specification, quantity, filter, and old-oil condition, while Engine Oil Top-Off records only what was added and why the level was low.
4. 4Set the priority, due date or meter interval, status, and notes. When work is performed, add completion date, updated meter, labor, parts, cost, test results, and the tailored repair details.
5. 5Save the completed service so the equipment timeline and reports stay current.

Field tip: Use Work Orders when a repair needs assignment, a checklist, or progress tracking across several people.

1. 1Open Inventory and select Add item.
2. 2Enter the item name and choose a category from the grouped menu. Select Other category and type a custom category when none of the standard choices fit.
3. 3Enter quantity, unit, unit cost, minimum level, supplier, storage location, SKU, manufacturer part number, and barcode when available.
4. 4Update the item when stock is purchased, consumed, reserved, transferred, or corrected.
5. 5Inventory automatically sorts and groups products by category. Review each group and its low-stock warnings from Inventory or the Command Center before scheduled work.

Field tip: Consistent units—such as gallons, pounds, bags, or each—make costs and low-stock warnings easier to trust.

1. 1Open Livestock and choose Animal Inventory.
2. 2Add an animal and choose its species. The list includes common livestock, equine, poultry, camelids, cervids, ratites, aquaculture, reptiles, amphibians, and farmed exotic species; choose Other and type a custom species when needed.
3. 3Save the animal before adding feed, breeding, growth, measurements, or health records.
4. 4Choose View full read-only profile on any animal card to review every saved identity, management, lineage, traceability, growth, acquisition, disposition, and notes field without entering edit mode.
5. 5Update location and status when the animal moves, is sold, is culled, or otherwise leaves the active herd.

Field tip: A unique tag or name prevents feed, breeding, weight, and treatment history from being attached to the wrong animal.

1. 1Open Livestock and select Feed.
2. 2Add each feed item with its quantity, unit, cost, supplier, storage location, and low-stock minimum.
3. 3Use Record feed movement to log a purchase, feeding, transfer, adjustment, or loss.
4. 4Link consumption to an animal or group when possible and review the remaining quantity and cost history.

Field tip: Record feed at the time it is used so the Command Center and Forge Intelligence see the current supply.

1. 1Add the female animal to Animal Inventory, then open the Breeding tab.
2. 2Create a breeding record and select the dam, sire or service method, breeding date, status, and notes.
3. 3Update the record with pregnancy-check results and the expected birth date.
4. 4After birth, record the outcome and add the offspring to Animal Inventory with the correct sire and dam.

Field tip: Expected dates drive breeding-window reminders and Farm Pulse readiness signals.

1. 1Open Livestock and select Growth.
2. 2Choose the animal, enter the measured weight, unit, date, method, and useful notes.
3. 3Save each new weighing as a separate record instead of replacing the prior result.
4. 4Review the animal’s growth history for unexpected gain, loss, or performance changes.

Field tip: Use the same scale and weighing conditions when practical to reduce misleading day-to-day variation.

1. 1Open Livestock and select Measurements.
2. 2Choose the animal and measurement date.
3. 3Enter the available body measurements, units, body-condition information, and notes.
4. 4Save the record and compare it with earlier measurements when evaluating growth or health.

1. 1Open Livestock and select Health & Vaccinations.
2. 2Choose the animal and event type, then enter the date, condition or vaccine, product, dose, route, provider, and notes.
3. 3Enter the next due date and any meat or milk withdrawal date when they apply.
4. 4Save supporting documents or veterinary notes and review upcoming due items from the Command Center.

Field tip: FieldForge can organize observations and decision steps, but urgent or uncertain medical cases still require a qualified veterinarian.

1. 1Open Crops & Planting and create a crop plan for the field or production area.
2. 2Enter the crop, variety, acreage, planting window, seed rate, projected harvest, projected yield, and notes.
3. 3Select inventory inputs carefully when recording planting or crop work; saved usage can deduct seed and supplies atomically.
4. 4Add scouting, spray, fertilizer, harvest, yield, and cost information as the season progresses.

Field tip: Check inventory units and quantities before saving an input deduction because the crop record and stock change are committed together.

1. 1Open Farm Operations and choose the activity type.
2. 2Enter the date, field or area, equipment, operator, acreage or quantity, inputs, weather notes, cost, and outcome that apply.
3. 3For grazing, record the herd, paddock, move date, exit date, and intended rest period.
4. 4Save the activity so it appears in Farm Timeline, reports, and related equipment or land history.

1. 1Open Farm Map. Use the Current Farm Map selector to open an existing map, or choose New map and name another farm, tract, leased property, or operating area. Every map keeps its own assets, address, and satellite center.
2. 2Use Assigned equipment and Assigned livestock to connect existing records to the selected map. One record can be assigned to several maps, and Remove only removes the map connection—it never deletes the equipment or animal. You can also choose Farm Maps while adding or editing an equipment or animal record.
3. 3If satellite imagery is not centered for the selected map, enter its address or choose Use this device location once; this map-level starting point does not require every asset to have GPS coordinates.
4. 4Select Add map asset.
5. 5For a road you intend to mow, choose Draw mowing road, or select Road, Farm lane, or Mowing road as the asset type. Tap points along its centerline directly over Satellite view, finish the road, and add it to the map. The saved line remains visible on the satellite imagery and is automatically included in Tractor GPS.
6. 6Enter a name and type, then choose a map symbol, rectangle, or custom boundary; the Center, North/front, South/front, South/rear, and North/rear GPS coordinate pairs are optional.
7. 7Place the new item on the map, drag it into position, use the omni-directional position pad for exact horizontal, vertical, or diagonal movement, set its map rotation, adjust rectangular assets independently on the X and Y axes, resize it, rename it at any time, or move individual custom-boundary points. In Satellite view, a positioned asset saves an exact GPS anchor so it stays on the same ground location while you pan or zoom.
8. 8Use the Labels menu above the map. Numbers is the clean default and matches every item to the numbered legend; Names shows full names on the map, and Hidden removes labels.
9. 9Save the layout and repeat for fields, barns, buildings, fences, gates, lanes, water, trees, equipment areas, and other infrastructure.
10. 10Choose Print map for a clean sheet of the currently selected map, Download PNG for a high-resolution image, or Use in Tractor GPS to prepare operator-reviewed work areas, reference paths, and buffered no-mow zones from its saved GPS coordinates. Rename, make default, switch, or delete maps from the controls above the selector.

Field tip: Use Custom boundary for irregular fields and property lines. Existing single GPS coordinates automatically remain available as the Center point. In Satellite view, drag the background or use the arrow pad to pan, use + and − to change the scale, and use Fit to return to the complete tract. Assets are projected from the fitted base view, so their position, width, height, map rotation, and X/Y angle remain in proportion as satellite zoom changes; zooming never overwrites the saved base dimensions. Visual assets can be rotated, resized, and angled independently on the X and Y axes in either view; Reset axes returns both axis angles to zero without changing the asset’s map rotation. Exact GPS boundaries use their saved corners for real-world size and angle, so FieldForge does not rotate or resize them a second time. If one corner is far outside the others, it is temporarily excluded and a review warning identifies the asset instead of allowing one typo to ruin the online or printed map. Every asset type uses a distinct static, realistic transparent cutout so structures and infrastructure remain easy to recognize without a square image background.

1. 1Open Tractor GPS outdoors on the phone or tablet you will use in the cab.
2. 2Under Farm Map → Tractor GPS, choose a GPS-anchored map and set the clearance around structures. Review the green work areas, lime custom mowing roads, blue mapped paths, and red no-mow zones before operating.
3. 3For a separate tractor display, download GeoJSON, KML, or GPX according to the manufacturer’s supported USB or cloud import workflow. Inspect every imported path and exclusion zone on that display before moving the tractor.
4. 4Enter the implement width, choose the satellite map, and allow precise location when you start the session.
5. 5Set the A point, drive a straight reference pass, set the B point, and use the parallel guidance lines and cross-track correction for following passes.
6. 6Stop and save the session, then review distance, estimated area, overlap, route, and GeoJSON export.

Field tip: Phone GPS accuracy varies. For repeatable sub-meter or inch-level work, connect compatible external GNSS or RTK equipment and follow its calibration instructions. Imported maps are guidance references—not autonomous steering or obstacle detection—and cannot include people, vehicles, temporary hazards, or unmapped objects.

1. 1Open Work Orders and select New work order.
2. 2Enter the title, description, priority, due date, status, related equipment, assignee, estimated cost, and checklist.
3. 3Update status and checklist items as the job moves from Open to In Progress and Completed.
4. 4Add notes, actual cost, parts, and completion details so the permanent history explains what happened.

1. 1Open Settings and locate the team or beta-access controls available to your account.
2. 2Invite the employee using the correct email and assign the minimum role needed for that person’s work.
3. 3Use farm and assignment fields on supported records to keep jobs and data associated with the correct operation.
4. 4Remove access promptly when a team member no longer needs the farm’s records.

Field tip: Never share one person’s password. Give every team member an individual account and appropriate role.

1. 1Open Farm Accounting and choose whether the entry is income or an expense.
2. 2Enter the date, amount, category, enterprise, vendor or customer, description, payment status, and tax-deductible flag.
3. 3Link the entry to its operational context when a field, order, work item, or other record is available.
4. 4Review summaries and export the records for your bookkeeper or tax professional.

Field tip: FieldForge organizes operational records; confirm tax classifications with a qualified accounting professional.

1. 1Open Orders & Commerce, then choose Import product inventory to create draft products from existing FieldForge Inventory or upload a supported product CSV. Review imported names, SKUs, starting prices, and inventory links before publishing.
2. 2Use Products to add or edit names, prices, descriptions, inventory links, tax settings, published status, and cover images. Every save has duplicate-submit protection, so one save creates one product.
3. 3For a haunted attraction, holiday event, farm tour, orchard day, or other admission, choose Event ticket / admission as the product type. Enter a product name for the admission being sold and a separate event name that FieldForge will print on every pass. Then enter the first start and optional end time, add any other selectable dates, enter the location, and publish it.
4. 4Open Waivers to update the default waiver template used for new ticket products. You can still customize the wording for an individual event or restore the current default from its product editor. Existing events and signed records are never silently rewritten. FieldForge provides a starting template, not legal advice; have qualified local counsel review it for the property, activity, state, insurance, and minor-participant rules.
5. 5Use Remove on a product when it is no longer sold. FieldForge removes it from the catalog while keeping past receipts, refund details, and inventory history.
6. 6Open Online store to choose a store name and web address, contact details, tax rate, fulfillment choices, fee, instructions, and color. Email is available for digital delivery and never receives a delivery or shipping fee.
7. 7Share the store link. A ticket buyer chooses the day the pass is valid, reads the exact event waiver, checks acceptance, and types a legal signature before FieldForge will reserve the order or open payment. Point-of-sale ticket sales require the same staff-assisted review and signature.
8. 8Before merchant verification, customers submit unpaid order requests; connect and verify the farm’s own Stripe account to accept card payments directly into that merchant account.
9. 9Customer stock is reserved atomically. Cancel an unpaid online order to release its inventory; incomplete Stripe checkouts release inventory when they expire.
10. 10Use Point of sale for in-person sales and Orders to manage both register and online fulfillment, payments, refunds, accounting, and status. Paid ticket orders issue one unique QR pass per admission automatically.
11. 11Open Tickets & check-in and choose Live scan to point the camera at the guest's QR code. A successful scan checks the pass in immediately; QR image reads and manually entered TKT codes remain available. FieldForge prevents a second entry, shows prior check-in status, and lets an authorized operator undo an accidental check-in.
12. 12Open any issued ticket to print or save the pass. Choose Email ticket to open a ready-to-send message addressed to the purchaser with the secure ticket link.
13. 13Open Waivers to search by signer, email, event, location, or order number. Open a signed record to view its exact preserved language, valid event day, signature, acceptance time, covered admissions, and verification hash, then print it, save it as PDF, or download a text copy.

1. 1Open Farm Timeline to see activity collected from connected FieldForge records.
2. 2Filter or scan by date, source, and activity type to reconstruct what happened across the farm.
3. 3Open a source record when you need its complete details.
4. 4Add a manual timeline event for important context that does not belong to another FieldForge module.

1. 1Open Reports & Export and select the reporting view you need.
2. 2Review the Financial overview, Readiness snapshot, maintenance, livestock, inventory, or activity information shown.
3. 3Correct incomplete source records before relying on the totals or due-item counts.
4. 4Use the appropriate export card when you need a portable file or offline analysis.

1. 1Open Reports & Export and choose the import or export card for the record type you need.
2. 2For imports, download or follow the expected CSV field layout, preserve the header row, and use one record per row.
3. 3Import a small test file first, review the created records, then import the remaining validated data.
4. 4For backups, create the complete portable export and store it in a secure location controlled by the farm owner.

Field tip: Export formats include supported CSV and JSON records, GeoJSON for GPS data, and complete account portability data.

1. 1Open Forge Intelligence and describe the outcome you need, including the machine, animal, field, symptoms, measurements, timing, and what you already tried.
2. 2Read the evidence, safety checks, decision steps, and follow-up questions. Answer in the same conversation so context is retained.
3. 3When you want a record changed, say exactly what to create or update—for example, “Create the high-priority work order due Friday.”
4. 4Review the confirmation and open the resulting FieldForge record to verify dates, assignment, quantities, and notes.

Field tip: A strong request includes identity, condition, measurements, timeline, desired result, and constraints. Start a New conversation when changing to an unrelated problem.

1. 1Open Forge Intelligence in a current Chrome or Edge browser and select Start live voice conversation.
2. 2Allow microphone access for fieldforge.farm when the browser asks, then wait for “Listening.”
3. 3State the problem or command clearly. Forge Intelligence transcribes it, completes the request, speaks the answer, and listens for your follow-up.
4. 4Say the exact record action when needed, listen for the confirmation, and select End voice conversation when finished.

Field tip: Voice uses the same Farm Pulse, troubleshooting, and action tools as text. Move away from loud engines when giving tags, measurements, dates, chemical names, or part numbers.

1. 1Open Forge Intelligence and select Dictate message.
2. 2Allow microphone access if asked and speak one complete question or command.
3. 3Select Stop dictation when necessary, then review and correct the transcribed text in the message box.
4. 4Select Send. Use Dictate message again for another one-time message.

Field tip: Use dictation when you want voice input but prefer to read the answer instead of maintaining a live spoken conversation.

1. 1Ask Forge Intelligence to “Run Farm Pulse” or to review a specific area such as maintenance, herd health, feed, breeding, inventory, or fieldwork readiness.
2. 2Review which records were checked, what evidence was found, and why each item received its priority.
3. 3Correct missing or stale source data when a finding is based on incomplete records.
4. 4Request the desired task, work order, maintenance, livestock, inventory, crop, or operations action and verify the success confirmation.

1. 1Open Integrations and read the status shown on each provider card.
2. 2Live means the service is available; Connect means your farm must authorize an account; Owner setup or Provider approval explains the remaining requirement.
3. 3For QuickBooks, select Connect QuickBooks, approve the company connection, return to FieldForge, and select Import from QuickBooks.
4. 4Review the last-check or last-sync result and disconnect a provider when the farm no longer wants it authorized.

Field tip: Never paste provider passwords or secret keys into Forge Intelligence chat. Integration secrets belong only in approved secure configuration fields.

1. 1Create or join a team workspace in Farm Operations, then ask a team manager to enter your employee name, job title, and employee number.
2. 2Open Payroll & Time, enter the work location and an optional clock-in note, then select Clock in.
3. 3Leave the page open or return later; the open shift remains active until you select Clock out.
4. 4Before clocking out, enter unpaid break minutes and an optional completion note, then select Clock out.
5. 5A manager opens Team Calendar, reviews the completed shift, and selects Approve shift. Approved native punches become payroll ready in the Business payroll review.

Field tip: Correct a disputed punch with a manager before payroll handoff. FieldForge does not infer breaks, overtime rules, taxes, or final pay.

1. 1Open Team Calendar and find Request time off.
2. 2Choose the time-off type, first day, last day, and an optional note that may be visible to the team after approval.
3. 3Select Send request. The request remains Pending until a team manager approves or denies it.
4. 4Managers use Manager approvals on the same page to approve or deny pending requests.
5. 5Approved dates appear as OOO on the shared calendar and create an automatic pinned OOO notice in Team Communication on each affected day.
6. 6The employee can cancel a pending or approved request from the request history when plans change.

Field tip: Use the team note only for information coworkers should see. Keep medical or sensitive personal details out of the shared request.

1. 1Open Team Calendar and use the arrows or Today button to choose a month.
2. 2Select an event type, add a title, date range, optional times and location, then assign it to one person or the whole team.
3. 3Select Add to team calendar. The event appears in green; existing Farm Operations tasks appear in blue and approved OOO dates appear in amber.
4. 4Open Manage calendar events to review or remove an event you created. Team managers can remove any team event.
5. 5Check the pinned OOO summary before assigning work, and open Team Communication for the day’s automatic availability notice.

1. 1Sign in to the farm’s Deputy installation as an administrator and copy its full installation address, such as yourfarm.us.deputy.com.
2. 2Follow Deputy’s permanent-token instructions to create a dedicated API client. Use a dedicated Deputy user with the minimum permissions practical for time-entry review, and copy the token when Deputy displays it.
3. 3In FieldForge, open Integrations, find Deputy, select Connect Deputy, enter the installation URL and permanent access token, then select Verify & connect.
4. 4After the card shows Connected, select Import time entries. FieldForge reads the latest 60 days and records the provider entry ID so later imports update the same records instead of duplicating them.
5. 5Open Payroll & Time to review employees, clock-in and clock-out times, breaks, regular hours, approval state, and payroll readiness before exporting.

Field tip: FieldForge uses the Deputy token only for read requests and stores it encrypted. Disconnect in FieldForge and revoke the token in Deputy when access is no longer needed.

1. 1Sign in to Homebase with an account that can manage API access, open API Settings, and request a read-only API key.
2. 2Wait for Homebase to approve the request. FieldForge cannot issue the Homebase key or bypass Homebase approval.
3. 3In FieldForge, open Integrations, find Homebase, select Connect Homebase, paste the approved read-only key, and select Verify & connect.
4. 4After the card shows Connected, select Import time entries. FieldForge reads authorized locations and imports their recent timecards without changing the source records.
5. 5Open Payroll & Time to review hours, overtime, unpaid breaks, location, role, and approval status before creating a payroll handoff file.

Field tip: Treat the Homebase API key like a password. Disconnect it in FieldForge and revoke it in Homebase if it is exposed or no longer needed.

1. 1Connect Deputy or Homebase from Integrations and complete an Import time entries action first.
2. 2Open Payroll & Time and select the 14-, 30-, 60-, 90-day, or one-year review window.
3. 3Compare employee identity, work date, clock-in and clock-out, regular hours, overtime, breaks, role, location, approval, and payroll-ready status with the source provider.
4. 4Correct disputed, incomplete, open, or unapproved time in the source system, then return to Integrations and import again.
5. 5Select Download payroll review CSV. Review employee and payroll IDs before uploading or reformatting the file for ADP, Gusto, Paychex, an accountant, or another payroll system.

Field tip: The CSV is a review and handoff file, not an automatic payroll submission. Your payroll provider’s current import template, pay rules, tax settings, and approval process remain authoritative.

1. 1Choose Google Drive, Microsoft OneDrive, or Dropbox on Integrations. Each provider is a separate connection and can be disconnected independently.
2. 2Select Connect, sign in on the provider's own page, review the requested file permission, and approve it. Google access is limited to files FieldForge creates; OneDrive uses its FieldForge application folder; Dropbox uses a dedicated app folder.
3. 3Return to Integrations and select Save backup now. FieldForge creates a dated complete portable JSON backup and uploads it directly to the authorized account.
4. 4Confirm the Last activity time. Periodically download and test a backup through Reports & Export as an additional recovery check.
5. 5Disconnect the provider in FieldForge and revoke FieldForge in the provider's account-security page when access is no longer needed.

Field tip: Cloud backup requires an internet connection. FieldForge encrypts refresh tokens server-side and never asks for a Google, Microsoft, or Dropbox password.

1. 1Choose Google Calendar & Gmail or Outlook Calendar & Mail. The connection requests calendar read access, permission to send mail, basic account identity, and offline renewal—never inbox-reading permission.
2. 2Select Connect and approve the permissions on Google or Microsoft. Each member connects only the account they are authorized to use.
3. 3Select Import calendar to copy the coming year and previous 30 days of primary-calendar events into the current default FieldForge Team Calendar. Re-importing updates the same provider events instead of duplicating them.
4. 4Optionally select Send test to myself and confirm the prompt. FieldForge sends one plain connection-test message to the verified email address on the connected account.
5. 5Open Team Calendar to review the imported events. Disconnect the provider when calendar import or member-initiated sending is no longer needed.

Field tip: FieldForge does not read Gmail or Outlook message bodies. Sending is limited to user-initiated FieldForge messages under the provider permission shown at consent.

1. 1Select Connect Xero, sign in to Xero, choose the intended organization, review the read-only invoice, bank-transaction, and settings scopes, and approve access.
2. 2Return to Integrations and select Import from Xero. FieldForge refreshes the short-lived access token securely and updates existing provider records by their Xero identifiers.
3. 3Open Farm Accounting and review imported income and expense records, contacts, payment state, dates, and source labels.
4. 4Correct accounting details in Xero, then import again. FieldForge does not edit invoices, bank transactions, payments, or account settings in Xero.
5. 5Disconnect Xero when access is no longer needed. Previously imported records remain available for audit and export.

Field tip: Xero refresh tokens rotate. FieldForge encrypts and replaces them server-side after every refresh so members never handle provider tokens.

1. 1Confirm the ADP card says Provider approval. Individual FieldForge members cannot configure this connection until ADP approves the FieldForge application.
2. 2The FieldForge owner must apply through ADP Marketplace or the applicable ADP developer program and document the worker, organization, and time-data use case with the minimum required read scopes.
3. 3After approval, obtain the ADP-issued client ID, client secret, API certificate, and private key. Store every credential only in the protected production secret manager—never in browser code, chat, screenshots, or Help Center content.
4. 4Register the exact fieldforge.farm callback or subscription URLs required by the approved ADP flow, then validate certificate authentication, token renewal, customer authorization, account isolation, and error handling in ADP’s approved test environment.
5. 5Complete ADP’s review and production promotion. Only after production credentials and an end-to-end test succeed should FieldForge change the ADP card from Provider approval to Ready to connect.

Field tip: ADP access is external to a normal farm account. Do not paste an ADP password, certificate, private key, or client secret into the existing Deputy/Homebase connection forms.

1. 1Confirm the Gusto card says Provider approval. A regular Gusto customer cannot create a direct production API connection for FieldForge.
2. 2The FieldForge owner must create a Gusto Developer Portal organization, submit Production Pre-Approval, create a demo application, and register an exact FieldForge callback URL without wildcards or URL fragments.
3. 3Use the demo client ID and secret only with api.gusto-demo.com. Build OAuth with state verification, one company per grant, encrypted access and refresh tokens, token rotation, and only the employee and time scopes Gusto approves.
4. 4Complete the Gusto Partner Checklist and QA review. Gusto issues production credentials only after the integration and production use case are approved.
5. 5After the production callback and sync pass an end-to-end test, enable Connect Gusto. A primary or full-access Gusto administrator must authorize each company separately.

Field tip: Do not use demo credentials against Gusto production or present the integration as live before Gusto issues production keys.

1. 1Confirm the Paychex card says Provider approval. FieldForge cannot create Paychex credentials on behalf of an individual member.
2. 2The FieldForge owner must submit the Paychex partnership questionnaire, document the payroll or workforce-data use case, and wait for Paychex to create a partner application if the request is approved.
3. 3When Paychex supplies the application client ID and secret, place them in protected server-side production configuration and implement the OAuth client-credentials token flow without exposing either value to the browser.
4. 4Validate the approved company, worker, and time endpoints; scope every request to the authorizing customer; handle the documented short token lifetime; and keep imports idempotent using Paychex record IDs.
5. 5Enable the member connection only after Paychex authorizes production use and a real test customer completes the provider’s required consent or access process.

Field tip: A successful application token does not by itself prove that a specific Paychex customer has granted access. Test both application authentication and customer data authorization.

1. 1On the Integrations card, check Platform mode. If it says Sandbox testing, do not connect a live company; the FieldForge owner must first install the Intuit production client ID and secret in the protected production environment.
2. 2In the Intuit Developer Portal, register https://fieldforge.farm/api/integrations/quickbooks/callback as the exact production redirect URI and complete Intuit’s production requirements.
3. 3After Platform mode shows Production, a QuickBooks company administrator can select Connect QuickBooks, sign in to Intuit, select the intended company, review the accounting permission, and approve access.
4. 4Return to Integrations and select Import from QuickBooks. Review the company name, import count, last-check time, and any sync error.
5. 5Open Farm Accounting to inspect imported bills, purchases, invoices, and sales receipts. Disconnect from FieldForge and revoke the app in Intuit when access is no longer required.

Field tip: QuickBooks access and refresh tokens remain server-side and encrypted. Never send Intuit client secrets or member tokens through email, support chat, or Forge Intelligence.

1. 1Check the badge on the John Deere card. Ready to connect — Sandbox means the FieldForge application credentials are protected on the server and the connection is using Deere test endpoints; it does not mean Deere has approved production access.
2. 2Deere must approve at least one requested Operations Center API before the sandbox organization test can finish. When the routes are approved, select Connect John Deere and sign in to the Deere account that can authorize the intended organization.
3. 3Review FieldForge’s read-only organization, equipment, location, field-operation, and work-plan scopes. FieldForge does not request Deere write, delete, file, financial, or user-management scopes.
4. 4In Deere Connections, choose the organization or organizations FieldForge may read and return to FieldForge. The connection is incomplete until at least one organization is selected.
5. 5Select Test sandbox import. Deere machines are upserted into Equipment, each organization receives a separate Farm Map, field boundaries are mapped as fields, equipment is assigned to its map, and field work is added to Farm Timeline without duplicating prior imports.
6. 6Review imported records and any provider-limitation message. A pending or unavailable API is reported separately so one unavailable Deere dataset does not erase successful imports from another.
7. 7After Deere grants production approval, the FieldForge owner changes the protected server environment to production, redeploys, authorizes a real organization, and runs the documented live connection test. Never point the production card at live Deere APIs before approval.

Field tip: OAuth access and refresh tokens remain encrypted server-side. Disconnecting FieldForge preserves imported history; use Deere Connections as well when you want to revoke organization access at Deere.

1. 1The FieldForge owner first creates the Square application, registers https://fieldforge.farm/api/integrations/commerce/square/callback, adds the signed webhook endpoint, and installs the production app credentials in protected server configuration.
2. 2Open Integrations, find Square, and select Connect Square. Sign in to the intended Square seller account and review the merchant-profile, catalog, inventory, and order read permissions.
3. 3After Square returns to FieldForge, select Import from Square. FieldForge imports catalog variations and the latest 60 days of orders without editing Square or requesting customer personal data.
4. 4Open Orders & Commerce to review the imported provider products, sales channel, totals, payment status, and order lines.
5. 5Disconnect when access is no longer needed. FieldForge revokes the Square OAuth token while preserving already imported business records for audit and export.

Field tip: FieldForge never asks a seller to paste a Square personal access token. Seller connections use revocable OAuth authorization.

1. 1The FieldForge owner first creates and releases the Shopify application, sets the app URL and https://fieldforge.farm/api/integrations/commerce/shopify/callback, configures the mandatory compliance webhook endpoint, and installs the protected production credentials.
2. 2Open Integrations, find Shopify, enter the store's permanent myshopify.com domain, and select Connect Shopify.
3. 3A Shopify administrator reviews the product, inventory, and recent-order read permissions and approves the installation.
4. 4Return to FieldForge and select Import from Shopify. FieldForge excludes customer personal data and does not edit products, fulfill orders, or move money.
5. 5Open Orders & Commerce to review imported products and orders. Disconnect only when you intend to uninstall FieldForge from that Shopify store.

Field tip: Use the permanent myshopify.com domain even when the storefront uses a custom public domain.

1. 1Open Membership to review Starter, Pro, and Business access and your current plan.
2. 2Open Settings and select Manage billing.
3. 3Use the Stripe-hosted portal to update payment details, view invoices, change the plan, or cancel renewal.
4. 4Return to FieldForge and refresh the page if the membership badge has not updated yet.

Field tip: FieldForge does not receive or store the raw card number entered in Stripe-hosted checkout.

1. 1Open Settings and locate API access.
2. 2Enter a descriptive key name for the approved system or automation and select Create Key.
3. 3Copy the displayed secret immediately and store it in that system’s encrypted secret manager.
4. 4Revoke the key from Settings when it is exposed, replaced, unused, or no longer authorized.

Field tip: API keys are credentials. Do not place them in screenshots, email, support messages, source code, or Forge Intelligence conversations.

1. 1Open Settings and confirm the signed-in email and account information are correct.
2. 2Under Two-factor authentication, select Set up authenticator and scan the QR code with Google Authenticator, Microsoft Authenticator, 1Password, Authy, or another TOTP app.
3. 3Enter the current six-digit code to finish enrollment. Future sign-ins and protected data requests will require that authenticator after your password.
4. 4Use a unique passphrase with at least 12 characters, keep email access secure, and sign out when leaving a shared device.
5. 5Create a portable export before closing the account if records must be retained elsewhere.
6. 6Use Delete account only when you intend to remove the account and its supported data; read the confirmation carefully before completing it.

Field tip: Keep access to your authenticator device. If it is lost while two-factor authentication is enabled, contact FieldForge support for identity-verified recovery.

1. 1Open Smart Scanner from the sidebar, Quick Add, or Guided Setup. The Quick Record Capture panel is shown first.
2. 2Optionally choose Speak a note and say who or what the record belongs to and what should be recorded. You may also type the note or use the phone keyboard microphone.
3. 3Choose Take photo for one new picture, or choose Choose photos or files to select up to 12 existing images, PDFs, text files, or CSV files at once. FieldForge automatically optimizes large phone photos before reading them.
4. 4For a batch, FieldForge analyzes one selected file at a time so unrelated records are never combined. Confirm and file the current item, retry it, skip it, or cancel the remaining queue; FieldForge then advances automatically and shows a completion summary.
5. 5Forge Intelligence classifies the document, extracts its details, and compares identifiers, names, models, tags, and other facts with your Equipment, Inventory, and Livestock profiles. Voice context helps with destination and intent but never replaces printed facts.
6. 6Check the suggested destination and choose the large Confirm and file button. FieldForge preserves the original, fills only blank fields, and can create a linked maintenance or animal-health entry.
7. 7If you add a voice note after the photo was read, choose Re-read this record with the voice note. If the photo contains an external barcode that is not linked to a FieldForge profile, FieldForge continues with document analysis instead of stopping at the code. Use the advanced section only when you need a live barcode, QR, tag, manual identifier, profile change, or duplicate merge.
8. 8If the scan reveals two profiles for the same item or animal, choose which profile to keep, select Merge duplicate profiles, review the warning, and type MERGE. FieldForge moves linked history and removes the duplicate as one protected action.
9. 9Choose Generate barcode & QR. Enter the printed name, what the code is for, optional details or instructions, a QR destination, and an optional barcode identifier.
10. 10Choose a 2 × 2, 3 × 4, or 4 × 6 inch print size and check the exact preview. Select Print customized QR label to print it or save it as a PDF. The separate download buttons still provide crisp SVG QR and Code 128 files.

Field tip: Keep the page flat, fill the frame, avoid glare, and include all edges. Document and voice contents are treated as untrusted data. Scanner suggestions never change a record, overwrite a populated field, or merge profiles without your explicit confirmation.

1. 1Open Livestock, locate the animal, and choose Stable profile & record barcode.
2. 2Use the automatically assigned animal record barcode for folders, veterinary paperwork, breeding files, stall records, and other internal filing. Each label prints with the animal’s name in small type above the barcode.
3. 3Print one label from the Animal record barcode section, or choose Print all record barcodes in Animal Inventory to create a three-column sheet of labels for every animal.
4. 4Upload or take the animal profile photo and select which identity fields may appear publicly.
5. 5Enter feeding, daily care, critical medical-alert, and emergency-contact information intended for stable staff or responders.
6. 6Enable the public QR, save the stable profile, preview it, and choose Print stable card.
7. 7Disable and save the public QR at any time to make the printed link stop displaying the profile.

Field tip: The animal record barcode never appears on the printed stable profile. Private health history, breeding records, financial values, and internal notes are never included on the public stable profile.

1. 1Add frequently used chemical or treatment products and enter their batch, storage, expiration, REI, PHI, or withdrawal defaults from the label.
2. 2Create a compliance record for each application, treatment, inspection, certificate, permit, training, or biosecurity event.
3. 3Attach the correct location, product, batch, provider, and important dates; FieldForge shows active restrictions and upcoming expirations.
4. 4Export CSV or print an audit packet when a regulator, certifier, veterinarian, buyer, or farm manager needs the history.

Field tip: Product labels, official regulations, and licensed professional directions remain the authority for regulated work.

1. 1Create or join a farm team from Farm Operations when posts need to be shared with other people.
2. 2Choose Message, Observation, Handoff, or Alert and enter the update by typing or voice dictation.
3. 3Add the field, pasture, shop, barn, row, or other location, and optionally link the related FieldForge record.
4. 4Review the shared log at each shift change and convert required work into a task or work order.

1. 1Enter the farm name and select operation types. Each selected type opens its own detailed profile for grains and row crops, livestock, exotic animals, equine, dairy, poultry, hay and forage, fruit and nut trees, berries and bushes, vegetables and herbs, homestead, or custom services. Use Add custom choice for any unlisted crop, plant, or species.
2. 2Complete setup so FieldForge and Forge Intelligence can use that operating context.
3. 3Confirm Complete Offline Access has refreshed before going into a dead zone. FieldForge refreshes it automatically and also provides a manual refresh button.
4. 4Enable device alerts if desired, install FieldForge, and review the production-services snapshot for owner or provider setup that remains.