Key concepts
Plain-language definitions of every term you will meet in CloudRaker.
Each entry below is a short definition — for how to do the thing, follow the link to the page that covers it.
New to CloudRaker? Read What CloudRaker is for the mental model first, then use this page as a reference whenever a word is unfamiliar.
The big picture
Organization
Your whole CloudRaker workspace — your people, spaces, definitions, and data. One organization is one tenant. If you belong to more than one, switch between them from the sidebar header; switching re-scopes and reloads the app so nothing carries across. See Organization settings.
The agent (AI assistant)
The built-in AI assistant. It reads documents, fills forms, and drafts records inside a playbook run. The agent only ever produces drafts — a person always approves. See Approvals and steering.
Draft
A proposed value, record, or document produced by the agent or automation that has not yet been approved. Nothing a draft contains becomes real data until a person approves it.
Grounding
The pointer from an AI-drafted value back to exactly where it came from in the source — the file and page and highlighted region of a PDF, or the timecode in an audio file. Grounding lets you confirm a value against its source before you approve it. See Search and graph.
Spaces
Where the work happens, and the template a space is created from.
Space
A workspace that holds the files, records, and people for one body of work. You do your work inside a space. Every space is created from a space type. See Spaces overview.
Space type
The reusable template a space is created from. Admins manage space types, and a space type decides which playbooks and actions are available to spaces created from it. See Space types.
Playbooks and runs
The reusable process, and one live execution of it.
Playbook
An org-level, reusable definition of a process: a goal, an ordered set of tasks, and the actions the agent is allowed to run. Playbooks are made available to spaces by their space type. See Playbooks overview.
Run
One execution of a playbook inside a space. The agent works through the run’s tasks and pauses at approval cards for you to review its drafts. See Run a playbook.
Approval
The human gate inside a run where a drafted output is reviewed and either approved or rejected. Approval is what turns the agent’s drafts into committed data. See Approvals and steering.
Actions
Installable capabilities that run over files.
Action
An installable, single-purpose capability run over files — for example extract data, fill a form, sign, or redact. An action runs either on its own from a space’s Actions tab, or dispatched by the agent inside a playbook run. See Actions overview.
Data
The structured data a space collects.
Record (data object)
A piece of structured data extracted or entered in a space — for example a single invoice. Approved drafts become records. See Records.
Record type
The org-level definition of a record’s shape — its set of fields. Every record follows a record type. See Record types.
Terms from the old product that no longer exist. If you’ve used an earlier version of CloudRaker, these are gone — don’t look for them: My work, Inbox, Projects and PRJ numbers, Building Blocks, task-type playbooks, and a standalone assistant chat. Work now lives in spaces, and the assistant appears only inside a playbook run.