How Flowra works

The core: an action with its full context

In most tools a task is a title with a few fields. In Flowra an action is the point the rest of the work is tied to: its owner, its due date, its project, the meeting it came out of, the file attached to it, the contract behind it and the money spent against it. None of those are copies; every one is a reference to the same record.

The consequence is that «context» is not something anybody assembles by hand. When a meeting ends and an action is created out of it, that action knows which meeting it came from. When an invoice is linked to a milestone, the project knows how much has been collected. Nobody keeps this up to date: the act itself creates the relation.

Actions are created from everywhere

You don't have to go to the Actions page to create work. A chat message, a follow-up in My Network, an occurrence of a recurring schedule, a checklist item on a Knowledge page or a meeting summary: each one creates a real action that knows where it came from.

1. From a message's menu: “Create a task from this message”
2. From My Network: “Remind me to follow up” creates an action with a reminder
3. From a recurring schedule: each occurrence can have its own action
4. From a Knowledge page: a checklist item linked to an action closes the action when it's checked
5. From a meeting: the summary's action items become actions

Two parallel modes: personal and workspace

Everything you create in Flowra belongs either to you or to a workspace. Personal mode has no members and nobody but you sees it. A workspace has members, roles and rules about access. The dashboards of the two are deliberately identical: the same action board, the same calendar, the same finances. Only the scope differs.

This means you never have to choose between «a personal tool» and «a team tool», or carry data from one into the other. You switch between modes from /select, and the same habits work in both.

Money and work in one place, not two

Flowra's ledger is not a separate module sitting next to the tasks. A transaction can be attached to an action, a project or a contract milestone, and at that moment a cost stops being a number in a table and becomes «what this piece of work cost».

That is why money can be seen and recorded from anywhere in the app: from an action, from a project, from a contract, or from the ledger itself. Where you record it only decides which relation is filled in for you; the record is the same one.

Rules that hold everywhere

A few rules hold across the whole product, and knowing them shortens the rest of the documentation. The ledger is never hard-deleted: deleting voids and audits. Every change to an action is written into its own history. A plan's ceiling stops you adding, never keeps you from holding. And access is never decided by the client; the server always decides for itself.

There's one more rule: Flowra never shows something as built when it isn't built yet. A connector that isn't ready is labeled “Coming soon” and moves no data.

How the documentation is organized

The documentation is split into nine groups, and each section has its own route. The order of the sidebar is the suggested reading order, but every page is written to stand on its own and you can jump straight into it. At the top of each page, the “What this is wired to” section tells you which other sections it's connected to.

1. Getting started: this page, plus workspaces, projects and access
2. Daily work: actions, calendar, recurring schedules, meetings
3. Docs and Knowledge: Knowledge, collaborating on Knowledge, My Files, Folio
4. Communication and chat: chat, mentions and notifications
5. Network and sales: My Network, Collaboration opportunities
6. Finance: ledger, accounts, contracts, payroll and commitments
7. Connectors: Connectors hub, MCP and AI agents, cloud connectors, Telegram
8. Settings and account: settings, subscription and plan, security
9. AI: Flowra Assistant, meeting intelligence