Getting started
Create a workspace, connect a source, invite your team. The graph begins assembling immediately and backfills 90 days of history.
- Create your workspace
- Connect Slack, Notion or Google Drive
- Invite teammates
Documentation
Start with your first source, then work outwards. Most teams are fully connected within an afternoon.
Create a workspace, connect a source, invite your team. The graph begins assembling immediately and backfills 90 days of history.
Each connector is scoped independently. Choose the channels, folders or projects Loreflow may read, and revoke at any time.
Nodes are artifacts, links are influence. Drag to rearrange, click to inspect, and edit the map directly to reflect how your company actually works.
Admins, members, guests and investors. Investor access is scoped separately, from reports-only through full read access.
A REST API for reading the graph, publishing updates and syncing custom sources. Routes are already reserved under /api.
Start here
Nothing below needs an engineer. The longest step is waiting for the first back-fill to finish, and you can close the tab while it runs.
Create the workspace
One workspace per company. Pick the domain everyone signs in with and Loreflow handles the rest of the identity setup.
≈ 40 seconds
Connect your first sources
OAuth into chat, docs and tickets. Read-only by default, and Loreflow is designed to mirror source permissions so nobody sees anything they could not already open.
≈ 2 minutes for three sources
Let the back-fill run
Roughly 90 days of history is imported and linked. The context map becomes useful long before the import completes.
First useful map within an hour
Ask your first real question
Not a demo question — the one your team argued about last month. Every answer arrives with the artifacts behind it.
Answers in seconds
Loreflow polls incrementally and back-pressures itself, so a large workspace never floods your source APIs. Coverage climbs steeply for the first hour and then tracks new activity in near real time.
Numbers from a 40-person workspace with six connected sources.
Coverage after connecting
Percentage of history indexed, by hour.
Reference
Four surfaces, four jobs. If you only learn one, learn the context map — everything else is a view onto it.
| Capability | Best for | Updates | Exports |
|---|---|---|---|
| Context map | Understanding how work connects | Live | PNG, JSON |
| Timeline | Reconstructing a period | Live | CSV, Markdown |
| Insights | Spotting a trend early | Hourly | CSV |
| Decisions | Keeping the reasoning | On write | Markdown, PDF |
| Investor updates | Sharing outward safely | On publish | PDF, link |
Health checks
Three numbers to watch in the first month, and what a healthy range looks like.
Coverage
Aim for 80%+ within two weeks. Below that, answers will have visible holes.
A healthy mix leans on chat. If chat is missing, most reasoning is missing.
Uneven team coverage points at a source you have not connected yet.
−25% from previous step
−38% from previous step
−51% from previous step
−22% from previous step
Rollout funnel: invite a team at a time rather than the whole company at once.
Security reviews, procurement questionnaires and connector questions all go to the same place.
The connector setup section, then sync behaviour. Together they explain everything about the first hour in a new workspace.
Coverage climbs steeply within the first hour and then tracks new activity in near real time. Large workspaces are paced so source APIs are never flooded.
Open Connectors in the app; anything needing a manual sync is pinned to the top with a Sync button and the reason it stalled.
Yes, read access to captured context and decisions, scoped by workspace token. The reference lives in these docs.