Skip to main content
To quickly get you started with Tela, let’s begin with the key concepts. They are organized from where you work, to what you build, to how you validate and share it.

Where you work

Workspace

Your team’s Workspace is the exclusive environment of your organization. Everything you build in Tela — projects, canvases, workflows, agents, and apps — lives inside a Workspace, where your team can collaborate.

Project

Projects work like folders: they group related Canvases, Workflows, and Agents together in a logical organization. A Canvas or Workflow lives either in a Project or, while you are still experimenting, in your private Drafts. Agents are always created inside a Project.

Dashboard

The Dashboard is the first thing you see when opening Tela. It shows the Projects and artifacts you have access to in your Workspace, and is where you create new Canvases, Workflows, and Agents.

Vault

The Vault is your Workspace’s file storage. Documents you upload — contracts, invoices, reports — live in the Vault and can be used as inputs for Canvases, Workflows, and Apps.

What you build

Tela gives you a few different building blocks. A good rule of thumb: start with a Canvas, and reach for a Workflow when your process has multiple steps that need to happen in sequence.

Prompt

A Prompt is a piece of text or an instruction that you provide to an AI model in order to generate a specific response or output — written in plain language, the way you would instruct a capable co-worker.

Canvas

A Canvas is the fundamental unit of Tela: a place to write, test, and run a single Prompt. Use a Canvas when one well-crafted instruction can do the job — extracting fields from a document, classifying a message, summarizing a report. Each Canvas has different experiences you can navigate between:
  • Craft: write and refine your Prompt, define Variables and the Output Format, pick a model, and preview results
  • Test: validate your Canvas against structured, repeatable Test Cases
  • Usage: review the executions of your Canvas, when enabled for your Workspace

Variable

Variables mark the places in your Prompt whose content changes at runtime — the document being analyzed, the message being classified. You provide their content on each run (typing text, dropping a file) without editing the Canvas itself.

Workflow

A Workflow chains multiple steps into one automated process — for example: extract data from a contract, then route it based on its value, then generate a document from a template. You define every step and the order they run in, so the same input always goes through the same path. Use a Workflow when a single Canvas is not enough: when there are multiple stages, conditions, or documents involved.

Agent

An Agent is an autonomous AI worker. Instead of a single Prompt, you give it a purpose, the inputs it receives, the outputs you expect, and the tools it can use — and the Agent decides which steps to take and completes the task on its own. Use an Agent when you can’t lay out the steps in advance: the path depends on what the Agent finds along the way, it needs to call external services, or it works through a back-and-forth conversation.

Canvas, Workflow or Agent?

A Workflow can also reuse an existing Canvas or Agent as one of its steps, so you can start small and combine the pieces later.

Draft

A Draft is a Canvas or Workflow that does not belong to a Project yet. Drafts are private: only you can see them. Creating a Canvas or Workflow from the Dashboard starts it as a Draft, so you can experiment without cluttering a shared Project. When it is ready, use Move to project to place it in a Project (clicking Publish on a Draft asks you to do this first). Only then can it be published, connected via API, or turned into an App. Moving a Draft into a Project cannot be undone.

Template

Templates are ready-made starting points. Instead of building from scratch, you can start from a Template that already implements a common pattern and adapt it to your case.

How you validate

Test Case

A Test Case is a saved input with an expected result. Running your Test Cases against a Canvas, Workflow or Agent tells you whether it still behaves correctly after you change the Prompt or the model — so you can trust it with real volume, not just the examples you tried by hand.

How you share

App / Workstation

An App packages a published Canvas, Workflow or Agent into a simple interface that anyone in your Workspace can use — without ever touching what’s behind it. The main App type is the Workstation: teammates send files or text, each input becomes a task, and results can be reviewed, approved and exported.

Publishing

Publishing creates a stable version of your Canvas, Workflow, or Agent that Apps and the API consume. You can keep editing and testing freely — only what you publish reaches production.

Environment

An Environment is a place where you publish a version. Every Canvas and Workflow has a Production environment, which Apps and API calls use by default. You can create other environments, such as staging, to try a version through the API before it reaches Production. Each environment serves one version at a time, so publishing a new version to Production replaces the one your App was using.
The easiest way to get started is by creating your first Canvas. It touches most of these concepts in a few minutes.