TealfabricLibrary

Path briefing

Workflows introduction

  • Path goal: Open your tenant, find My Work, and learn the vocabulary you will see everywhere.
  • Why this stop: Explains Operations My Work and how work kinds show up for people in the tenant.
  • Do next: Note the difference between employee My Work and admin publishing.

Do next: Note the difference between employee My Work and admin publishing.

Source: path manifesto (offline-safe)

Stop 3 of 8·Open canonical page

Workflows

Document information
  • Canonical URL: /docs/12_workflows/00_introduction
  • Version: 2026-10-02
  • Tags: operations, workflows, my-work, processflow, guides

Workflows is the Library pillar for work that employees finish in Operations My Work. It covers how integrations, ProcessFlows, and WebApps publish governed requests, and how tenant admins and Trace keep those requests honest (Approve only when a real gate exists).

Operations work published from integrations and ProcessFlow into My Work for employees.

Who this is for

AudienceStart here
Employees using My WorkOperational requests and My Work
Tenant admins wiring systemsPublishing work for tenant admins
Trace / AI process authorsTrace: craft Operations-aligned work
Copyable end-to-end patternTemplate: customer onboarding

Core idea

Automatic and AI-assisted ProcessFlow steps should rarely become tasks. Human decisions and recovery create work kinds in My Work:

  • Approval — yes/no with a pending human-input id
  • Action required — person does work outside Tealfabric; process updates state later
  • Exception — automation blocked; clear guidance and optional Retry

Storage stays the DataPool schema operational_requests. Prefer sandbox helpers tf.operations.* over hand-written JSON.

See also

Next stop