# Orijin - product documentation Generated from docs-site/src/content/docs. Canonical HTML: https://docs.orijin.io A farm is called a Supplier. A purchase from a farmer is a Collection (also called a lot). --- # What is Orijin > Orijin is the record of where your coffee or cocoa actually came from - collected in the field, checked against satellite, and carried through every lot you sell. Source: https://docs.orijin.io/start-here/what-is-orijin/ Orijin is where a producer organisation keeps the record of its **first mile**: who the farmers are, where their land is, what was bought from them, what was paid, and what can be proven about all of it. That record used to live in notebooks, in a warehouse ledger, and in three different spreadsheets that disagreed with each other. When a buyer asks for proof - a deforestation check, a farmer list, a due-diligence pack - the answer takes a week of reconciliation. Orijin is the attempt to make that answer take a minute, because the data was captured correctly the first time. ## The two halves Orijin is two applications sharing one set of data. **The Field App** runs on phones, in villages, usually with no signal. Field officers use it to register farmers, walk plot boundaries, run surveys and record purchases at the point of collection. It works offline and syncs when it next finds a connection. **The Dashboard** is the web application your office uses. It's where the field data lands, where you check and correct it, run compliance checks, manage processing and trades, and produce the reports that leave the building. Most of this documentation is about the dashboard, because that's where the decisions get made. ## What it's for Four things, in the order most organisations need them: **Know your supply base.** Every farmer and every farm registered once, with a short code, so "Kwizera John" isn't three different people across three seasons. Plots mapped, so their land is a boundary on a map rather than a village name. **Prove compliance.** Mapped plots can be checked against satellite data for deforestation, which is what EUDR asks of anyone selling into the EU. The result is a due-diligence report you can hand to a buyer. **Trace what you buy and sell.** A purchase from a farmer is a **Collection**. Collections get combined, processed, bagged and sold. Orijin keeps that chain connected, so a lot leaving your warehouse can be traced back to the farms it came from. **Pay people, and show that you did.** Payments are recorded against the collection they settle - in cash or through mobile money - and every approval and edit is in the audit log. ## What Orijin is not It is not an accounting system, and it is not a substitute for your ERP. It is the layer underneath both: the primary record of the farms, the purchases and the evidence. It also does not decide anything for you. Deforestation checks return a risk level from satellite analysis; whether that means you buy from that plot is your call, and Orijin records the call you made. ## Next - [How Orijin fits together](/start-here/how-it-fits-together/) - the shape of the system - [Core concepts](/start-here/core-concepts/) - the words, and why a farm is called a Supplier - [Getting access](/start-here/getting-access/) - logging in for the first time --- # How Orijin fits together > Data starts in the field, lands in the dashboard, gets checked against satellite, and leaves as a traced lot or a compliance report. Source: https://docs.orijin.io/start-here/how-it-fits-together/ One path runs through the whole system. Almost everything in Orijin is a step on it. ``` Field App Dashboard Out ───────── ───────── ─── register farmer ──▶ Suppliers & Persons walk plot ──▶ Plots ──▶ satellite check ──▶ EUDR report ──▶ buyer run survey ──▶ Surveys & Field Services record purchase ──▶ Collections ──▶ Processing ──▶ Trades ──▶ Product Story Collections ──▶ Payments ──▶ farmer paid ``` ## 1. The field captures it A field officer opens the Field App, selects or registers a farmer, and records what happened - a new plot boundary walked on foot, a survey answered, a delivery weighed and bought. None of this needs a connection. The phone holds it until it can sync. Because the field is where errors are cheapest to prevent, this is also where Orijin is strictest: a farmer has one record with one short code, and a purchase is attached to that record, not to a name typed from memory. ## 2. The dashboard receives it Synced data appears in the dashboard under **Supply Base** (suppliers, persons, plots) and **Traceability and Production** (collections). The office checks it, fixes what needs fixing, and fills in what the field can't know. Every change is recorded. **Events**, under **Configuration** after **Settings**, shows the log, split into Info, Field App, Warning and Error, so a disagreement about what happened has an answer. ## 3. Compliance runs on top of it A plot with a mapped boundary can be sent for satellite analysis. The result is a deforestation risk level for that specific piece of land, stored against the plot. Once your plots carry results, you can generate an **EUDR due-diligence report** covering a set of suppliers or an entire lot's chain - the farms, their boundaries, the checks, and the ancestry of the lot itself. That report is the artefact your buyer's compliance team actually wants. This is why mapping matters more than it looks. An unmapped plot can't be checked, and an unchecked plot weakens the report. ## 4. Production carries it forward Collections don't stay collections. They're combined, dried, hulled, graded, bagged and eventually sold. **Processing**, **Warehouse** and **Trades** track that, and Orijin keeps the ancestry: a bag leaving the warehouse knows which collections it contains, and therefore which farms. At the end of that chain, a **Product Story** can publish a public, shareable page about a specific lot - which is the same traceability data, pointed outward at a consumer instead of an auditor. ## 5. Money goes back down it Payments are recorded against the collection they settle, so "was this farmer paid for this delivery?" is a question with one answer. Where mobile money is enabled, payment happens through the wallet system and the events are logged alongside everything else. ## The shape of it The value isn't in any one of those steps - other tools do each of them. It's that they share one record. The farm you registered in step 1 is the same farm in the compliance report in step 3 and the payment in step 5, without anyone re-typing it. That's the whole idea, and everything that feels strict about Orijin is in service of it. ## Next - [Core concepts](/start-here/core-concepts/) - the vocabulary this all assumes - [The dashboard](/start-here/the-dashboard/) - where each of these lives in the menu --- # Core concepts > Supplier, Person, Plot, Collection, Lot, Season, Facility - the words Orijin uses, and what each one actually means. Source: https://docs.orijin.io/start-here/core-concepts/ Orijin has about eight words in it. Learn these and the rest of the product explains itself. ## Supplier **A farm.** In the dashboard a farm is shown as a **Supplier**, because from your organisation's point of view that's what it is - the thing you buy from. This trips up nearly everyone at first, so it's worth saying plainly: when this documentation, the menu, or the AI Assistant says "Supplier", it means a farm and the farmer who runs it. There is no separate "Farms" page to go looking for. A supplier has a **short code** - a unique identifier like `REN-0042` - which is how the same farm stays the same farm across seasons, spreadsheets and staff changes. Short codes matter more than names, because names are spelled four ways and shared by cousins. ## Person **A human being.** The farmer, their spouse, a contact person, a field officer. A supplier has a contact person - the farmer. That person exists in their own right under **Persons**, so if the same farmer is connected to two farms, or changes their phone number, there's one place that's true. Phone numbers live on a person's contacts, not on the farm. ## Plot **A piece of land.** A supplier has one or more plots, and a plot is where crops actually grow. A plot becomes useful once it has a **boundary** - a polygon walked in the field or uploaded as a file - or at minimum a GPS point. A plot with a boundary is "mapped", and mapping coverage figures count exactly this. Mapping is the gate for compliance. An unmapped plot cannot be checked for deforestation, which means it cannot appear properly in an EUDR report. ## Collection **A purchase from a farmer.** One delivery: this farmer, this weight, this price, this day. Collections are the atoms of everything downstream. They are also called **lots**, and you'll see both words - a collection *is* a lot, at the point in its life where it has just been bought. ## Lot **A batch of product moving through your operation.** A collection is the first lot. As product is bulked, dried, processed and bagged, new lots are created from old ones, and Orijin records the parentage. That parentage is what "traceability" means in practice: any lot can be walked backwards to the collections inside it, and therefore to the farms. ## Season **A buying period.** Most things you look at - collections, totals, analytics - are filtered by season, because comparing this year's volumes to last year's is most of what anyone wants to know. If a page looks emptier than expected, check which season it's showing. ## Facility **A physical place where product is handled.** A collection point, a washing station, a warehouse, a dry mill. Facilities are what make a supply chain a map rather than a list: this collection was bought *here*, moved *there*, processed *there*. ## Assessment **A check performed on a plot.** In practice this is usually the satellite deforestation analysis - a request goes out, results come back, and the plot carries a risk level. An assessment is evidence, with a date. It is not a permanent property of the land, and re-running it later can give a different answer. ## Certification status **A property of a supplier**, not a separate certificate record. Organic, Fairtrade, in-conversion, none - it's a field on the supplier that you set, in bulk if needed. Orijin deliberately does not model certificates as documents with expiry dates and scans. The status is what gates decisions, so the status is what it stores. ## How they relate ``` Person ──is contact for──▶ Supplier ──has──▶ Plot ──has──▶ Assessment │ │ │ └──has──▶ boundary (polygon or GPS) │ └──sells──▶ Collection (a Lot) ──▶ Processing ──▶ Lot ──▶ Trade │ └──settled by──▶ Payment ``` ## Next - [Getting access](/start-here/getting-access/) - [Add a supplier](/supply-base/add-a-supplier/) - the first thing most people do --- # Getting access > How to get an Orijin login, what your role controls, and what to do when a page you expect is missing. Source: https://docs.orijin.io/start-here/getting-access/ You can't sign yourself up for Orijin. Access is granted by an administrator inside your own organisation. ## Getting a login Ask an administrator at your organisation to add you under **Configuration → Users**. They'll need your email address and will choose your **role**. You'll receive an invitation by email. Follow it to set a password, then sign in at your organisation's Orijin address. If you don't know who your administrator is, your Orijin contact does - see [Get more help](/start-here/get-help/). ## Roles decide what you see Orijin shows you only what your role allows. This is the single most common source of "the documentation mentions a page I don't have". Broadly: - **Field officers** work in the Field App - registering farmers, mapping plots, running surveys, recording collections. - **Office and management roles** work in the dashboard, and see suppliers, collections, analytics and reports. - **Financial roles** additionally see inventory, trades and payment approval. - **Administrators** see configuration, users, reference data and settings. ## Your organisation also decides Beyond your role, whole sections are switched on or off per organisation. An organisation that doesn't buy for the EU market may have compliance features hidden entirely; one that doesn't use mobile money won't see wallets. So if a page in this documentation isn't in your menu, there are three possible reasons, in order of likelihood: 1. Your role doesn't include it. 2. Your organisation doesn't have that module enabled. 3. It's there, but under a group you haven't expanded - try [searching the menu](/start-here/find-a-page/). ## Workspaces After you sign in to the Field App, you **Choose Organisation** if you belong to more than one. If you only belong to one organisation, the app opens it automatically. Then **Choose Workspace** from the same opening screen as login. Open the list, tap the name you need, then **Proceed to dashboard**. The Field App has two workspaces per organisation: the **main** one, where real data goes, and a **test** one for training and trying things out. Data recorded in the test workspace is not your real supply base. If your organisation isn't actively training people, an administrator can [close the test workspace](/organisation/test-workspace/) so nobody uses it by accident. ## Next - [The dashboard](/start-here/the-dashboard/) - what each menu group is for --- # The dashboard > What each group in the left-hand menu is for, and where to find the thing you are looking for. Source: https://docs.orijin.io/start-here/the-dashboard/ Everything in the dashboard hangs off the left-hand menu, grouped by what you're trying to do rather than by what the data is called. ## The groups **Home** - your organisation's summary view. A spinner shows in the middle of the page while Home loads, instead of a blank white screen. **Supply Base** - who you buy from. Suppliers, Persons, the supplier map, and the analytics that describe them (farm summaries, plot dashboard, plot summaries). This is where most people spend their first week. **Sustainability & Monitoring** - Surveys and Field Services: what your field team asks farmers and does with them, plus the analytics over it. **Risk & Compliance** - Risk Assessment and Certification analytics. This is where deforestation results and certification coverage are summarised. Note that you *start* a deforestation check on the plot itself, not here. **Traceability and Production** - the operational chain. Collections (with Analytics under it), **Payments** (Payment Transactions, Prices, and where mobile money is enabled, Wallets, Mobile Money Users, and Mobile Money Events), Processing, Warehouse, Inventory, Trades, and Product Stories. **Organisation** - documents and notes that belong to the organisation as a whole. **Configuration** - administrator territory. Users, reference data (crops, seasons, locations, facilities, certification types and more), Settings, then **Events** (the log of everything that happened), and bulk data import. ## Two things worth knowing early **Farms are called Suppliers.** There is no Farms page. See [Core concepts](/start-here/core-concepts/). **Analytics pages are configurable.** Most of them have a **View** or **Configure sections** control that decides which graphs and report sections appear. Your organisation may have set a default that hides things you'd otherwise expect. If a chart is missing, look there before assuming the data is. ## Finding things The menu has a search box at the top. It matches common alternative names too - typing "farmers" finds Suppliers. See [Find a page](/start-here/find-a-page/). You can also ask the in-dashboard AI Assistant, which can both explain how to do something and answer questions about your actual data. --- # Find a page > Use the menu search to jump to any page, including by the name you would normally call it. Source: https://docs.orijin.io/start-here/find-a-page/ The left-hand menu has a search box at the top. It is the fastest way to get anywhere, and it does something slightly more useful than filtering. ## How to use it Type part of a page name - `surv` finds Surveys - and matching pages appear, **including pages inside groups you haven't expanded**. That's the point: you don't need to know which group something lives in. Click a result to open it. Clear the box to get the full menu back. ## It knows what you call things The search also matches common alternative names. Typing **farmers** finds **Suppliers**, because that's what most people actually call them. This is deliberate - the product's internal vocabulary and your team's vocabulary don't have to match for the menu to be usable. ## On a phone or narrow window The menu is collapsed behind the menu button. Open it first; the same search box is at the top. ## If you still can't find it The page may not be available to you at all. See [Getting access](/start-here/getting-access/) - a page can be hidden by your role or by which modules your organisation has enabled. --- # Get more help > Reach the Orijin team on WhatsApp, report a bug, or ask the in-dashboard assistant. Source: https://docs.orijin.io/start-here/get-help/ Three routes, depending on what you need. ## Talk to a person Open **Help** - the question mark - and choose **Customer support**. Pick your region (**LATAM**, **Africa & Asia**, or **Europe**), then **Chat on WhatsApp** to message the Orijin team directly. The region is pre-selected based on where you're opening the app from, and you can change it. ## Report a bug or request a feature Same **Help** window, **File a report**. Include what you were doing and what you expected - a short code or a lot number makes a report far faster to act on than a screenshot alone. ## Ask the assistant The in-dashboard **AI Assistant** (open **Assistant** in the left menu) is in **beta**. It answers two kinds of question: - **How do I...?** - it walks you through the real steps, using the actual menu and button names. Its answers come from this documentation. - **Data questions** - "how many suppliers are active?", "which farms have unmapped plots?", "totals by collection point this season?" - **Downloads** - ask for a report and use **PDF** or **Excel** on the preview. For collections by collection point, district and season (including which suppliers delivered, kg, and how many times), ask for an Excel — it uses this organisation's own location words (for example **district**) and treats a **collection point** as a facility. Treat it as a preview: answers can be wrong or incomplete. Check important numbers, payments and compliance steps in the dashboard before you act. It won't invent a screen that doesn't exist. If it says it doesn't know, that's a real answer, and worth passing to support. ## Connect Claude, ChatGPT or Cursor You can ask the same organisation questions from the assistant you already use (**Claude**, **ChatGPT**, **Cursor**, or any other MCP-capable client). Access is read-only and limited to your organisation. Your Orijin contact will send a **server URL** and an **API key**. Full setup steps: [Connect your assistant](/for-agents/connect-your-assistant/). --- # Filter by date > Jump to this year, last year, this season, or last season on pages that have a start date and end date. Source: https://docs.orijin.io/start-here/filter-by-date/ Many lists and insight pages let you limit what you see to a date range. Look for **Start date** and **End date**, then **Quick Range** next to them. ## Jump to a common range 1. Open the page you need — for example a survey **Tasks insights** or **Table** tab, Field Services, or Collections. 2. Click **Quick Range**. 3. Choose one of: - **This year** — 1 January of this year through today - **Last year** — 1 January through 31 December of last year - **This season** — your organisation's current season - **Last season** — the season before the current one The start and end dates fill in, and the table or charts update. **This season** and **Last season** only appear if your organisation has seasons set up. ## Pick your own dates You can still set **Start date** and **End date** yourself. Quick Range is only a shortcut. --- # Supply Base > Suppliers, farmers and plots - the foundation everything else in Orijin is built on. Source: https://docs.orijin.io/supply-base/ **Supply Base** is who you buy from. Everything else in Orijin - compliance, traceability, payments - is built on top of it, which means the quality of your supply base sets the ceiling for everything downstream. Remember: [a farm is shown as a **Supplier**](/start-here/core-concepts/#supplier). ## What's in this section **Suppliers** - the farms. Each has a short code, a contact person (the farmer), plots, collections and history. **Persons** - the people. Farmers, contacts, and anyone else recorded by name. A person exists independently of any one farm. **Supplier map** - your whole supply base as points and boundaries on a map. **Analytics** - Farm summaries, Plot dashboard, Plot summaries: coverage, size distribution, mapping progress and the shape of your base. ## The order to do things in 1. **[Add the supplier](/supply-base/add-a-supplier/)** - farm and farmer together, in one short form. 2. **[Add its plots and map them](/supply-base/plots-and-mapping/)** - this is the step that unlocks compliance. An unmapped plot cannot be checked. 3. **[Set certification status](/supply-base/certification-status/)** if it applies to your organisation. 4. Everything else - surveys, collections, payments - now has something to attach to. Most organisations do steps 1 and 2 in the field, on phones, and only correct them in the dashboard. That's the intended shape: capture once, at the source. ## Getting data in at scale If you're starting with an existing farmer list rather than registering one at a time, don't type it in. See [Import data in bulk](/organisation/import-data/) - suppliers, farmers and plot boundaries can all be uploaded, including GeoJSON and KML map files. ## The number that matters **Mapping coverage** - the share of your plots that have a saved boundary or GPS point. It's the leading indicator for whether you'll be able to produce a credible EUDR report when a buyer asks. Track it on the Plot dashboard. --- # Add a supplier > Register a new farm and its farmer in Orijin, from the dashboard or the Field App. Source: https://docs.orijin.io/supply-base/add-a-supplier/ A farm and the farmer who runs it are registered together, in one short form. ## Steps 1. Open **Suppliers** from the left-hand menu, under **Supply Base**. 2. At the top of the page, click **Create New Supplier**. 3. Fill in the farmer's and the farm's details. 4. Save. The new supplier appears in the list. Open it to add plots and map their boundaries - which is the step that actually makes the record useful. ## What to get right the first time **The short code.** This is how the farm stays identifiable forever. If your organisation has a coding scheme, follow it exactly. Codes that drift - `REN-42` here, `REN-042` there - create duplicate farms that take real work to merge later. **The farmer's name, spelled the way it will be spelled again.** Names are the single biggest source of duplicates. Where a national ID or similar identification number exists, record it - it's the only field that reliably distinguishes two people with the same name in the same village. **Location.** Get the administrative hierarchy right (region, district, sub-county or their local equivalents). Analytics, collection-point assignment and regional reporting all key off it. ## Doing it in the field instead Most suppliers are registered in the **Field App**, at the farm, by a field officer - which is better, because the farmer is standing there to confirm the details and the plot can be walked in the same visit. The dashboard form exists for office corrections and for farms added after the fact. ## Doing it in bulk Registering an existing farmer list one at a time is a mistake. See [Import data in bulk](/organisation/import-data/). ## Next - [Add plots and map their boundaries](/supply-base/plots-and-mapping/) - [Set certification status](/supply-base/certification-status/) --- # Plots and mapping > Add plots to a supplier and map their boundaries by drawing, uploading or dropping a GPS point. Source: https://docs.orijin.io/supply-base/plots-and-mapping/ This is the most consequential page in the Supply Base section. A plot without a boundary can't be checked for deforestation, which means it can't appear properly in an EUDR report, which means the farm effectively can't be sold into the EU market with confidence. ## Add a plot 1. Open the supplier from **Suppliers**. 2. Open its **Plots** tab. 3. Click **Create** to open the new-plot form. 4. Fill in the details and save. ## Map its boundary Open the plot menu - the **…** button - and choose one of three options. ### Draw Polygon Draw the boundary directly on the map. Use the **map search bar** to jump to the village or place first, then click the map to add points around the plot. Best for plots you know well, or for correcting a boundary that came back from the field slightly wrong. ### Upload Polygon Upload an existing boundary file. Use this when boundaries were collected with other equipment, or supplied by a cooperative or government dataset. For many plots at once, use [bulk import](/organisation/import-data/) instead - it accepts GeoJSON and KML. ### Add GPS Point Type a latitude and longitude, or drop a pin on the map. A single point is weaker evidence than a boundary - it locates the plot but doesn't describe its shape or area. Use it when a full boundary isn't available, not as the default. :::caution If the plot **already has a polygon**, adding a GPS point will ask you to confirm - because the point **replaces** the boundary. You are trading better evidence for worse. Say no unless you're certain the existing boundary is wrong. ::: ## The supplier house location Separate from plots, a supplier has a house location - where the farmer actually lives, which is often not on the land they farm. In the right-hand panel, next to **Supplier House**, use **Set location** or **Edit location**. ## Overlaps on the map When two plot boundaries cross, the map can colour the overlapping area and label it with the plot names and the overlap percentage. That is **on by default**. Under the map, in the third column after **Satellite Analysis Overlay**, use **Plot overlays**: 1. **Show nearby plots** — off by default. Tick it to load neighbouring plots from other suppliers nearby. The choice is remembered in this browser. 2. **Show overlaps** — on by default. Untick it to hide overlap colours and labels. Plot boundaries stay on the map. A **Supplier Report** (Show Report on the supplier page) never shows those overlap names from other plots, on screen or in the printed PDF. ## What counts as "mapped" A plot is mapped once its **boundary or GPS point is saved**. That's the definition behind every mapping-coverage figure in the product, so if your coverage number looks wrong, it's counting exactly this. ## Doing it properly in the field The strongest boundary is one walked on foot with the Field App, at the plot, with the farmer present to confirm where the edges are. Everything else is a reconstruction. Where you have the choice, walk it. ## Next - [Run a deforestation check](/risk-compliance/deforestation-checks/) - what mapping unlocks - [Generate satellite imagery](/risk-compliance/satellite-imagery/) --- # Find a supplier > Search and filter the Suppliers list by short code, name, or what evidence a farm already has. Source: https://docs.orijin.io/supply-base/find-a-supplier/ Open **Suppliers** and use the search box or the filters at the top of the page. If you arrive from a chart on **Analytics → Compliance**, the matching filter is already on and outlined in green. Open **Filters** if the bar is closed. Filters follow the columns in **View**. Hide a column or a whole group and its filters disappear; hide every column and the filter bar is empty. ## Search Search by **short code** or by the **farmer's name**. Prefer the short code. Names are spelled inconsistently, shared between relatives, and recorded differently by different field officers - the short code is the one thing guaranteed to be unique. ## Filters The filters at the top match the columns on the table. Open **View** (top right) to show or hide columns and groups — hiding a column or a whole group also hides its filters. If you hide every column, the filter bar is empty. Four filters narrow the list by what evidence a farm already carries: - **Satellite images** - **Notes** - **Documents** - **Evidence** The same four filters are available on the **Plots** tab, which is often the more useful place to use them - "plots with no satellite images" is a work queue. ## Using filters as a work queue This is what the filters are actually for. Before a buyer audit, the questions you need answered are: - Which suppliers have **no documents**? Those are gaps in your file. - Which plots have **no satellite images**? Those are unfinished compliance work. Filter to those, and you have your list. ## Opening a record Click any result to open the full supplier record - its plots, collections, surveys, payments and history, each on its own tab. If you opened the supplier from a **parent organisation**, the child organisation's short tag and colour appear at the top of the record. ## Print a supplier report On the supplier page, click **Show Report** (the document icon at the top). Choose which sections to include, then **Print** to save a PDF. The report fits in the window without a sideways scrollbar. The PDF has space at the top and bottom of each page. The map shows this supplier's plots only - it does not label overlapping plots from other suppliers. ## Parent organisations If the organisation you are signed into is a parent of other organisations, **Suppliers** (list, plots, and **View Map**) and **Analytics → Compliance** show an **Organisations** picker. Tick the child organisations you want to include. Tick boxes stay checked when you move between the list and the map, leave the page, or refresh. On **View Map**, supplier points use each child organisation's colour — the same colours as the short tags — rather than the usual colours that mean fewer or more suppliers. ## Next - [Edit a farmer's details](/supply-base/edit-farmer-details/) - [Plots and mapping](/supply-base/plots-and-mapping/) --- # Edit a farmer's details > Correct a farmer's code, name, gender, date of birth, email or identification number from the supplier page. Source: https://docs.orijin.io/supply-base/edit-farmer-details/ You don't need to go to **Persons** to fix a farmer's details. You can do it from the farm. ## Steps 1. Open the supplier from **Suppliers**. 2. In the supplier info card, scroll to the **contact person / farmer** section. 3. Click the field you want to change - code, first name, last name, gender, date of birth, email, identification number. The code sits above first name. 4. Edit it and save. ## Where the change actually lands On the **person**, not on the farm. This matters. A person is a record in their own right, so the correction follows them everywhere: open them from **Persons** and you'll see the same change. If that farmer is the contact for a second farm, that farm sees it too. Use **View person** when you need the full person record rather than the summary on the supplier page. ## Phone numbers Phone numbers live on a person's **contacts**, not as a field on the farm. If you're looking for where to change a number and can't find it on the supplier card, that's why - open the person record. ## Identification numbers are worth the effort The identification number is the field that makes two farmers with the same name in the same village distinguishable. It's tedious to collect and it's the difference between a supply base you can audit and one you can't. Fill it in where you have it. --- # Certification status > Set a supplier's certification status individually or in bulk, and manage the list of certification types. Source: https://docs.orijin.io/supply-base/certification-status/ Orijin does **not** store certifications as separate records with scans and expiry dates. Each supplier simply has a **certification status**. This is a deliberate simplification: the status is what gates buying decisions and what buyers ask about, so the status is what the product stores. ## Set it on one supplier 1. Open the supplier from **Suppliers**. 2. In its **Details** card, find the certification status field - it's editable in place. 3. Set it and save. ## Set it on many at once 1. On the **Suppliers** list, tick the suppliers you want. 2. Open the bulk-actions menu and use **bulk edit**. This is how certification is normally maintained. Status changes arrive as a list from the certifying body once or twice a season, and you apply them to a few hundred farms in one pass rather than one at a time. ## The list of possible statuses The available certification types are managed by an administrator under **Configuration → Certification Types**. If the status you need isn't in the list, that's where it gets added - ask an administrator rather than approximating with a status that's nearly right. ## Keeping it honest Certification status drives what you're allowed to sell as certified. Two habits are worth having: - **Update it when the certifier does, not when you remember.** A stale "Organic" is a compliance problem, not a data-quality problem. - **Record the source.** Use the supplier's documents to attach the list or certificate the status came from, so an auditor can see why it says what it says. ## Seeing the whole picture **Risk & Compliance → Certification analytics** summarises coverage across your supply base - how many farms hold each status, and where they are. --- # Supplier surveys > Open a specific completed survey on a supplier and share a direct link to it. Source: https://docs.orijin.io/supply-base/supplier-surveys/ Surveys are what your field team asks farmers - baseline questionnaires, annual assessments, programme-specific forms. Completed ones are stored against the supplier. ## Open one 1. Open the supplier from **Suppliers**. 2. Open the **Surveys** tab. 3. Click the survey you want, identified by **name and date**. ## Share it Every survey has **its own address**. When you click a survey, the address in your browser updates to point at that specific survey on that specific supplier. Copy that address and send it. Anyone in your organisation who opens it lands exactly where you were - same supplier, same survey, no instructions needed. This is the fastest way to settle a question about a specific farmer's answers. Rather than "look at the Kwizera survey from March", send the link. ## Who can open it Only people in your organisation with access to that supplier. The link is a pointer, not a public share - it doesn't expose anything to someone who couldn't already see it. ## Where surveys come from Surveys are designed and run through **Sustainability & Monitoring → Surveys**, and answered in the Field App, usually offline at the farm. What you see on the supplier's Surveys tab is the result. If a survey includes a **Manage Plots** step and that survey requires offline maps, the **phone** Field App asks you to download maps first. The download retries if the connection drops. In a **web browser**, live maps are used and that download is not required. --- # Edit a survey > Organisation admins can edit a Firestore survey from the survey page, using the same editor as Organisation config. Source: https://docs.orijin.io/supply-base/edit-a-survey/ Surveys that your organisation owns live in organisation settings. Admins can open that editor from the survey itself, instead of going through Organisation config. ## Open it 1. Open **Sustainability & Monitoring → Surveys**. 2. Open the survey you want. 3. Open the **Survey config** tab. It sits after **Planning**. You see the same editor as **Organisation config → Surveys** for that survey. Change sections, questions or settings, then save. ## Question help and saved answers When you edit a question: - **Hint** is the short help shown under that question on the web and in WhatsApp. It is not a second question. - **Saves answer to** copies the answer onto the supplier record when the survey is submitted. Choose **Survey answer only** to keep it as a survey answer. The list only offers fields that match the question type, such as contact gender, contact phone, contact email, contact date of birth, supplier name, supplier area, plot name, and plot area. ## Help on a standard field Standard sections (Plots, Personal details, and the others) already have their own fields. Open **Manage fields** on that section. Each included field has a help line per language. - The text is shown under that field in the field app, on the web, and in WhatsApp. - Leave it empty to keep the wording the field already has. - The survey JSON stores the text under the survey's labels, and lists the field on that section. ## Section intro Personal details, Location, Farm details, Plots and Documents can each start with a short intro. Open **Manage fields** on the section and write the intro at the top, one box per language. - In WhatsApp and Telegram, the intro is sent as its own message just before the first question of that section, once per survey. - On the web, it is shown at the top of the section. - In the field app, it is shown under the step name. - Leave every box empty for no intro. ## Address fields - The **Location** section has an **Address** field for the supplier: how to get there, in the farmer's own words. It is saved on the supplier and shown on the supplier page. - The **Plots** section has an **Address** field for each plot: directions or a landmark near the plot. It is saved on the plot and shown on the plot page. - Both are off by default, so existing surveys do not change. To use one, tick **Address** in **Manage fields** on that section. The farmer can still leave it empty. ## Plot names in WhatsApp and Telegram When the Plots section keeps the plot **Name** field, the bot asks the farmer to name each plot after they finish walking it. When the survey leaves the name out, the bot names plots Plot 1, Plot 2 and so on. ## Who sees it The tab is only there when **all** of these are true: - you are an **organisation admin** - the survey is stored in your organisation (copied or created in Organisation config), not a built-in template If you do not see **Survey config**, either this survey is a built-in template, or your role cannot change organisation settings. --- # Deforestation checks > Run a satellite deforestation (EUDR) analysis on a mapped plot and read its risk level. Source: https://docs.orijin.io/risk-compliance/deforestation-checks/ A deforestation check runs **per plot**, and the plot needs a [mapped boundary](/supply-base/plots-and-mapping/) first. ## Steps 1. Open the supplier from **Suppliers**. 2. Go to its **Plots** tab and open the plot you want. 3. In the plot's **EUDR** section, request the satellite analysis. 4. When it finishes, fetch the results to see the plot's deforestation risk level. :::note[Where checks start] The supplier's **Assessments** tab *shows* results but does not *start* a check. Checks always start on the plot. ::: ## What the result means The analysis returns a risk level for that specific piece of land, on the date it ran. It is evidence, not a verdict - whether you buy from that plot is your decision, and Orijin records the decision you made. Re-running the check later can give a different answer, because the underlying satellite data changes. :::caution[This page is a summary] The steps above are accurate and complete. A fuller guide - risk levels explained, what to do about a flagged plot, and how checks feed the report - is still being written. ::: ## Next - [EUDR due-diligence reports](/risk-compliance/eudr-reports/) - [Satellite imagery](/risk-compliance/satellite-imagery/) --- # EUDR due-diligence reports > Build and print the EUDR due-diligence report for a set of suppliers or an entire lot's chain. Source: https://docs.orijin.io/risk-compliance/eudr-reports/ This is the artefact your buyer's compliance team actually asks for. ## From a set of suppliers 1. On the **Suppliers** page, tick the supplier(s) you want to cover. 2. Open the bulk-actions menu and choose the **EUDR report** action. 3. A setup dialog lets you pick which sections and columns to include - confirm it to build the report. **Geolocation errors** is off until you tick it; each plot row then lists its geolocation errors. Unticking **Legal risk distribution** removes legal risk from the chart and from the plot table. 4. Use the **Print** button (the printer icon) to save it as a PDF to share. ## From a lot The same report is available on a lot's **EUDR** tab, covering **every supplier in that lot's chain**. It includes the lot ancestry alongside the field setup and the same Print button. This is usually the version a buyer wants, because it answers the question they actually asked: where did *this shipment* come from. ## Report quality depends on the work upstream The report is only as complete as the data under it. It is most complete when plots are **mapped** and their **deforestation checks have been run**. A report full of unmapped plots is not a compliance document; it's a list of gaps. Check your mapping coverage before you generate anything you intend to send. :::caution[This page is a summary] The steps above are accurate and complete. A fuller guide - what each report section contains, and how to interpret it - is still being written. ::: --- # Satellite imagery > Generate or delete baseline and comparison satellite images across many plots at once. Source: https://docs.orijin.io/risk-compliance/satellite-imagery/ Satellite images are the visual evidence that sits alongside a [deforestation check](/risk-compliance/deforestation-checks/) - what the land looked like then, and what it looks like now. ## In bulk 1. On **Suppliers**, tick the suppliers - or switch to the **Plots** tab and tick plots. 2. Open the bulk-actions menu and choose **EUDR**. 3. Choose **Generate Satellite Imagery**. 4. Pick your options: **Baseline**, **Compare with**, and **Surrounding area**. 5. Confirm, to start images for every selected plot. **Delete Satellite Imagery** uses the same date choices and removes that image set. ## For one plot The same options are on an individual supplier's or plot's **Satellite** tab. ## Prerequisite Plots need a [mapped boundary](/supply-base/plots-and-mapping/) first. There's nothing to photograph without one. :::caution[This page is a summary] The steps above are accurate and complete. A fuller guide - choosing baseline dates and reading the comparisons - is still being written. ::: --- # Record a collection > Record a purchase from a farmer, in the Field App at the point of collection or in the dashboard. Source: https://docs.orijin.io/traceability/record-a-collection/ A purchase from a farmer is recorded as a **Collection** - also called a **lot**. It's the atom that everything downstream is built from. ## In the field (the normal way) The Field App captures it at the point of collection, in this order: choose the farmer, then the payment method, then the weight and the rest of the delivery. Once the farmer or the payment method is chosen it stays fixed. To change either one, start the collection again. Offline is fine - it syncs later. This is where it should happen. The farmer is present, the scale is there, and the purchase is attached to a real farmer record rather than a name written down and typed in later. ## In the dashboard 1. Open **Collections**, under **Traceability and Production**. 2. Click **Create lot**. 3. Fill in the form and save. A supplier's collections also appear on its own **Collections** tab. The filter bar there starts closed; open **Filters** to change season or other filters. To look up existing collections by lot label, collection ID, or a pasted list, see [Find a collection](/traceability/find-a-collection/). ## Where the rest lives - **Payments** - **Traceability → Payments → Payment Transactions**. See [Pay a farmer](/payments/pay-a-farmer/). - **Charts, the collection activity map, operator totals, facility totals and the season view** - **Collections → Analytics**. See [Collection analytics](/traceability/collection-analytics/). :::caution[This page is a summary] The steps above are accurate and complete. A fuller guide - collection points, stages, and how collections combine into processed lots - is still being written. ::: --- # Collection analytics > Collection charts, the collection activity map, operator totals, facility totals, and the season view. Source: https://docs.orijin.io/traceability/collection-analytics/ Open **Traceability → Collections → Analytics**. Five tabs, each answering a different question. ## Dashboard Collection charts - volume and value over the season. On the collections list and similar tables, **Quick Range** can jump to **This year**, **Last year**, **This season**, or **Last season**. See [Filter by date](/start-here/filter-by-date/). Location charts use the same level toggle as the home page. On the second location level, the first-level code is shown on the bar and rows sort by that first level. Each graph has a **View lots** or **View collections** link, and clicking a slice or bar opens that table with the matching filter. ## Collection Activity The map. Where collection actually happened, which is often not where you assumed. Open a lot and choose **Map** to see that same map for the lot alone. There is no filter bar. Points also include logistics records and other activities that have a recorded position. Collection, activity, and logistics points use different colours. ## Operator Totals Totals by **operator** and **collection point**, with the **purchase location** levels used when a collection is recorded shown on that same row. This tab is more interactive than it looks: - The operator email sits under the operator name. - The collection location **code** sits under the location name. - Purchase location columns follow the organisation's purchase location hierarchy. They show the location for that collection point and do not split the table into extra rows. If that collection point has more than one purchase location, or some collections have no location, those columns stay empty. - If Collection ID is turned on for the organisation, that column appears as a count. Click it to see the collection IDs, the same way as receipts. - Click a **supplier, receipt, collection ID or lot count** to see the underlying values. Use **Copy all** or the copy icon next to a row to copy the list. - Click a **collection point** to open those collections on the **Stages** tab. **Export Operator Totals** when you need a list of each collection point and who delivered there - it's the report most operations teams end up wanting. ## Facility Totals Same numbers as Operator Totals, but **each facility appears once**. Collections by every operator at that site are combined into one row. - Click a **supplier, operator, receipt, collection ID or lot count** to see the names. - **Copy all** copies the whole popup list. The copy icon copies one row. - Click the **facility name** to open those collections on the **Stages** tab. - Group by **Whole period** if you want one row per facility for the selected dates. Group by day, week or month if you want the same facility broken out by time. ## Season The season view - totals for the collection period as a whole. ## Where the raw lists are - The collection list itself: **Collections → Collections** - Payments: **Traceability → Payments → Payment Transactions** :::caution[This page is a summary] The steps above are accurate and complete. A fuller guide - reading each chart and configuring which sections appear - is still being written. ::: --- # Find a collection > Filter Collections by lot label, collection ID, or session ID — one value or a pasted list. Source: https://docs.orijin.io/traceability/find-a-collection/ Open **Traceability → Collections**. The same filters sit on the **Lots** tab and the **Stages** tab, and on a supplier's **Collections** tab. The bar starts closed even when a season is already selected. Open **Filters** to change season, dates, or other filters. A number on the button shows how many are already on. ## One value Use the ordinary text filters: - **Lot label** — the collection's lot label - **Collection Id** — only if your organisation uses collection IDs - **Session Id** — only if your organisation uses session IDs ## A list of values When you have many IDs (from a spreadsheet or a receipt book), open the matching list filter instead of typing them one by one: - **Lot label list** - **Collection ID list** — only if Collection Id is on - **Session ID list** — only if Session Id is on Paste or type the values, one per line or separated by commas, then apply the filter. You can also upload a file with a column of values. The table shows only the matching rows. A short report above the table says how many values matched, how many were not found, and whether any value matched more than one row. ## Next - [Record a collection](/traceability/record-a-collection/) - [Collection analytics](/traceability/collection-analytics/) --- # Pay a farmer > Record, approve and edit a payment against the collection it settles. Source: https://docs.orijin.io/payments/pay-a-farmer/ The key thing to know: **you record a payment against a collection, not from the payments list**. If you're staring at Payment Transactions looking for an "add" button, that's why. ## Record a payment 1. Open **Collections**, under **Traceability and Production**. 2. Open the lot you want to pay. 3. Click **Add payment transaction**. 4. Fill in the payment and save. ## Approve it On that lot's **Payment Transactions** tab, use **Approve** from the row actions. ## Check or edit an existing payment Open the payment from **Traceability → Payments → Payment Transactions**. You can approve it there, or edit: - amount - status - type - payee name - receipt number - comment Hover a field and use the pencil - the same in-place editing as on a supplier page. You can also add **notes and documents** on the payment page, which is where a receipt scan or a note about a disputed weight belongs. ## What you can't change Collection, supplier and created-by details stay **read-only**. A payment is tied to the delivery it settles and the person who entered it, and that link is not editable by design. ## The audit trail Changes, approvals, notes and documents are all listed in the **Audit log** and **Notes & documents** sections on the payment page. This is the answer to "was this farmer paid, by whom, and when was it approved?" - and it's why edits are recorded rather than silent. :::caution[This page is a summary] The steps above are accurate and complete. A fuller guide - cash versus mobile money, wallets, and bulk payment runs - is still being written. ::: --- # Documents and notes > Store files and comments that belong to the organisation as a whole, such as due-diligence packs and data-clean reports. Source: https://docs.orijin.io/organisation/documents-and-notes/ Some files belong to the organisation rather than to any one farm - an EUDR due-diligence pack, a data-clean report, a policy document. ## Add a document 1. Open **Organisation** in the left-hand menu. 2. Go to **Documents**. 3. Click **Add document**. 4. Choose a **category** and, optionally, a **report date**. 5. Upload. The report date matters more than it looks. It's what lets you answer "what did we know, and when?" - which is the question an auditor asks. ## Notes **Notes** is for organisation-level comments: context that isn't a file and doesn't belong on a specific supplier. ## What lives elsewhere - **Settings** - under **Configuration** - **Risk Assessment** - under **Risk & Compliance** :::caution[This page is a summary] The steps above are accurate and complete. A fuller guide - document categories and retention - is still being written. ::: --- # Users and roles > Add a colleague to your organisation and choose what they can see and do. Source: https://docs.orijin.io/organisation/users/ ## Add someone 1. Go to **Configuration → Users**. 2. On the **Users** tab, click **Add**. 3. Enter their email address. 4. Choose their **role** - this controls what they can see and do. 5. Save. ## Sessions 1. Go to **Configuration → Users**. 2. Open the **Sessions** tab. 3. The current Android field app version is shown above the list. 4. Green means that login is on the current version. Amber means it is still allowed, but older than the newest release. Red means it is older than the required version. 5. Click the person's **name** to open their page. ## If you can't see this page This area is limited to **administrators**. If **Configuration → Users** isn't in your menu, ask an admin in your organisation to add the person for you. ## Choosing a role The role is the whole of the access decision, so it's worth a moment's thought rather than defaulting to the most permissive option. A field officer who only needs to collect data does not need payment approval; giving it to them makes your audit log less meaningful, not more convenient. See [Getting access](/start-here/getting-access/) for what the broad role categories cover. :::caution[This page is a summary] The steps above are accurate and complete. A fuller guide - the full role matrix and what each permission grants - is still being written. ::: --- # Find a facility > Filter collection points and other facilities by whether they have suppliers, lots, a location, GPS, or a contact person. Source: https://docs.orijin.io/organisation/find-a-facility/ Open **Configuration → Facilities**. - **Hierarchy** is the location tree. - **All facilities** is the list. Use the filters at the top of the table. - **Map** plots facilities that have a GPS position. Click a point and the details open in the panel on the right. **Open facility** (or the name) goes to the full facility page. Facilities with no GPS stay off the map. ## What you can filter by These Yes/No filters are for finishing incomplete records and finding which collection points are actually in use: - **Has suppliers** - linked farmers - **Has lots** - collections bought at or currently held by this facility - **Has contact person** - **Has location** - **Has GPS** **Yes** keeps facilities that have that thing. **No** keeps the ones that are missing it. You can still type a minimum supplier or lot count when you need "at least 4" rather than "at least 1". ## Using this as a work queue Before a season starts, the useful questions are: - Which collection points have **no suppliers**? - Which have **no contact person**? - Which have **no location** or **no GPS**? Filter to those, and you have the list to complete. ## Opening a record Click a facility name to open it - suppliers, people, documents and the rest of the profile. The **lots** number is a link: it opens **Collections** already filtered to collections bought at that facility. --- # Import data in bulk > Upload suppliers, farmers, plots and map boundaries from spreadsheets, GeoJSON or KML. Source: https://docs.orijin.io/organisation/import-data/ Two routes, depending on scale. ## Quick import into one list Use the **Import** button on the page itself - for example on **Suppliers** - and upload a file. ## Larger or first-time imports Go to **Configuration → Import Data**. It has tabs for: - **Reference data** - single record or Excel - **Map boundaries** - GeoJSON / KML - **Production data** - **An onboarding wizard** for first-time setup A **Jobs Center** tracks progress, which matters because a large import is not instant. ## Do a small sample first Always. Import ten rows, open them in the dashboard, and check they landed the way you expected - especially short codes, the location hierarchy, and whether farmers were matched to existing people or created as duplicates. Fixing ten bad rows is an afternoon. Fixing four thousand is a project. ## If you're unsure about the format Ask your Orijin contact before uploading rather than after. Import formats are particular, and a malformed file that partially succeeds is the worst outcome. :::caution[This page is a summary] The steps above are accurate and complete. A fuller guide - file formats, column definitions and matching rules - is still being written. ::: --- # The Field App test workspace > Open or close the Field App test workspace so staff do not record real data in it by accident. Source: https://docs.orijin.io/organisation/test-workspace/ Each organisation has two Field App workspaces: the **main** one, holding real data, and a **test** one for training. The failure mode this page prevents: a field officer picks the wrong workspace and a day of real collections lands somewhere that isn't your supply base. If the test workspace is still open, the Field App shows a warning on the workspace picker before you continue. ## Close it 1. In the dashboard, go to **Settings**, under **Configuration**. 2. Stay on the **General** tab. 3. Find **Test workspace is open** and turn it **off**. 4. Save. The test workspace then no longer appears when people choose a workspace in the Field App. ## Open it again Turn the same switch back on when you want staff to use the test workspace - during onboarding or training, for example. ## The main workspace is not affected Closing the test workspace changes nothing about real data or normal use. ## A reasonable default Keep it closed. Open it deliberately for a training session, and close it again afterwards. :::caution[This page is a summary] The steps above are accurate and complete. A fuller guide is still being written. ::: --- # Events > The log of everything that happened - split into Info, Field App, Warning and Error, and searchable. Source: https://docs.orijin.io/organisation/events/ **Events** is the record of what happened - who changed what, what the Field App sent, and what went wrong. ## The tabs Open **Configuration → Events** (after **Settings**) and use the tabs: - **Info** - normal activity - **Field App** - what came in from phones - **Warning** - things that need a look - **Error** - things that failed Each tab has **its own address**, so you can bookmark one or send it to a colleague. ## Search Search by **type**, **name**, **short code**, or **the person who made the change**. The short code is usually the fastest way in. If a farm's data looks wrong, search its short code here and you'll see everything that ever happened to it. Your search stays in the address too, so a refresh keeps the same tab and the same search - and a link you share carries both. ## What it's for Two things, in practice: - **Settling disagreements.** "This supplier's area changed" has an answer here, with a name and a timestamp. - **Catching sync problems early.** The **Warning** and **Error** tabs are worth a glance after a big field sync, rather than discovering a problem a month later in a report. :::caution[This page is a summary] The steps above are accurate and complete. A fuller guide - event types and what each warning means - is still being written. ::: --- # Farmer Bot > Invite users, follow conversations, and send broadcasts from Farmer Bot. Source: https://docs.orijin.io/organisation/farmer-bot/ Farmer Bot is the Telegram bot your organisation uses to talk with users. ## Open Farmer Bot 1. Go to **Configuration → Farmer Bot**. 2. Use **Overview**, **Users**, **Conversations**, and **Broadcasts**. Config and Usage are not on this page. If you do not see **Farmer Bot** in Configuration, ask an administrator. ## Invite a user 1. Open **Users**. 2. Click **Invite to bot**. 3. Choose the supplier, then generate a link or send it by SMS. The person must open the link and start the bot before they can receive messages. ## Follow a conversation 1. Open **Conversations**. 2. Open a thread to read it or reply. ## Send a broadcast 1. Open **Broadcasts**. 2. Click **Create broadcast**. 3. Enter a title and message, then create it. 4. Send the draft from the list. A broadcast only reaches users who have already started the bot. ## Bot setup Token, webhook, and usage reports are Superuser-only. Ask your Orijin contact if the bot is not configured yet. --- # Connect your assistant > Query your own Orijin data in plain language from Claude, Cursor or any MCP-capable assistant. Read-only, scoped to your organisation. Source: https://docs.orijin.io/for-agents/connect-your-assistant/ Ask your own Orijin supply-chain data questions in plain language, from the AI assistant your team already uses - no new dashboard, no exports, no SQL. Access is **read-only** and **scoped to your organisation only**. ## What you need from Orijin Your Orijin contact will send you two things: 1. **A server URL** - e.g. `https://mcp.orijin.io/mcp/` 2. **An API key** - a long secret string, e.g. `orijin_live_xxxxxxxxxxxxxxxxxxxx` :::danger[Treat the API key like a password] It grants read access to your organisation's data. Don't share it, and don't commit it to code. If it leaks, tell Orijin and we'll revoke it. ::: ## Claude Code (CLI) One command - replace the URL and key with the ones Orijin gave you: ```bash claude mcp add --transport http orijin https://mcp.orijin.io/mcp/ --header "Authorization: Bearer " ``` Start Claude Code and type `/mcp` to confirm it shows **orijin - connected**. - List or check: `claude mcp list` - Remove: `claude mcp remove orijin` ## Claude Desktop Claude Desktop connects to remote servers through a helper called `mcp-remote`. It requires [Node.js](https://nodejs.org). Add this to your config file: - **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json` - **Windows**: `%APPDATA%\Claude\claude_desktop_config.json` ```json { "mcpServers": { "orijin": { "command": "npx", "args": [ "mcp-remote", "https://mcp.orijin.io/mcp/", "--header", "Authorization: Bearer " ] } } } ``` Save, then **restart Claude Desktop**. The Orijin tools appear in the tools menu. ## Try it - "How many of our farms are active?" - "Show plot mapping coverage by region." - "List certifications that are expired." - "How many procurement lots are still pending payment?" - "What's the risk-score breakdown across our farms?" The assistant picks the right tool automatically and answers from your live data. Ask it to show the underlying numbers if you want to verify. ## Good to know - **Read-only.** Nothing you or the assistant does can change or delete data. - **Your data only.** The key is tied to your organisation; it cannot see any other client's data. - **Rate limit.** Up to 100 requests per minute per key. Heavy back-and-forth may briefly pause - just retry. - **Your data stays in Orijin.** Only the answers to your questions leave, and only to the assistant you connected. ## Troubleshooting | Symptom | Likely cause / fix | |---------|--------------------| | "Connected" but tools error with 401/403 | Key is wrong, expired, or the URL org doesn't match the key. Re-check both; contact Orijin for a fresh key. | | Tools time out | The server URL is wrong, or a network/firewall block. Confirm the exact URL with Orijin. | | Claude Desktop shows nothing | Node.js not installed, or a typo in the config JSON. Validate the JSON and restart Desktop. | | Web (claude.ai) can't add it | The browser client requires OAuth, which isn't available yet - use Claude Code or Claude Desktop. | Questions, or a new key: contact your Orijin representative. ## Next - [What agents can do](/for-agents/what-agents-can-do/) --- # What agents can do > The tools an assistant connected to Orijin can call, what it cannot do, and how to get good answers out of it. Source: https://docs.orijin.io/for-agents/what-agents-can-do/ Once [connected](/for-agents/connect-your-assistant/), an assistant can read your organisation's supply-chain data through a set of named tools. It chooses which to call; you just ask the question. ## What it can read **Your supply base** - farms (suppliers), the people attached to them, plots, and plot geolocations. Look up one by id or by short code, or list and filter them. **Compliance evidence** - satellite assessments on plots, and certifications including the list of certification types your organisation uses. **Procurement** - collection lots, trades and payments. **Aggregate statistics** - farm counts, farms by region, certification coverage, risk breakdowns, non-compliance and trade totals. Ask "how many" or "by region" questions and it will use these rather than counting rows, which is both faster and more accurate. ## What it cannot do - **Write anything.** Every tool is read-only. There is no tool that creates, edits or deletes, so no instruction - from you or from anything it reads - can cause a change. - **See another organisation.** The API key is bound to your organisation. Even if it asked for someone else's data, the server would refuse. - **See more than you can.** Access follows the key's scopes. ## Getting good answers **Ask for the number, then ask to see it.** "How many plots are unmapped?" then "show me the list" - the second question confirms the first. **Use your own vocabulary.** It knows a farm is a Supplier. Ask about farmers, producers, or suppliers and you'll get the same place. **Say which organisation** if you have access to more than one. If you only have one, it's used automatically. **Prefer aggregates for totals.** "Certification coverage by region" gets a statistics tool. "List every farm and count them" makes it page through thousands of records to get the same answer worse. ## Verifying what it tells you Ask it which tool it used and what the raw numbers were. The tools return real figures with totals attached, and an assistant that can't show you its source for a number is one you shouldn't quote to a buyer. Cross-check anything you're about to put in a compliance document against the dashboard. ## Reading the documentation itself This documentation is also machine-readable. A connected assistant can search and read these pages, so "how do I run a deforestation check?" is answered from the same source you're reading now - not from guesswork. See [llms.txt](/for-agents/llms-txt/) for how any assistant, connected or not, can read these docs. --- # llms.txt > Machine-readable versions of this documentation, for any AI assistant. Source: https://docs.orijin.io/for-agents/llms-txt/ This documentation is published in a form assistants can read directly, without any integration. ## The files **[/llms.txt](/llms.txt)** - an index. Every page, with its title, a one-line description and its URL. Small enough to drop into a prompt whole. **[/llms-full.txt](/llms-full.txt)** - the entire documentation as one plain-text file. Larger, but complete: an assistant that reads it has the whole product. Both follow the [llms.txt convention](https://llmstxt.org/). ## Using them Point any assistant at the URL: > Read https://docs.orijin.io/llms-full.txt and then tell me how to run a > deforestation check on a plot. Or paste `llms.txt` into a system prompt, and let the assistant fetch the specific pages it needs. ## Why this exists These pages are the **single source of truth** for how Orijin works. The same Markdown produces this website, the help library behind the in-dashboard AI Assistant, and these files. That's deliberate. Documentation that only humans can read goes stale, because nobody notices. Documentation that an assistant answers from is exercised every day, by every user who asks it a question - and a wrong answer gets reported. It also means an assistant working with Orijin doesn't have to guess at screen names or invent buttons. It reads what's here. ## For engineers changing Orijin If you're an agent or a developer changing a user-facing flow, the doc page is the thing you update - not the generated help library, and not this file. See `docs-site/CONTRIBUTING.md` in the repository. --- # Privacy Policy > How Orijin collects, uses and protects personal data across the Orijin field app, dashboard and website. Source: https://docs.orijin.io/legal/privacy/ **Last updated:** 22 September 2026 Orijin Oy ("Orijin", "we") builds software that helps agricultural producers, cooperatives and exporters record where their crops come from and demonstrate compliance with regulations such as the EU Deforestation Regulation (EUDR). This policy covers the **Orijin OnField** mobile app, the Orijin web dashboard, and orijin.io. ## 1. Who to contact Orijin Oy, Finland — privacy@orijin.io ## 2. Our role: when we are a processor, and when we are a controller This distinction matters, because it determines who you should contact about your data. **Farmer and supply-chain data — we are a processor.** When a cooperative, exporter or producer organisation uses Orijin, *they* decide which farmers to register, what to record and why. We process that data on their documented instructions, under a data processing agreement. If you are a farmer whose details are held in Orijin and you want to see, correct or delete them, contact the organisation that registered you. They are the controller. We will support them in responding, but we cannot act on your data without their instruction. **Accounts of people who use our software — we are the controller.** For the field agents, supervisors and administrators who log in to Orijin, we decide how account and usage data is handled, and this policy applies to us directly. ## 3. What the field app collects The Orijin OnField app is used by field agents working for our customers. It collects: - **Account details** — name, email address, and the organisation you belong to. - **Precise location.** The app records GPS coordinates when an agent stamps a form, registers a farm, or walks a plot boundary. Boundary walking uses a foreground service, so location is collected while the walk is running and a notification is shown throughout. We record the accuracy of each reading alongside the coordinates, because accuracy is itself evidence of data quality. Location is never collected when the app is closed. - **Photographs** taken through the app — farms, crops, receipts, signatures and supporting documents. - **Device information** — model, manufacturer, operating system version, app version, a device identifier, and whether the device was online or offline when a record was created. - **Bluetooth readings** from connected weighing equipment. Bluetooth permissions are used only to talk to scales; the app does not scan for or track nearby devices or people. - **Supply-chain records entered by the agent** — farmer and supplier names and contact details, farm and plot locations and boundaries, crop and collection quantities, prices and payments. This is the farmer data described in section 2, for which our customer is the controller. **Receipt text recognition runs entirely on the device.** The app bundles an offline text recognition model, so when it reads a printed receipt the image is processed on the phone. The image is not sent anywhere for that purpose. The app is built to work offline. Records are stored on the device and synchronised when a connection is available. ## 4. What the dashboard and website collect The dashboard collects account details, authentication data, and a log of actions taken so that changes to supply-chain records are auditable. The website collects standard server logs and any details you submit through a contact form. ## 5. Why we process this data, and on what legal basis | Purpose | Legal basis | | --- | --- | | Providing the platform to our customers | Performance of a contract with the customer; for farmer data, processing on the controller's instructions | | Authenticating users and securing accounts | Legitimate interests — keeping the service secure | | Diagnosing crashes and improving reliability | Legitimate interests — the software must work offline in remote areas, where faults are hard to reproduce | | Producing compliance evidence, including EUDR due diligence | The customer's legal obligation, for which we act as processor | We do not sell personal data. We do not use it for advertising or profiling. ## 6. Who else processes data on our behalf | Service | Purpose | Location | | --- | --- | --- | | Google Cloud / Firebase | Hosting, authentication, database, file storage, push notifications | EU and US | | Sentry | Crash and error reporting, including session replay | United States | | Mapbox / MapLibre | Map tiles shown in the app and dashboard | United States | | Google Sign-In | Optional account sign-in | United States | **About session replay.** We use Sentry to understand faults that happen in the field. This includes recording a sample of roughly one in ten sessions so we can see the sequence of screens that led to an error. These recordings mask on-screen text and block images by default, so they show the structure of what happened rather than the content of records. They are stored in the United States. **Transfers outside the EEA.** Some of the services above are based in the United States. Those transfers rely on the European Commission's Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework. ## 7. How long we keep data We retain supply-chain and compliance records for **five years**, which matches the record-keeping period required for EUDR due diligence. Our customers may instruct us to delete data sooner, and we return or delete data when a customer contract ends, subject to any retention we are legally required to apply. Account data is kept while the account is active and deleted within a reasonable period afterwards. Crash and session replay data is kept according to Sentry's retention settings. ## 8. How we protect data Data is encrypted in transit. Access to production systems is limited to staff who need it. Data on the device is protected by the device's own security; agents should use a screen lock, because the app is designed to hold records offline. ## 9. Your rights If you are in the EEA or UK you have the right to access your data, correct it, have it deleted, restrict or object to processing, and receive it in a portable form. You may also complain to a supervisory authority — in Finland, the Office of the Data Protection Ombudsman. If you are a farmer or supplier recorded in Orijin, please direct these requests to the organisation that registered you, for the reason explained in section 2. ## 10. Children Orijin is workplace software and is not intended for children. We do not knowingly collect data from anyone under 16. ## 11. Changes We will update this page when our processing changes, and revise the date at the top. Material changes will be communicated to our customers directly.