A few ideas underpin everything you do in Pyron. Once you know how the tree, the entries you log against it, and the forms that shape them fit together, every other screen falls into place — from the pages that display your data to the roles that decide who sees it.
The building blocks
These pages read well in order. The first few cover the foundations, and the rest build on top of them.
- The directory — the tree of sites, areas and locations that organises everything you capture.
- Entries — what your team logs, what each entry holds, and where it belongs.
- Forms and data schemas — how input forms shape what your team logs.
- Pages, tabs and widgets — the pages attached to the directory, and the widgets you place on them.
- Dashboards — live views over your entries, with KPIs, charts and tables.
- Reports — scheduled, branded documents built from your data.
- Lifecycles — the named states an entry moves through as work progresses.
- Automations — flow graphs that react to events and run on a schedule.
- Roles and permissions — who can see and do what, and how admins control it.
- Access and sharing — how to share parts of the tree with specific people.
- Portals and form links — lightweight ways for field staff and people outside your organisation to submit entries.
- Search — how to find entries and screens fast, from anywhere.
- The AI assistant — a built-in assistant that reads your data and drafts changes for you.
- Glossary — the words Pyron uses, defined once.