Stood Flows is a desktop application that reads a Salesforce org and turns it into an actionable, end-to-end picture: what the org does (business processes, record types, automation), what it costs (licences, profile budgets, user activity), and how it talks to the outside world (inbound APIs, outbound callouts, Apex dependencies).
The methodology is deliberately layered. You start from the backbone of the org — the standard CRM objects and their record types — and progressively zoom in on volumes, complexity, code, licensing, and integrations. Each zoom level produces artefacts you can save, share, anchor issues against, and bring forward to the next refresh.
This documentation is for users who are comfortable with Salesforce concepts (objects, profiles, record types, Apex, named credentials) but may not have used everything Stood Flows surfaces — Event Log Files, External Data Sources, Apex dependency walks, etc. Those are explained where they appear.
Prerequisites and the Salesforce CLI — what to install, what permissions the connected org user needs.
License keys — how the refresh-time licence check works and where the key file lives.
Getting started — your first folder, your first refresh, version snapshots.
Methodology overview — why backbone-first, what each refresh actually fetches, how versioning works.
KPI table — every column in the master view, where each number comes from, how to read it.
Volumes and complexity — record counts, ghost rows, the complexity score and what feeds it.
Objects, record types and lineage — backbone vs custom objects, parent-child relationships, why a record type gets a column.
History timeline — when each element Stood tracks was created or last modified (and by whom), plus the 180-day Setup audit trail.
Apex analysis and packaging — dependency tree, org-wide roots/orphans, RT/DML/SOQL detection, the migration handoff package.
Licensing — licence inventory, profile budgets, cohorts, credits, and the deactivation policy.
DML analysis and ELF — Event Log Files explained, the activity buckets, drill from bucket → licence → profile → user.
I/O analysis and heavy consumers — inbound caller drill, outbound destination drill, External Data Sources, identifying heavy consumers.
SELA contracts — record what you pay Salesforce and compare it to actual usage.
Multi-org KPI dashboard — compare every org in a folder over time, no contract required.
Issue management — GitHub-backed or CSV-backed, anchored issues that survive refreshes.
Settings: GitHub, offline mode, CLI paths — how to wire each one, including how to force offline mode via config.json.
Team sharing (S3) — publish a folder's results to an S3 bucket for teammates to pull.
Roles: Admin and Viewer — how the licence key decides who can run analyses versus browse read-only.
Security posture — read-only by design, where the security guarantees live in the codebase, link to the public statement.
Everything Stood Flows reads or writes is under ~/StoodFlows/:
~/StoodFlows/├── config.json # app-global config (defaultOrg, offline flag, …)├── workspaces/│ └── <org-alias>/ # one folder per Salesforce org you connect│ ├── license.key # optional licence key for refresh│ └── graphs/│ └── <graph-slug>/ # one graph per analysis project│ ├── graph.json # graph config (enabled objects, tags, integrations)│ ├── versions/ # versioned metadata snapshots│ ├── apex/ # mirrored .cls / .trigger bodies│ ├── apex-panel.json # extracted Apex analysis (RT/DML/SOQL)│ ├── apex-packages/ # "Generate schema artefacts" output│ ├── elf-aggregates/ # I/O + DML aggregates (JSON)│ ├── flows-raw/ # record-triggered flow XML by object│ ├── sfschema/ # per-object schema dumps│ ├── usage-actors.json # backbone actors per (object, RT)│ └── issues.csv # local issue tracker (when GitHub isn't used)
Nothing is uploaded anywhere. The app reads your org through the sf CLI and writes everything to that local folder.