Frequently asked questions
Short answers to the questions people ask most, each with a link to the full explanation.
About Floxar
What is Floxar?
Floxar turns the way your team works into processes that people and AI agents run step by step, with a record of every run. Instead of a procedure people read and remember, you have a flow they follow. See What is Floxar?
Who is Floxar for?
Any team whose repeatable work has to be done reliably and the same way every time, by people, by AI agents, or by both: support, operations, finance, people teams, IT and others.
How is Floxar different from a wiki or a knowledge base?
A wiki holds documents people read; Floxar holds procedures people and agents carry out. Your documentation can stay where it is; the part that describes how work is done becomes something you run, with a record of each run. See Floxar, documentation and knowledge.
What are bits, flows, trails and references?
A bit is one step. A flow is bits connected into a process. A trail is one run of a flow. A reference is supporting material linked to steps. See What is Floxar?
Building processes
How do I create a flow?
Write its steps as bits, connect them, and choose a starting bit. You can also have the Flow Designer or your own AI client draft it. See Building flows and The bit editor.
What can a step ask for?
Checklists, choices, dates, free text, searchable lists, links and video. Each can be required, and choices can decide which next step is available. See Interactive elements and their settings and Bit connections.
If I change a bit, what happens to the flows that use it?
A bit is the same in every flow that uses it, so a change appears in all of them at once. Trails in progress follow the current content. See The bit editor.
Can we version our content and test it before it goes live?
Yes, with a test account and your own repository, using an AI agent to promote approved changes. Built-in versions for bits are coming. See Version control and promoting content.
Running work
How do I get started?
Create an account, then build your first flow with your AI client or in the website, and run it once. See Getting started.
How do we route work to the right team?
With categories on trails. Label work, for example night-shift or tier-2, change the labels as cases progress, and let each team or agent filter the queue for its own work. See Organizing work with categories.
Can I stop partway through and come back?
Yes. A trail can be paused and resumed, transferred to a colleague, or released to a shared queue. See Running and tracking trails.
What does Floxar record about a run?
Each step visited, in order and with times, every answer given, who did each step, every hand-off, and how the run ended. See Running and tracking trails.
AI and agents
Can AI agents run our processes?
Yes. An agent runs the same flows as people, one step at a time, choosing among the paths your authors defined, and people and agents can hand a run to each other at any step. See Where Floxar fits in an AI stack.
Does Floxar provide the AI model?
Floxar's own AI features, the AI Assistant and the Flow Designer, are built in. Agents that run your work use the models you choose; Floxar provides the process, the permissions and the record. See Registering an agent.
Are we tied to one AI provider or model?
No. Your processes and their history live in Floxar, and the agents that run them use the providers and models you choose, which you can change at any time. You can also use different models for different work, by a step's complexity or a flow's priority and categories. See Choosing AI providers and models.
Can I use Floxar from my own AI client?
Yes. People can connect supported AI clients to their account and read, run and write content within their own permissions. See Connecting an AI client.
What is the difference between an agent and an AI client?
An AI client acts for a person who signed in, with that person's permissions. An agent is software registered by your account that works under its own identity. See Agents and AI clients.
Is there a ready-made agent for running flows?
The Operator, coming soon, will run your flows and hand work to people when it should. See The Operator.
Data and security
Can Floxar see the credentials our agents use?
No. Credentials kept in the Secrets Vault are encrypted so that Floxar itself can never read them; only the agents you grant access can. See The Secrets Vault.
Who can see and change our content?
Your account's members, according to the role each has at each level of your organization. See Inviting users, roles, and permissions.
Is there a record of who changed what?
Yes. Changes to content are recorded, and administrators can review them in the account's audit. See Account settings and administration.
Last reviewed: 2026-10-06