Editor

Editor is the build surface of Tale. Where Member is the role that runs the product and Admin is the role that governs it, Editor is the role that creates the things everyone else uses — agents, projects, automations, the documents and structured data the knowledge base holds, the prompts saved for the team. People with the Editor role see the full set of build tabs without the admin governance surface and without the developer-only levers.

This overview names what an Editor does, where they do it, and which pages cover each piece. Editors typically land here on their first day, build out the org's first useful agent and project, and come back to this tab whenever the next thing needs to be built. The role-and-permission story behind the tabs lives on Members and roles.

What Editor covers

The work an Editor does falls into four buckets: building agents (instructions, knowledge bindings, tools, models), curating the knowledge base (uploading documents, maintaining customers, products, vendors, websites), authoring automations (workflows with triggers, steps, and approval gates), and bundling projects (file sets, scoped agents, project instructions). Each bucket has its own section in Platform; the Editor tab is the index across them.

Editors share the build surface with Developers — Developers also see all four buckets and can do everything an Editor can, plus the API and integration plane. Reach for an Editor when the day-to-day work is content and configuration; reach for a Developer when the work crosses into code or external systems.

Pages in this section

The Editor surface is the same surface the per-area sections of Platform document. What follows is the index across them.

Agents → concepts — the four-knob mental model an Editor builds every agent from.

Automations → concepts — workflows, triggers, steps, executions.

Knowledge → overview — the documents and structured-data area an Editor curates.

Projects → overview — the shared workspace an Editor bundles around a customer or a launch.

Prompt library — the saved-prompts area an Editor uses to keep recurring chat starters reusable.

Where this fits

Editor is the role most teams have several of — the people who do the build work other roles consume. The natural first read on day one is Agent concepts, because the four-knob model is what every other build page assumes. The natural second is Build your first agent — it walks the four knobs end to end on a fresh instance.