Everything you have asked, in one place.

Flowra gathers work around the action. Every action carries its own owner, due date, priority, status and checklist, and everything that belongs to it stays beside it: the comments, the meeting you booked for it, the files that changed hands, the contract behind it and the transactions that moved because of it. The result is that understanding where a piece of work stands never means hunting through several tools - it is all on the work itself, and its history is recorded.

An ordinary task manager keeps a title and a checkbox; the rest of the story scatters across email, chat and a drive. Flowra keeps the context too, and writes every change into the action's own history: who reassigned it, when the date moved, which file was attached, which decision came out of which meeting. Three months later, when somebody asks why something happened, the answer is not a guess.

Both, and without them mixing. You get a personal space only you can see, plus as many team workspaces as you need; each one has its own members, projects, files and ledger. Switching between them is one click, and nothing leaks from one into another.

No, and you do not have to decide all at once. Start with the actions and leave the rest where it is: meetings can stay on your own Google Meet or Zoom, files on Drive or Dropbox, the calendar on Google Calendar. Flowra connects to those, so every tool whose context you bring here is one fewer place to switch to rather than a migration.

Create an account and your personal space is ready that moment, so you can file your first action straight away. For team work, create a workspace, set up your projects and invite your teammates by email. Anybody without an account gets a sign-up link, and their invitation is waiting the instant the account exists.

An owner, a due date, a priority, a status and a checklist; comments and mentions; attached files; the meetings tied to it; and links to contracts and transactions. Beside all of that runs a history that misses nothing, from a change of owner to a moved deadline. Opening an action means seeing the whole story, not a line of text.

By three things: workspace, project and label. An action is either personal or belongs to a project inside a workspace, and access follows from exactly that - somebody without access to the project never sees the action at all. Labels are for the other cuts: kind of work, client, campaign or whatever you actually need.

Yes. Every action carries its own checklist for the small steps that do not need an owner of their own, and for the parts that do need their own owner and date you create separate actions against the same project. That is how a large piece of work breaks into things somebody can actually finish.

Yes, over seven days, thirty days, six months and a year, grouped and filtered by person. You can export it to CSV or copy the whole list to the clipboard in one tap, which is usually all a weekly report or a review meeting needs.

There are three: owner, editor and viewer. A viewer only reads, an editor creates and changes work, and an owner runs the workspace - members, projects and the subscription are theirs. If you do not want somebody seeing the whole space, invite them to a single project instead and that is all they will see.

You invite by email. If they already have an account the invitation lands in their approvals, and accepting it is what actually puts them in the workspace. If they do not, they get a sign-up link and the invitation is waiting the moment their account exists - you never have to send it twice.

They stay. Removing access means that person can no longer see anything, not that the actions, comments and files they made are deleted; the history stays intact too. Whatever was assigned to them can simply be reassigned.

A mention is a username and always raises a notification, whether it sits in a chat or on an action's comments - a mention is addressed at somebody, so it is never folded into a daily digest. If a person cannot open that work or that conversation, the mention leaks nothing and raises nothing at all.

Three things. First, every file stays beside the work it arrived for, so you can find it from the work rather than only by its name. Second, sharing is person by person and a file's address is never public - permission is checked every time somebody opens one. Third, files are grouped by what they actually are and are searchable, and you can see how much space each format is taking.

For 21 days, yes. Deleting is soft: the file leaves the list but sits in the trash and comes back whenever you want it. Deleting for good has its own separate path, and it warns you first that this one does not come back.

Yes - a real connection, authorised from the service itself. A dedicated folder called «Flowra» is created in your own account and files stay in step between the two sides; the boundary is visible and the rest of your cloud is never touched. Dropbox syncs both ways. With Drive, sending from here always works, but seeing files you dropped into that folder yourself needs the full scope, which Google classes as restricted.

Never. If you delete a file on the other side it leaves the list here but goes to the trash and can be restored - a sync that destroys something for good is not a sync. Nothing travels the other way: Flowra never removes anything from your Drive or Dropbox.

Either, and it is your choice. Flowra has its own video room with screen sharing, recording and live chat. If you have connected Google Calendar or Zoom, the link is minted there instead - and wherever you open that meeting from, it hands you that link rather than an empty room.

Into your files, shared with everybody who was in the meeting. That is deliberate: a recording belongs to everyone who was invited, not only to the host, so it shows up in their shared items too. It records the screen, with the microphone and the screen's own audio mixed together.

Yes, and that is the main difference. Every action has its own comments and mentions, and every meeting has a real thread that outlives the call - what was said in the room is still there the next time the meeting is opened. Direct messages exist too, but anything that belongs to a piece of work stays on that work.

Yes, on the Prime plan. The transcript is built with timestamps, so clicking a line jumps the video to that moment; then you get a summary and a list of suggested action items, each of which becomes a real action in one click, assigned to somebody who was actually in the meeting.

Accounts and cards in their own currencies, transactions with categories and labels, transfers between accounts, salaries and recurring obligations, and reports built from exactly those. Balances and cash flow are calculated rather than typed in, so nothing is quietly left out.

No, and that is on purpose. Deleting a transaction voids it and leaves its trace in the audit log; the ledger is never hard-deleted. The reason is simple: a ledger you can make something vanish from is a ledger nobody can rely on.

A contract hangs off a project and carries its own milestones. A milestone counts as paid only when you link a transaction to it - nothing is matched by amount or date, because a coincidence should never mark an invoice settled. What has been received, and where the contract stands, are derived from those links.

Whichever ones you define. Each account has its own currency, and so do shared and team accounts - you can keep a separate wallet per currency, and the reports are built per currency too.

An A4 sheet you design yourself: a contract, a receipt, a sign-up form or any document you need. You place the fields on the page and mark who fills each one - you or the other side. Start from a blank sheet or from a ready-made template.

No. You send them a guest link and they see only the fields you marked for them, fill those in and sign - with no account to create and no sight of anything else of yours. For somebody who was never going to be a regular user, that is the whole interaction.

The printable export lands in a folder named after the sheet, inside your own files, so the archive keeps itself tidy. A change history is kept as well, so you can see what moved between rounds and who filled in what.

Yes, and not only in the interface. Flowra ships in more than one language and in both reading directions, and dates follow the calendar you pick - on actions, on reports, on transactions and even in the CSV exports. Switching is one click and your choice is remembered.

In layers. A lock screen with a passcode for when you step away; a list of live sessions you can end one at a time; and a session that expires by itself after 30 days. Changing a password or freezing an account closes every live session at once. Failed sign-ins are counted too, so guessing at a password cannot go on for ever.

In Flowra's own database, with files in private storage. File addresses are never public: every time somebody opens one, their permission is checked first, and the temporary link that gets created lives for a few minutes at most.

Yes. Reports and lists export to CSV, a finished sheet lands in your own files as a printable document, and every file you uploaded is always downloadable. Nothing is stored in a shape that can only be read from inside Flowra.

One workspace, up to three people with access (you and two others), and 2 GB of file storage. All the core capabilities are there - actions, projects, meetings, chat, files, sheets and the ledger. What the paid plans add is capacity, and the AI features.

No. A plan belongs to your account rather than to a workspace, and every space you own runs on it. Since the paid plans carry unlimited workspaces, charging per space would mean selling the same thing several times over.

A seat is one person with access, and you hold one of them. Somebody who appears in several of your workspaces is counted once, and a guest with access to a single project is still a seat, because they can reach your data. If the team grows past the plan's seats, each extra person adds the price of that one person.

No member and no file is removed. A plan's limit is a ceiling on adding, never a reason to take something away: the workspace keeps everybody it has and you simply cannot invite the next person. Evicting people because an invoice ran out would destroy work.

At checkout, in dollars, or with a gift code issued to you. Every attempt to pay, successful or not, lands as a row in your payment history, so if something stops halfway you can see where it stood.

Yes, and cancelling means «do not renew», not «cut it off now». The period you paid for runs to its end, and you can turn renewal back on whenever you change your mind. Renewing early does not waste the days you have left either - they stack onto the next period.