Navigating the app

The sidebar is organized from the work down to the administration: sessions and projects first, then the knowledge the agent uses, then the connections and tools it works with, then the control panel. This page explains each area. For the underlying terms, see Concepts.

Good to know

Project

One engagement: its tasks, linked systems, files, playbooks, and artifacts.

System

A connection to an ERP, database, file server, or other service. One system serves many clients through separate credentials.

Tool

A saved, repeatable action such as a migration load or a nightly sync. Runs the same way every time.

Playbook

A reusable method the agent follows: inputs, steps, approval moments, and completion criteria.

Artifact

A report, mapping proposal, questionnaire, or spreadsheet the agent produced. Downloads as PDF, Word, HTML, or Excel.

Run

One execution of a tool, recorded with its trigger, credential, input, steps, and result.

Agents

The session tree. New session starts a conversation inside a project or on its own. The start screen shows the built-in playbooks, so you can pick Discover a system or Migrate data directly. A session keeps its project for its whole life.

Inside a session, the right side shows the artifacts, files and tool activity of that conversation. Drop files into the chat to use them in the session.

Projects

One card per engagement. New project creates an empty project. Create project starts an agent session that plans the engagement with you. A project page has Tasks (Board and Table views) and Resources (the linked systems, tools, playbooks, artifacts and files).

Brain

• Setup connects context sources: meeting notetakers, Slack, Microsoft Teams, Notion, Google Drive, SharePoint, Box, Gmail and Outlook. Each person connects their own accounts.
• Playbooks lists built-in and custom playbooks. Custom playbooks open in an editor with an agent sidebar.
• Artifacts lists every report, mapping, questionnaire and spreadsheet the agent produced, with sharing and downloads.
• File context holds uploaded files. System documentation lives on the system’s knowledge base instead.

Capabilities

• Tools lists saved tools. Open one to test it in the playground, inspect its steps, see its version history, and deploy it on a schedule, webhook, API or MCP server.
• Systems lists connections. Open one to change authentication, manage credentials and maintain its documentation.
• Credentials lists your personal and shared credentials across systems.
• Schedules lists every recurring run in the organization.
• MCP Servers configures named servers that expose selected tools to AI clients.

Control Panel

• Runs is the execution history with filters, search, and the Investigate and Load Run actions.
• Activity (admins) shows who created, changed, shared and ran what.
• Organization manages members, invitations and roles.
• Access Rules (admins, Enterprise) configures what each role can see and do.

Organization menu

The menu at the bottom left holds API Keys, Settings (branding, run storage, notifications, timeouts), the organization switcher and sign-out.

i

When you are not sure where something is, ask the agent. It knows the app and can open or create most resources for you, including projects, playbooks, MCP servers and schedules.