Fluo glossary
The Fluo glossary briefly explains the terms you see in the app and in the help center. Terms are grouped by topic and listed alphabetically within each group.
Spaces and roles
Admin—a role in a Fluo team space: an admin manages the space, its members and projects almost like the owner. An admin can't delete the space, start or cancel a subscription, or change another admin's role.
Learn more: “Roles: owner, admin, member and guest”.
Guest—a view-only role in Fluo: a guest sees the projects, tasks and articles open to them but can't change anything or post in a task chat. Guests don't take a seat in the subscription.
Learn more: “Roles: owner, admin, member and guest”.
Member—a role in a Fluo team space for everyday work: a member sees all of the team's projects and creates and edits projects, tasks and articles, but can't invite people. Every member takes a seat in the subscription.
Learn more: “Roles: owner, admin, member and guest”.
Owner—the role of the person who created a team space in Fluo. A space has exactly one owner, who can do everything, including subscribing to a plan and deleting the space.
Learn more: “Roles: owner, admin, member and guest”.
Personal space—your own space in Fluo, created when you sign up: your personal plan (Free or Pro) applies there, and only you can see its projects. In the sidebar, it's labeled “My projects”.
Learn more: “Personal and team spaces: what's the difference”.
Space—the place in Fluo where your projects live. There are personal spaces and team spaces, and each has its own plan.
Learn more: “Personal and team spaces: what's the difference”.
Team space—a Fluo space for working together, with members in different roles and its own name, color and plan, Free Team or Business. You create one with the “Add a team” button in the sidebar.
Learn more: “Personal and team spaces: what's the difference”.
Projects and sections
Epic—a part of the project plan on a Fluo roadmap: a bar with start and end dates and a progress percentage. Tasks from the project's boards are linked to an epic in the task window, in the “Epic” field.
Extended project—a Fluo project with a second section added to it. It gets an “Overview” page, section tabs and, if the project has a board, a “Workflow” tab.
Learn more: “Simple and extended projects: how a project grows”.
Knowledge base—a project section in Fluo with articles and folders, where guidelines, instructions and notes sit next to your tasks. Articles are written in the block editor or in Markdown.
Learn more: “Projects and sections: how work is organized”.
Project—a set of boards, knowledge bases and roadmaps on one topic, such as launching a website or releasing an app. In Fluo, every project belongs to one space.
Learn more: “Projects and sections: how work is organized”.
Roadmap—a project section in Fluo with a Gantt chart that lays out the project's epics over time. You move epics on the roadmap with the mouse and connect them with dependencies.
Learn more: “Projects and sections: how work is organized”.
Section—a board, knowledge base or roadmap inside a Fluo project. Plans limit the number of sections in a space, not the number of projects.
Learn more: “Projects and sections: how work is organized”.
Service desk—a Fluo channel through which people outside your team send you tickets: customers, contractors and colleagues from other departments. Every ticket becomes a project task: it waits in the service desk's queue first and then goes to a board.
Simple project—a Fluo project with one section: a board, a knowledge base or a roadmap. Opening it takes you straight to that section, and the interface labels such a project by the section type, for example “Board project” or “Roadmap project”.
Learn more: “Simple and extended projects: how a project grows”.
Boards and tasks
Assignee—the person responsible for a task in Fluo. A task has only one assignee, and Fluo assigns a new task to the person who creates it.
Learn more: “Assignee, deadline and priority”.
Blocker—a mark on a task card in Fluo with a short reason: work has stopped (“Full stop”) or slowed down (“Impediment”). You can set blockers in team spaces on the Business plan.
Learn more: “Blockers: how to mark a task as blocked”.
Board—a project section in Fluo where tasks sit in columns, and each column stands for a task status. Move a card to another column, and the task's status changes.
Learn more: “Boards, columns and statuses”.
Column—a vertical list on a Fluo board that sets the task's status: whatever column a card sits in, that's the task's status. On the free plans, a board can have up to 8 columns.
Learn more: “Boards, columns and statuses”.
Deadline—a task's due date and time in Fluo, set in the “Deadline” field of the task window. The deadline puts the task in “Today” and “Upcoming”, and once it has passed, among overdue tasks.
Learn more: “Assignee, deadline and priority”.
Related tasks—tasks in Fluo linked by the order of work: a next task starts after the previous one, and parallel tasks run at the same time. You can link tasks, including tasks on different boards, in team spaces on the Business plan.
Learn more: “Related tasks and task chains”.
Status—the stage a task is at in Fluo, that is, the board column the task sits in. A status doesn't close the task by itself: you mark the task as done with the circle on its card.
Learn more: “Boards, columns and statuses”.
Task—one piece of work in Fluo with a title, an assignee, a deadline and its own chat. A task sits in a board column, and a task noted down without a project stays in “Inbox” until it's moved to a board.
Learn more: “The task window: what's in it”.
Task limit (WIP)—a column's WIP limit in Fluo, the maximum number of open tasks that can sit in the column at the same time. On the Pro and Business plans, a limit is either a signal limit, which only warns you, or a strict limit, which keeps extra tasks out.
Learn more: “Column task limit (WIP)”.
Workflows and routes
Check—a checklist item with assigned people that a status automation or a link rule adds to a task in Fluo. Until the check is ticked off, the task can't leave the board onward, but it can be returned back. A check holds the task only on Business and during its trial.
Learn more: “Conditions and checks: what holds a task”.
Connector—a node of the Fluo workflow map through which tasks pass between projects: a link leads from a column into the connector and from the connector into a column of another project. The “Task types at the exit” table sets which type the task gets on the way out. Connectors are available on the Pro and Business plans.
Learn more: “Connectors: passing tasks between projects”.
Fork—a diamond on the Fluo workflow map with one input and several branches. A task takes the first branch whose condition is met, and the last branch, “Otherwise”, takes all other tasks.
Learn more: “Branches: different paths by condition”.
Handed off—a button on a Fluo board with the number of tasks that left this board further along the route and aren't closed yet, for example “3 tasks handed off”. Its panel shows the board and column where each task is now.
Learn more: “‘Handed off’: where tasks that left the board are now”.
Link—a line on the Fluo workflow map from a column to another column of the same or another board, or from a service desk or a connector. A task moves along its route by links, and a link can move a task by itself and have its own rules.
Learn more: “How to connect columns of different boards”.
Link rules—conditions, checks and actions that work only when a task is moved along this link. They add up with the status automations, and the assignee, deadline and type from the link take priority over those from the status automations. They work in team spaces on the Business plan.
Learn more: “Link rules: conditions and actions on the way”.
Project workflow—the map on the “Workflow” tab of an extended project in Fluo: boards with their columns, service desks, connectors, forks and links. The map shows one route at a time, and you choose it with the “Route: …” button above the map.
Learn more: “Project workflow: task routes and task types”.
Return—moving a task in Fluo back to a column where it has already been. A return asks for a comment, after it the task doesn't move on by itself, and the marks on the checks of the board it was returned from are reset. Undoing a move with “Undo” in the notification within 5 minutes isn't a return.
Learn more: “How a task moves along its route”.
Route—the set of links between board columns that tasks of one type follow in Fluo. Each task type has its own route, tasks without a type follow the “No type” route, and a link belongs to one route only.
Learn more: “Project workflow: task routes and task types”.
Status automations—automation of a status in Fluo, that is, of a board column: conditions, checks and actions applied to a task when it arrives in the column or leaves it, along any link or without one. Fluo performs the actions by itself: it sets the assignee, sets a deadline, changes the type or closes the task. You open the “Status automations” window with the item of the same name in the column menu. Status automations work in team spaces on the Business plan; on Free Team, they are view-only.
Learn more: “Status automations: actions on entry and exit”.
Task type—a kind of task in a Fluo project, such as “Contract” or “Bug”, with its own name, icon and color. A task follows the route of its type, and a new task is created with “No type” by default. You can set an existing type on a task on any plan, and create, rename and delete types on Pro and Business.
Learn more: “Task types: create, choose, change”.
Personal lists
Inbox—your personal list in Fluo of tasks noted down without a project and not yet sorted onto boards. Once you know which project a task belongs to, you move it to a board.
Learn more: “Inbox: capture tasks quickly and sort them onto boards”.
Today—your personal list in Fluo of tasks due today from all your spaces, with overdue tasks at the top. You don't add tasks to it separately: a task gets here through its deadline.
Learn more: “Today: your plan for the day”.
Upcoming—your personal list in Fluo that arranges your tasks with a deadline by day for a year ahead. Drag a task to another day, and its deadline changes to that day.
Learn more: “Upcoming: tasks day by day”.
Plans and billing
Business plan—the paid plan for a team space in Fluo, with any number of members and payment per seat. Status automations, link rules, blockers, related tasks and time tracking work only on Business.
Learn more: “Fluo plans and feature comparison”.
Free plan—the free plan for your personal space in Fluo, with no time limit. It includes up to 5 sections and up to 8 columns per board.
Learn more: “Fluo plans and feature comparison”.
Free Team plan—the free plan for a team space in Fluo with up to 5 members, including the owner. An owner can have only one free team.
Learn more: “Fluo plans and feature comparison”.
Paused Pro—your own paid Pro subscription in Fluo, on hold while you have Pro from your team; the remaining days are kept and start running again when the team-provided Pro ends. The “Pro paused” label also appears when a Pro renewal invoice hasn't been paid: pay it within 30 days after the period ends, and the plan comes back at the same price.
Learn more: “Personal and team plans: what applies where”.
Pro from your team—the Pro plan in your personal Fluo space that you get for free when you take a seat in a team on Business or on a Business trial. The “Billing” tab of your profile then says “Pro is provided by your team”.
Learn more: “Personal and team plans: what applies where”.
Pro plan—the paid plan for your personal space in Fluo: up to 300 sections, files in tasks, column task limits and connectors between your own projects. A 14-day Pro trial starts automatically when you sign up, and no card is needed.
Learn more: “Fluo plans and feature comparison”.
Seat—one person's right to work in a Fluo team space as the owner, an admin or a member. On Business, every seat is paid for, Free Team has 5 seats, and guests don't take a seat.
Learn more: “Business seats: who takes a seat and how to change the number of seats”.
FluoAI and AI assistants
Connected AI assistants (MCP)—Claude, ChatGPT, Cursor and other external assistants that work with the tasks, boards and knowledge base of one Fluo space on your behalf through the MCP protocol. The “Connector address” for connecting them and the list of assistants with the “Disconnect” button are in your profile, on the “API” tab.
Sparks—the units Fluo uses to charge for FluoAI, its AI assistant: each answer costs sparks, and its price is shown under it. Paid Pro and Business plans add sparks every month, and spark packs can be bought separately on any plan.
Learn more: “Fluo plans and feature comparison”.
FluoAI—the AI assistant built into Fluo: it answers questions about your tasks, projects and articles, changes tasks when you ask and runs scheduled routines. FluoAI works with the permissions of the person asking and spends sparks.
Learn more: “Quick questions on each screen”.
Related articles
Related articles
- Inbox: capture tasks quickly and sort them onto boards
- Today: your plan for the day
- Upcoming: tasks day by day
- The task window: what's in it
- Assignee, deadline and priority
- Blockers: how to mark a task as blocked
- Related tasks and task chains
- Roles: owner, admin, member and guest
- Simple and extended projects: how a project grows
- Column task limit (WIP)
- Project workflow: task routes and task types
- How to connect columns of different boards
- How a task moves along its route
- Task types: create, choose, change
- Connectors: passing tasks between projects
- Status automations: actions on entry and exit
- Conditions and checks: what holds a task
- Quick questions on each screen
- Personal and team plans: what applies where
- Business seats: who takes a seat and how to change the number of seats
- Link rules: conditions and actions on the way
- Branches: different paths by condition
- “Handed off”: where tasks that left the board are now