Dashboard Overview

The Floe dashboard is where you configure everything: your products, the AI agent's knowledge, demo settings, and session intelligence. Here's what each section does and when you'll use it.

Sites

Sites are the top-level container. Each site represents one product or application. When you open the dashboard, you land on the Sites list.

Click into a site to access everything related to that product: content, exploration data, capabilities, plans, and demo sessions. If you manage multiple products, each one gets its own site. See Sites for details.

Ingestion

The Ingestion tab inside a site is where you add content sources. This is how Floe learns what your product does.

You add configs pointing to your docs, knowledge base, videos, and other content. Each config shows its processing status (pending, processing, completed, failed). Most teams start with their docs site and expand from there.

See Ingestion for supported content types and configuration.

Content

The Content tab shows what Floe has ingested and indexed. It's the library of everything the AI agent can reference during conversations.

Use this tab to verify that your content was processed correctly. You can see individual articles, their source URLs, and when they were last updated. If the agent says something inaccurate during a demo, this is where you check whether the source material is correct or needs updating.

Explorer

The Explorer tab shows the screens and navigation paths Floe discovered when it navigated your product. Think of it as Floe's map of your UI.

After running exploration, you'll see each screen Floe visited, the interactive elements it found, and how screens connect to each other. This data powers the agent's ability to navigate your product during demos and onboarding.

You'll come back here when you ship UI changes and need to update Floe's understanding. See Exploration.

Knowledge

The Knowledge tab is where you review what Floe's research pipeline extracted from your content and screens. It shows topics, features, screen associations, and content coverage.

This is the "did Floe get it right?" checkpoint. If a topic shows low coverage or a feature is associated with the wrong screen, you know where to improve your inputs before running demos.

Capabilities

The Capabilities tab lists what users can do on your product, generated from your content and exploration data. Each capability describes a user action (e.g., "Create a survey," "Invite team members") with details about where it happens and how involved it is.

Capabilities drive what the AI demo agent shows and what the onboarding automation agent helps users complete. You generate them from this tab and review the output. See Capabilities.

Plans

The Plans tab contains the step-by-step task flows for each capability. A plan for "Configure notifications" might include: navigate to settings, click notifications, fill email field, choose notification frequency.

Plans have a list view (sequential tasks) and a flow view (visual graph with branches). You can edit plans directly: reorder tasks, update voice scripts, adjust element targeting, and modify decision branches. See Plans.

Demo Sessions

Demo Sessions is where you launch and review AI-powered demo calls.

To start a session, click Start Demo and optionally add prospect context (name, company, role, interests). The agent launches a browser with your product and begins the voice conversation.

After a session ends, you can review:

  • Full conversation transcript
  • Screen recordings showing what the agent navigated
  • Buying signals the prospect expressed
  • Questions the prospect asked
  • Session duration and engagement patterns

This data feeds your sales team's follow-up. See the Demo Agent overview for how sessions work.

Recordings

The Recordings section stores workflow recordings captured from your product. These are step-by-step traces of user actions (clicks, form fills, navigation) that Floe uses to improve plan quality.

Recordings can be captured using the Floe recorder, which you inject into your product's browser session. The recorder captures each action with rich metadata about what was clicked, what was typed, and what the screen looked like at each step.

Users

The Users section shows people who have interacted with the AI agent during onboarding or support sessions. It tracks which capabilities each user has completed, where they are in their onboarding journey, and any issues they encountered.

This is your view into the user onboarding funnel at the individual level.

Accounts

Accounts shows your organization's settings: team members, billing, and API keys. This is where you manage who has access to the dashboard and configure global settings that apply across all your sites.

Navigation

The dashboard follows a consistent pattern:

  1. Sites list is the home screen
  2. Click a site to see its tabs (Ingestion, Content, Explorer, Knowledge, Capabilities, Plans, Demo Sessions, Recordings)
  3. Click a tab to see that section's content
  4. Click an item (a plan, a session, a capability) to see its details

Most work happens inside a site. You pick the site you're working on, then move between tabs as needed. The sidebar stays visible so you can jump between sections without going back to the list.

Getting started

If you're new to the dashboard:

  1. Start with the Quickstart to create your first site
  2. Add content via Ingestion
  3. Run Exploration to map your product
  4. Generate Capabilities and review the output
  5. Launch your first demo session

FAQ

Can multiple team members use the dashboard? Yes. Add team members from the Accounts section. Everyone sees the same sites and data.

Is there a way to search across the dashboard? Each section has its own search or filter. Content is searchable by keyword, capabilities by category, and plans by name.

How do I know if my site is fully set up? A fully set up site has: at least one ingestion config completed, exploration run at least once, and capabilities generated. The Capabilities tab will be empty if any prerequisite is missing.