Glossary

The words Floxar uses, in alphabetical order, each with a link to where it is explained in full.

Abandon. End a trail without finishing it, optionally with a closing reason. See Running and tracking trails.

Account. Your organization's space in Floxar: its content, its people and agents, and its settings. Accounts are independent of each other. See Organizations, groups, and scopes.

Agent. Software registered by your account that works in Floxar under its own identity and role, for example to run flows. See Registering an agent.

AI Assistant. Floxar's built-in assistant that answers questions from your content and about Floxar, and never changes anything. See The AI Assistant.

AI client. An AI application a person connects to their Floxar account, such as a chat or coding assistant, which then acts with that person's permissions. See Connecting an AI client.

Bit. One step of a process: a focused piece of content with the interactive elements that step needs. A bit can be part of several flows. See What is Floxar?

Bit connection. A link from one bit to a possible next step, shown in the bit as a next-step card. See Bit connections.

Category. A label of your choosing on a flow, bit, reference or trail, used to organize, filter and route work. See Organizing work with categories.

Claim. Take a trail from the queue so that it is assigned to you. See Running and tracking trails.

Closing reason. The reason recorded when a trail is completed or abandoned.

Complete. Finish a trail at its last step.

Complexity. A bit's setting, Low, Medium or High, saying how much reasoning effort an AI agent should invest in the step. See Choosing AI providers and models.

Conditional connection. A bit connection that can be taken only after a certain answer on its step. See Bit connections.

Credential. A key or password an agent needs for another system, kept in the Secrets Vault. See The Secrets Vault.

Flow. A process: bits connected from a starting bit, which people and agents run step by step. See Building flows.

Flow Designer. Floxar's built-in AI that drafts new flows and improvements to existing ones as proposals for you to accept. See The Flow Designer.

Group. A part of an organization, such as a team, with its own content and permissions. See Organizations, groups, and scopes.

Hand-off. Passing a trail to someone else partway through, between people, agents, or both.

Interactive element. Something a step asks for and records: a checklist, a choice, a date, text, a searchable list, a link or a video. See Interactive elements and their settings.

Operator. Floxar's ready-made agent for running flows, coming soon. See The Operator.

Organization. A division of your account, with its own groups, content and permissions. See Organizations, groups, and scopes.

Pause. Set a trail aside to resume later.

Priority. The urgency of a flow or trail: low, medium, high or critical.

Queue. The shared list of trails waiting for someone to claim them. See Running and tracking trails.

Reference. Read-only supporting material, such as a policy or a definition, linked to the steps that rely on it. See References and the process library.

Release. Put a trail back in the queue for someone else to claim.

Required element. An interactive element that must be answered before the trail can move on from its step. See Interactive elements and their settings.

Scope. The level you are working at, the whole account, an organization or a group, which decides what you see and file. See Organizations, groups, and scopes.

Secrets Vault. Where credentials for your agents are kept, encrypted so that Floxar itself can never read them. See The Secrets Vault.

SLA target. The time a step is expected to take, set in the bit's properties.

Starting bit. The first step of a flow, where every run begins.

Task. A personal to-do in Floxar, separate from flows and trails. See Navigating Floxar.

Test account. An account marked as a test account in its settings, used to try content away from real work. See Version control and promoting content.

Trail. One run of a flow, with the record of every step, answer and hand-off. See Running and tracking trails.

Transfer. Hand a trail directly to a named person.

Worklist. Where you continue your open trails and start new ones. See Navigating Floxar.

Last reviewed: 2026-10-06