Key concepts

Your whole RakerOne workspace — your people, projects, building blocks, and data. If you belong to more than one organization, switch between them from the sidebar header; switching reloads the app so nothing carries across. See Organization settings.

The built-in AI assistant. Florent reads documents, pre-fills forms, drafts records and documents, and helps shape work. Florent only ever proposes drafts — a person always approves, activates, submits, starts, and deletes. See Chat with Florent.

A proposed value, record, or document produced by AI or automation that has not yet been approved. Nothing a draft contains becomes real data until a person approves it. See Reviewing AI work.

The sidebar group holding the reusable definitions you set up once and reuse everywhere: project templates, playbooks, actions, record types, and document templates. See What RakerOne is for where it sits in the sidebar, and the building-block entries below for each definition.

The state of a piece of work — a task, a run, an action run, or a building-block definition — shown as a colored badge throughout the app (for example Available, Running, Published). Each kind of work has its own set of statuses.

Your personal page, opened from Home in the sidebar. It lists the tasks waiting on you across all projects, grouped by urgency. See My work.

Your notifications overlay, opened from the sidebar. It collects mentions, task assignments, and approval requests. It pops over the current screen rather than being its own page. See Collaboration.

An “Ask Florent” thread. Conversations are private to you; your recent ones appear under the Chat group in the sidebar. See Chat with Florent.

A message on a task, record, or review-grid row. Comments support @mentions, and you can edit or delete your own. See Collaboration.

Tagging a teammate in a comment to pull them into the conversation and notify them. See Collaboration.

The one-time human gate inside a run that lets a task’s drafted output be written. Approval is required for all Florent and automated work, and for anything that writes records. See the approval model and the act of approving.

Ongoing, per-field verification of an AI-extracted value. You Approve a value (verified correct) or Reject it (flagged wrong); both lock the value, and Dismiss unlocks it. Field review is separate from task approval. See Reviewing AI work.

An Approved or Rejected value that later AI runs won’t overwrite and that can’t be silently hand-edited. Dismiss it first to unlock it. See Reviewing AI work.

The pointer from an AI-extracted value back to exactly where it came from in the source — the file, the page, the highlighted region, and the quoted text. Click a value to see its source. See Reviewing AI work.

The AI’s rating of how sure it is about a value, shown as an icon out of five — or Confirmed absent / Not found — review for empty values. See Reviewing AI work.

A pre-built starting point for a project. Its contents are snapshot-copied when you create a project from it — later edits to the template do not change projects already created. See Project templates.

A reusable definition of a multi-step process: the tasks, their order and dependencies, who’s assigned, and what needs approval. See Playbooks overview.

The playbook as it lives in the library — the blueprint. It has Draft / Published / Archived status and a version number that increases each time you publish. See Playbooks overview.

A reusable, single-purpose automation. Built-in actions run only inside playbooks; custom actions — extract, generate, or fill — are ones you build, test, and run yourself. See Actions overview.

The shape, or set of fields, of a kind of data — for example “Invoice.” A record type can live in three independent scopes: the org library, a project template, or a live project. See Record types overview.

One attribute on a record type, with a type such as Text, Number, Currency, Date, or Select. Fields define what every record of that type captures. See Build a record type.

A Word (.docx) file with placeholders, filled with record data by a generate action to produce a finished PDF or Word file. Distinct from a project template. See Document templates.

The record type a document template’s placeholders are checked and filled against. A template that isn’t bound to a record type works from “Free-form data.” See Document templates.

The workspace for one piece of work. It holds that work’s files, records, runs, and members in one place. See Projects overview.

One live execution of a playbook inside a project. A run is made up of tasks and is identified by a run number (for example PT-001). See Run a playbook.

The identifier for a run, set by the playbook’s numbering settings. See Run a playbook.

A plain-English description of a process you type into “Ask Florent” inside a project. Florent shapes it into a reviewable playbook plan; it never runs on its own — you click Run it to create and start anything. See Run a playbook.

A single step in a run. There are five task types: Form, File upload, Document, Action, and AI task. See Task types.

A task where a person fills in fields, and optionally creates or updates a record. See Completing tasks.

A task where a person uploads one or more files. See Completing tasks.

A task where Florent reads files and extracts structured records, transcribes audio, finds facts, or annotates PDFs. The results are drafts that you review before they become records. See Task types.

A task that runs a registered action automatically. See Task types.

A bounded, open-ended step Florent works on automatically using a prompt and tools. See Task types.

A related task type where Florent fills a blank PDF or image form with the run’s values and parks the filled document for approval. See Task types.

One row of a record type — for example a single invoice. Records live only in live projects, and approved drafts become records. See Project data.

The per-project pool of files — uploaded, produced by tasks, or generated by runs and actions. Files are reusable across runs and outlive any single run. See Files.

Running one action over many files (extract) or many records (generate or fill) at once, reviewed in a grid before any result is committed. See Batch runs.

A person who can see and work in a project. See Create a project.

A bundle of permissions assigned in your identity provider. The four roles are Admin, Manager, Builder, and Member. See Roles and permissions.

A fine-grained capability that decides which menu items and actions you can see and use. See Roles and permissions.

The external sign-in system your organization uses. People, invitations, deactivation, and role assignment all happen there — RakerOne only displays them. See Members and invites.

A credential that lets an external system call the RakerOne API. It carries its own permissions and is shown in full only once. See API keys.