overview
HeyFlora beta documentation
Start here to learn what the beta covers, where to begin, and how the main workflows fit together.
What HeyFlora beta helps with
HeyFlora beta helps commercial landscaping teams turn day-to-day field information into searchable context and follow-up work. Use it when you need to connect a field observation, site conversation, document, customer, or property to the next question or action.
The beta is centered on:
- Property memory as the long-lived record.
- Field capture through Field Snaps, huddles, mobile flows, and plant-health assessments.
- Knowledge-base uploads for SOPs, site documents, service material, and prior business context.
- Flora chat as the operating surface for searching, drafting, and asking grounded questions.
- Role and module access so each user sees the parts of the product their company enables.
Where to start
If you are new, begin with Getting started, then complete Discover so Flora understands the company, your role, and one recurring workflow. After that, upload a few trusted documents, confirm customer and property records, and try one field workflow such as Field Snaps or plant health.
Admins should review Roles and permissions before inviting broader teams. Field teams should start with Mobile access and Field Snaps.
What these docs cover
These docs describe the public beta surface, not every internal engineering module. They cover setup, Discover, agent chat, knowledge base, customers and properties, Field Snaps, plant health, huddles, roles, mobile access, troubleshooting, privacy boundaries, and release notes.
Technical names are used only when they help admins understand behavior. Day-to-day users should think in terms of documents, properties, field observations, tasks, and approved actions.
Current boundaries
These docs cover public beta behavior, not every internal engineering module. Some features may be enabled only for specific roles, modules, or beta tenants. If a page, button, or chat tool is missing, check access before assuming the feature is unavailable.
Mobile access routes through your tenant's own HeyFlora environment. Mobile does not connect to external AI services directly.
How these docs stay current
The public docs index tracks every page's source files, routes, and last-verified date. When beta product code changes a documented workflow, a matching docs update ships alongside it. The index lets search tools cite the right page and helps catch outdated content.