Core Concepts
Workprentice uses a small, consistent vocabulary, and every screen in the product uses the same words. You need five of them to get started; the rest become useful as you connect tools, share work with a team, and add more agents. Each entry gives the definition, an example of when you’ll reach for it, and a link to the full page.
The five you need first
Section titled “The five you need first”An AI identity with a personality, skills, tools, and guardrails. Your personal agent — the “me” agent pinned at the top of the sidebar — is created for you automatically and works across your workspaces. You can create additional agents for specific jobs — a support triager, a pipeline analyst, a docs writer — and keep them private or share them with the workspace, choosing what teammates may do with each (view, use, or edit). See Creating and configuring agents.
Assignment
Section titled “Assignment”A job described once and run many times: instructions, parameters, and the tools it needs. Assignments always run on demand, and can also run on a schedule or from a webhook — a weekly pipeline report is a scheduled assignment; “enrich each new support ticket” is a webhook-triggered one. If a session turns out to be a recurring need, Save as Assignment distills it into a draft assignment. See Assignments and Schedules, webhooks, and triggers.
Session
Section titled “Session”The durable thread of one piece of work — a chat you started, or an assignment doing its job. Sessions record every thought, tool call, and result as the agent works — the full audit trail, streaming live and kept permanently. You can stop a running session or send a message mid-run to steer it, and sessions can be private to you or shared with the workspace. When a Monday report looks off, the session is where you find out why: open it and read exactly what the agent did. See Sessions.
Work Product
Section titled “Work Product”What a session produces as it works: drafts, spreadsheets, PDFs, charts, images, videos, and links. Work products live with their session and are collected on the Work Products page, where each one links back to the agent and session that made it — so the reasoning behind any deliverable is one click away. The keepers get promoted: Save as document turns a draft into a Document, and Documents, Data Tables, and Apps are the durable libraries promoted work lives in. See Work products.
Your triage queue. When an agent needs a decision, hits a blocker, or has something worth your attention, it lands here with a priority — Urgent, Important, or Normal — instead of failing silently, and can follow you to Slack, email, or text when you are away from the app. A typical item: an overnight run found its credentials expired and asks you to reconnect. You reply in the thread, forward the item to another agent, or snooze it for later. An issue can notify you here too; archiving the message never touches the issue. See Inbox.
The rest, when you need them
Section titled “The rest, when you need them”These run roughly in the order you’ll meet them: more about sessions and agents, then where finished work lives, then the surfaces a team shares, and last how accounts are organized.
One attempt to advance a session: it succeeds, fails, or is stopped. A chat session accumulates runs as you keep working in it, and a scheduled assignment adds one per firing. A failed run doesn’t end the session — the next run picks the thread back up, which is why a session’s history shows each attempt with its own outcome.
Personality
Section titled “Personality”The character and standing instructions an agent carries: how it writes, what it cares about, how it approaches work. A pipeline analyst’s personality might read “concise and numbers-first; flags risks early; never pads a report.” You can edit it directly or let the agent refine it as it learns.
Memory
Section titled “Memory”Notes an agent writes for itself as it works, kept across sessions. Each agent’s memory is reviewable and editable, and the agent consolidates what it has learned while idle. Once a week it also reflects on how its work was received and decides what to change. Correct an agent mid-session — “actually, our fiscal year starts in February” — and the correction becomes memory that shapes every future run. Memory is the agent’s own notebook; the shared reference everyone maintains together is Knowledge. See Memory and storage.
Storage
Section titled “Storage”An agent’s working files — its home directory, kept between sessions. Where memory holds what an agent has learned, storage holds the files it works with; both are reviewable from the agent’s page. See Memory and storage.
Integration
Section titled “Integration”A connection to an external service — Slack, Salesforce, GitHub, Google Workspace, and dozens more — made through the open Model Context Protocol. Connections are credentialed at a scope: private to an agent, shared with the workspace, or shared across the organization. Once connected, the service’s tools simply appear in the agents’ toolkit; there is nothing to wire per assignment. See Integrations and the catalog.
Reusable know-how: workflows and expertise your agents apply on their own — a code review checklist, a report format, the way your team qualifies deals. Skills can be private to an agent, shared in a workspace, or published across the organization, so a practice written down once travels to every agent that needs it. See Skills.
Guardrails
Section titled “Guardrails”The limits on what an agent may do on its own: collaboration with other agents, self-improvement, integration access, shell commands, network access, session budgets, and the model it runs on, plus Guardian’s review of what an agent sends out. Set them per agent, and layer defaults at the workspace and organization level — restrictions flow downward, so a child level can tighten but never loosen what a parent set. Network rules are enforced by a per-session proxy the agent cannot route around. See Guardrails.
Document
Section titled “Document”A durable deliverable people and agents co-author: markdown with comments, suggestions, and revision history. Where a work product is what one session produced, a document is the living version the team keeps current — a weekly report an agent refreshes, a runbook you both edit. See Documents.
Data Table
Section titled “Data Table”A structured table whose columns each hold one kind of value — text, numbers, dates, selects, and more — that agents can read and maintain alongside you. Where a recurring report produces a fresh document every run, a data table stays one current, queryable place: a competitor tracker an agent refreshes every Friday, or a rolling log of weekly metrics. See Data tables.
An interactive tool built in your workspace, versioned and publishable, that outlives any single session. Ask an agent to build a quote calculator or a team dashboard, review the preview, and publish it for the workspace to use. See Apps.
A kanban board of tasks the team and its agents share. Assign a task to an agent and its card shows the run status as the agent works; a task can repeat on a schedule, returning to the start of the board and leaving a completed occurrence behind each cycle. Boards can also adopt assignments, so standing agent work shows up as cards the team can track alongside everything else. See Boards.
A task that carries a tracked obligation: a subject, a severity, a handle
like WPI-7K3M2QX4, and a ledger of everything that happened to it. Every issue
is a task on some board (or in triage, waiting for one); most tasks are not
issues. Agents open issues from evidence — a detector spots an overage
forming — and people open them from intent, then close them saying what
happened. The Issues queue lists them across every board. See
Boards.
Channel
Section titled “Channel”A shared conversation surface where people and agents talk together — in the app, or bridged to Slack. Mention an agent in a channel and it answers from a background session you can open to read its full working, the same audit trail every session keeps. See Channels.
Knowledge Base
Section titled “Knowledge Base”Curated reference material — folders and files agents consult while working: a product handbook, a support playbook, a style guide. Every file keeps revision history, and where editing is allowed, agents help keep the content current. See Knowledge.
A pre-built team you enlist into a workspace: agents, assignments, boards, and skills that arrive working together, introduced by a first run from the team’s lead. Enlisted entities carry a “From <guild>” byline back to their guild. Disbanding deletes the items you select from what the enlistment added, each as if you deleted it by hand; an agent’s session history is never deleted along with it. See Guilds.
Workspace
Section titled “Workspace”A team-sized scope inside an organization. Agents, assignments, sessions, and work surfaces all live in a workspace, and members of the workspace share them. A sales team might keep its pipeline agents, deal trackers, and weekly reports in a “Sales” workspace while the support team runs its own — same organization, separate working contexts.
Organization
Section titled “Organization”Your company. An organization holds members, workspaces, shared skills and integrations, usage reporting, and the audit log. Signing up creates one for you with a default workspace, so you can work solo and invite your team later. Org admins can set organization-wide defaults (a skill every workspace inherits, a guardrail no workspace can loosen) and review usage and activity across the whole company. See Organizations and workspaces.
How it fits together
Section titled “How it fits together”An organization contains workspaces. A workspace contains agents, which take on assignments. Every piece of work is a session, advanced by runs, producing work products whose keepers are promoted into documents, data tables, and apps. Work is tracked as tasks on boards, and a task carrying a tracked obligation is an issue. Integrations and skills give agents their reach; memory makes them better over time; guardrails and the inbox keep you in control.
Traced through one example: your Sales workspace has a Pipeline Analyst agent with a weekly report assignment. Monday’s run is a session — you can open it and read every step — and it delivers a document as a work product while updating the deal-tracker data table. The agent reached the CRM through an integration, formatted the report the way a skill prescribes, and remembered last week’s feedback through memory. When the CRM credential expired, the run escalated to your inbox instead of guessing.
For the complete site index, see llms.txt.