Getting StartedCore Concepts

Core Concepts

The ideas the rest of the docs build on - the Outcome Algorithm, IP Security, Apps and Members, tools and Steps, access, knowledge, Assets and Credits.

The Ideas Behind ThoughtFlow

A handful of ideas run through everything in ThoughtFlow. This page starts with the Outcome Algorithm, the idea behind the product, and IP Security, which protects what you put into it. Then it explains the terms the rest of the docs use. For quick definitions, see the Glossary.

The Outcome Algorithm

ThoughtFlow tools produce outcomes that matter to your clients, not just AI output. That's because three things work together each time AI does work in one of your tools:

  • The right context. Your knowledge, each Member's User Knowledge, and the results of earlier Steps in the tool.
  • The right instructions. You plan them in Builder AI by answering questions about your clients and how you help them. Spark writes them from your answers.
  • The Member's input where it matters. Their answers to your questions, and their review of results at the points you choose.

The rest of these docs show where each one comes from: Universal Knowledge for context, Your First Tool for instructions, and Human Review for the Member's review.

IP Security

IP Security protects your App's agent instructions and knowledge from extraction attempts by Members. It's set for each App, and it's on by default if your plan includes it. You find it in App Settings > Account and Branding.

If you turn it off, ThoughtFlow asks you to confirm first, because every agent and workflow in the App will then be able to reveal its instructions, prompts and knowledge sources to Members. See IP Security.

Organizations, Apps and Members

ThoughtFlow has three levels:

  • Organization: your business on ThoughtFlow. It holds your plan, billing and Credits.
  • App: where your tools live and your Members use them. An Organization can have more than one App, and each App has its own tools, Members and settings.
  • Member: someone who uses the tools in your App, such as a client or student.

Builder AI is separate from all of this. It's an App ThoughtFlow provides to help you plan and build your tools. It isn't one of your Apps, and it doesn't count toward the Apps your plan includes. You can still open it from the App switcher.

Builders and Roles

A Builder is anyone who creates and manages tools. Your role decides what you can do:

LevelRoleWhat it covers
OrganizationOwnerOwns the Organization. Manages the plan and billing, and can do everything an App Admin can in every App.
OrganizationAdminHelps run the Organization. Can do everything an App Admin can in every App, and sees Org Management and Billing. Some settings, such as updating the payment method, are for the Owner only.
AppAdminBuilds tools and manages everything in the App, including Members, Access Groups and the App's settings. In these docs, an App Admin.
AppEditorBuilds and manages tools and knowledge in the App. In these docs, an App Editor.
AppMemberUses the tools they have access to.

See Team Roles for the full details.

Tools: Agents and Workflows

Everything you build is a tool. As a Builder, you work with two kinds:

  • Agent: a single-step AI tool. A form agent asks for inputs and returns a result. A chat agent has a conversation.
  • Workflow: a tool with several Steps, run in order.

Your Members never see this difference. To them, everything is a tool.

Steps

A workflow is made of Steps. Some Steps ask the Member for something, like a Human Input step with questions to answer. Others do work, like an Agent step that writes a draft.

Each Step has its own settings. One of them, on an Agent step, is Pause for Human Review: the workflow stops so the Member sees that Step's result and can review it before the workflow continues. Without it, the Step runs in the background. See Human Review.

Drafts and Published Tools

A tool you create, or that Spark builds for you, starts as a draft. You can test a draft as much as you like. Members can't see it.

When the tool is ready, you publish it. Even then, Members only see it if they have access to it.

Who Can See a Tool

Every tool has a Visibility setting:

VisibilityWhat Members seeUse it for
OpenEvery Member can see and run it.Tools every Member should have.
PrivateEvery Member sees that the tool exists, with its name and a lock, but only Members with access can open it.Showing Members what they could get, such as by upgrading or joining a program.
SecretOnly Members with access know it exists.Tools meant for a specific program, group or client.

New tools start as Secret.

Content Bundles and Access Groups

Two separate systems decide how Members find tools and which ones they can use:

  • Content Bundles organize what Members see. They're the folders in the sidebar Library and the groups on Home.
  • Access Groups decide who can use what. You give a group permission to a tool or a whole Content Bundle, then add Members to the group.

The two are independent. A Content Bundle doesn't grant access on its own, and an Access Group doesn't change how tools are organized. You can map them together in any combination. See Content Bundles and Access Groups.

Universal Knowledge

Your tools work from two kinds of knowledge, together called Universal Knowledge:

  • Agent Knowledge: what you know, saved once and used by your tools. It's the same for every Member.
  • User Knowledge: facts about each Member, like their business or audience. You decide which fields to ask for. Each Member fills them in once, and tools use their answers automatically.

See Universal Knowledge.

Assets and Activity

  • Assets are saved results from tools. Builder AI saves results such as your AI-Assisted Outcomes List and your Tool Visions as Assets, and Tool Designer's plan goes to Spark. Your Members' results are saved as Assets too.
  • Activity lists runs and chats, so you or your Members can pick up where you left off or look back at a finished run.

See Activity and Assets.

Credits

Credits pay for AI work. They're used when anyone runs your tools, including you when you test them, and when you upload video or audio to be transcribed into knowledge. Planning in Builder AI and building with Spark don't use Credits. See Credits.