Pyron uses a small, consistent set of words for the things you work with — the directory, an entry, a form, a lifecycle. Each one is defined here in a sentence or two, with a link to the page that covers it in full. When a word in the docs is unfamiliar, this is the place to look it up.
Terms
Your directory
- Directory — Everything your organisation keeps track of — sites, areas, vehicles, equipment — arranged as a branching structure. Where something sits in the directory decides who can see it, which forms apply, what it counts toward, and what happens next. See The directory.
- Tree — One branching structure in the directory, from a single root down through its branches. Your organisation can keep several side by side, each holding one kind of information. See The directory.
- Category — What kind of thing something in the directory is at its level — a site, an area, a vehicle. Pyron speaks in category names — "Edit Vehicle", "Add Site" — so the directory reads in your organisation's own words. See The directory.
- Root — The top of a tree — the one place everything else in that tree hangs off. Each tree has exactly one root, and no two trees share one.
- Child — Anything that sits directly beneath something else in the directory. The one above it is its parent, and access always reaches the children too, all the way down the branch.
Capturing information
- Entry — One thing your team has logged, filed where it belongs in the directory: an inspection against a site, an incident against a vehicle, a shift handover. Entries are the information Pyron holds for you, and almost everything else is a way to capture, move or read them. See Entries.
- Form — The set of questions your team answers to log an entry. A form decides what gets captured and how, so the shape of a form is the shape of the information you end up with. See Forms and data schemas.
- Field — One question on a form. A field has a label — the words you read — and a type that decides what kind of answer it accepts, such as text, a number, a date, or Yes / No. See Forms and data schemas.
- Data schema — The underlying shape of the answers a form collects: which questions it holds, what type each answer takes, and which are required. The form is what you fill in; the data schema is the structure behind it. See Forms and data schemas.
- Choice list — A fixed set of options a field offers to pick from, instead of free typing. The same list can be shared across several fields so they all draw from one set, and an option can carry a colour that shows up as a pill in tables. See Forms and data schemas.
Moving work along
- Lifecycle — A set of named states an entry moves through — open, in progress, resolved — and the steps that carry it from one to the next. A lifecycle tracks where an entry sits and what can happen to it next. See Lifecycles.
- State — One named state in a lifecycle, such as open or resolved. Each state carries its own colour, shown as a badge on the entry, so you can tell at a glance where something stands. See Lifecycles.
- Automation — A set of steps Pyron carries out for you when something happens: emailing a manager, building a report, or attaching a lifecycle to a new entry. You set one up once and it runs on its own from then on. See Automations.
- Flow graph — The diagram of wired-together steps behind an automation. Each step does one job, and arrows carry values from one step into the next. The steps on that canvas are the one thing Pyron calls nodes. See Automations.
- Trigger — The thing that starts an automation: an event such as an entry being logged, a schedule such as every Monday morning, or a button someone presses. Each automation has exactly one trigger. See Automations.
Seeing your information
- Page — A screen that shows your information, split into tabs of widgets. Most pages belong to something in the directory, so opening a site or a vehicle brings up the page built for it. See Pages, tabs and widgets.
- Tab — A named section of a page, with its own layout of widgets. A page always opens on its first tab, and switching tabs changes what you see without leaving the page. See Pages, tabs and widgets.
- Widget — A single block on a tab — a table, a chart, a metric tile, a form. Each widget shows one thing, and several can sit together on a grid you rearrange. See Pages, tabs and widgets.
- Dashboard — A live screen of panels — counts, charts and tables — that stays up to date as your team works. A dashboard is a page shared across your organisation rather than tied to one part of the directory. See Dashboards.
- KPI — A single headline number on a dashboard or page, such as a count of open inspections or a compliance rate. See Dashboards.
- Report — A fixed document Pyron builds from your data — a shift handover, a monthly roll-up — captured at one moment and saved as a file you can open, download or send. See Reports.
- Template — The reusable blueprint behind a report: its layout, your organisation's branding, and a definition of which data to pull in. One template can produce many reports over time, each a snapshot from when it ran. See Reports.
People and access
- Role — A named bundle of permissions an administrator gives a person. It decides which actions and screens are open to them, and someone can hold more than one role, their permissions adding together. See Roles and permissions.
- Permission — The right to do one thing: create an entry, edit part of the directory, or reach the reports area. Hold the permission and the button or link is there; lack it and it is hidden. See Roles and permissions.
- Sharing — Giving one person access to a single part of the directory, on top of whatever their role already allows. A share always includes everything beneath the place you pick, entries included. See Access and sharing.
- Administrator — A person who sets up and manages Pyron for your organisation: building forms, defining roles, and creating lifecycles and automations. Which of these someone can do depends on the permissions their role carries.
- Organisation — Everything your organisation keeps in Pyron — its directory, entries, forms, people and settings — held apart from every other organisation.
- Portal — A single shared account for a device many people use on site, such as a tablet at a loading dock. Each person picks their name and enters a PIN to act as themselves, so their entries stay filed under their own account. See Portals and form links.
- Form link — A URL that opens one form for someone to fill in and submit, without finding their way around the app. A form link can require the visitor to sign in or be made public, and you can revoke or expire it. See Portals and form links.
Finding things and getting help
- Search — A shortcut opens a search box that reaches across Pyron — your entries and the screens you work in — and only ever shows what you are allowed to see. See Search.
- Assistant — Pyron's built-in helper you can chat with in plain language to find information, draft a form, or put together a report. See The AI assistant.