How-to
These articles walk you through the everyday tasks in Floxar, from signing in to building content and running it. You learn how to create bits, connect them into flows, run and track trails, and work with references in the process library. If you administer an account, you also find how to invite people, grant roles and manage account settings.
Getting started: from a new account to your first flow
This walkthrough takes you from nothing to a working flow that you have run once. It has one shared start, then two paths: building your first flow with an AI client you already use, or building it yourself in the Floxar website. Both end in the same place.
Signing in and authentication
You use Floxar with a personal Floxar sign-in tied to your email address. This article covers signing in, verifying your email as a new user, what to do when you cannot sign in, and how sessions behave.
Seeing and disconnecting your AI clients
To see the AI clients you have connected to Floxar, open your profile's Security page: Your MCP connections lists every one, in every account. To disconnect one, choose Disconnect on its row; only that connection ends. Disconnect applications ends them all at once.
Creating and editing bits
Bits are the smallest building blocks of content in Floxar. Each bit is a single, self-contained process step that combines rich text, media, and interactive elements that can capture input from the person working through it. This article covers what a bit contains, what the editor can do, and how bits relate to flows.
The bit editor
The bit editor is where a bit's content is written: its text and media, its interactive elements and its connections to the next steps. This article explains how to open it, how it is laid out, how it saves your work into the bit's draft and how you publish it. For what a bit can contain, see Creating and editing bits; for every element and its settings, see Interactive elements and their settings.
Interactive elements and their settings
Interactive elements are the parts of a bit that the person or agent running a step fills in: a checklist to tick, a choice to make, a date to pick, text to write. They are what turn a step from something you read into something you do, and every answer is recorded on the trail. This article lists every element, what it is for, the settings you can give it, and what it records. For adding content to a bit in general, see Creating and editing bits; for when an element is worth adding at all, see Writing effective bits.
Bit connections
A bit connection links one step to a possible next step. Connections are what turn separate bits into a process: a flow is its starting bit and every bit you can reach from it by following connections. A step with one connection simply continues; a step with several is a decision point, where whoever runs the flow chooses the path.
Building flows
A flow is a navigable sequence of connected bits — the template for a process that people run step by step. You build a flow by choosing where it starts and connecting bits into paths, including branching paths where the person's choice determines what comes next. This article covers flow setup, connections, how navigation works for the person running the flow, and the editing rules that keep flows consistent.
Running and tracking trails
A trail is the record of one run through a flow: which steps were visited, in what order, what was entered at each step, and what happened to the run along the way. When you start a flow, Floxar creates a trail for you and keeps it as a complete, reviewable history of that piece of work. This article covers starting a trail, moving through it, how your answers are saved, and what the finished record contains.
Creating trails in bulk with the Workload Generator
The Workload Generator turns a spreadsheet into trails. Each row of the file becomes one real piece of work: a trail on the flow the row names, already on that flow's first step, assigned to the person the row names or waiting in the queue for whoever is free. It is the fastest way to put a whole list of work in front of a team, and every trail it creates is tracked from its first step to its last like any other.
The Live Flow View
The Live view puts a flow's work on the flow itself. It draws the flow as a diagram and shows, on every bit, how many open trails are sitting there right now, which of them are stuck, and who is running them. Switch to Trends and the same diagram shows where work went over the last hour, day, week or month, and where it dropped off. It is built for the person responsible for a flow: it answers "where is the work, and what needs attention?" without paging through trails one by one.
References and the process library
A reference is a read-only supporting document — a policy, guideline, definition, FAQ, or decision matrix that people may need to consult while working through a flow. Where a bit tells you what to do, a reference holds the why, the what-if, and the background. This article covers what references are for, how they support bits and flows, and how the process library and search surface them.
Inviting users, roles, and permissions
Every person in a Floxar account has a permission level that controls what they can see and do. This article explains what each level means, how new people join an account, and how access flows through the account's organizations and groups.
Account settings and administration
Account administrators keep a Floxar account organized: they shape its structure, manage its people, and set account-wide options. This article gives a conceptual overview of what account administration covers. You need the Admin permission level on the account to do these things.
MCP usage
The Usage tab of the MCP page in Account Settings shows how your account is used through MCP: by agents your account registered, and by the AI clients people connected, such as Claude, ChatGPT or Cursor. It counts requests, tool calls, refusals and limits over a period you choose. It is read-only: nothing on it changes a setting, a limit or a connection.