Getting Started

QBO is an orchestration platform. It sits above your systems of record and runs the work that happens around them: it opens a process (a case) when something needs doing, runs the workflow, hands each task to the right person, generates and files the documents, calls outside services and AI models, and keeps a dated record of all of it. You configure QBO with templates in a web browser; developers extend it with plugins and call it through one consistent API.

Core vocabulary

These words appear on nearly every page of QBO and of this documentation.

Term	What it means	In QBO
Record	Any item QBO stores: a contact, an organization, a process, a document, a task. Every record has a summary page.	Each record type is a module (class), such as Contact or Attachment.
Parent	The record another record belongs to. A document belongs to a process; a process belongs to a contact or an asset. Security and reporting follow the parent.	Object and ObjectID on the child
Template	The definition of a kind of record: a kind of process, workflow, document, task, or message. Each record made from it is an instance.	ITemplate
Process (case)	A unit of work with a beginning and an end, such as a claim, an application, a lease renewal, or an order. The hub that holds the work together.	Process
Workflow	A flowchart that runs against a record: it decides what happens next and does the automated work itself.	Decision
Step	One shape on the workflow’s flowchart: create a task, generate a document, calculate a score, call a service, and so on.	DecisionStep
Task	Work for a person, captured as a form. Completing the task can complete its workflow step.	ImportForm
Worklist	A queue of tasks for a team. People choose Get next item and QBO serves the most important one.	SmartWorklist, with each queued item a SmartWorklistMember
Document	A file attached to a record, uploaded or generated from a template.	Attachment
Role	A set of permissions. What you see in QBO, from menus to individual options, depends on your roles.	SystemRole

How Learn is organized

Learn has a page for each building block of the platform, plus pages for Quandis products. Most pages come in up to four views; choose one under the page title, and links across Learn will follow your choice.

View	For	Covers
Overview	Everyone	What the building block is and its key concepts
End user	People doing the work	Day-to-day screens: worklists, processes, documents, messages
Power user	Analysts and administrators	Templates, rules, security, and configuration
Developer	Integrators and engineers	The API, data model, and extension points

Suggested reading path

1. Start here: choose the view that fits your job. End users should read New user foundations next.
2. How work is organized: Templates, Cases, and Workflow.
3. How work reaches people: Worklists, Forms, and Messaging.
4. Documents and data: Document Management, Imports, Scoring, Reports, and Ledgers.
5. Control and automation: Business Rules, Security, Contacts & Organizations, and AI.
6. Integration: API & Architecture.

Choose your view

Use the buttons under the page title. End user covers signing in, finding records, and working a worklist; Power user covers how configuration is organized and the administrator roles; Developer covers the API route pattern, authentication, and where to go next.