privacy and data boundaries
Privacy and data boundaries
Know which information is public product help, private tenant knowledge, business records, or mobile traffic.
Public product docs
Public platform docs explain how HeyFlora works. They are global, safe for all tenants, and served from the public website.
The public docs index contains page titles, excerpts, canonical URLs, product areas, keywords, routes, last verified dates, and internal source-file references for drift control.
Tenant knowledge
Tenant knowledge is private workspace material such as uploaded documents, SOPs, site files, client notes, proposal examples, and extracted document context.
Tenant questions search your private workspace and cite your company's documents. Public docs explain how HeyFlora works. They do not contain or prove your company's private facts.
Which search should Flora use
Use public product docs for "how do I use this HeyFlora feature?" Use tenant knowledge for "what does our SOP, site file, proposal, or client note say?" Use business records for customers, properties, Field Snaps, huddles, plant-health assessments, users, roles, and modules.
Business records
Customers, properties, Field Snaps, huddles, plant-health assessments, users, roles, and modules live in the beta business data plane. Read and write access depends on user roles, modules, and selected agent policy.
Mobile boundary
Mobile routes through your tenant's HeyFlora environment. It does not connect to external AI services directly in the current documented path.
No shortcut around access
Agent tool configurations are not enough by themselves. HeyFlora checks the current user's role and module access when an action runs.
Related docs