FAQ
Click a question to expand it.
Roles & access
What's the difference between Admin, Owner, and Standard?
Admin sees and edits every workflow including Technical Configuration, manages Settings, and is the only role that can add/remove people or change their role. Owner can create workflows (becoming the owner automatically) and edit only the workflow(s) they're assigned as Owner on, including Approve/Reject on those — but can never see Technical Configuration, not even on their own workflows. Standard is fully read-only everywhere (Settings, saves, approvals, archiving) but can still see Process Steps and History on every workflow, same as Owner minus the ability to act.
How do I add a new person or change someone's role?
Settings → User Management (Admin only). Add by email + role, or change an existing person's role from the dropdown next to their name. Someone Access has authenticated but who has no row here yet is blocked with a message to ask their Admin — not silently let in.
Settings looks different for me than for my Admin, or a workflow's Technical Configuration is missing — why?
Everyone can open Settings, but most of it is Admin-only — Owner and Standard see just Company Information (read-only) and Notifications (editable, self-service). The other tabs (Workflow Options, Import/Export, User Management, and editing Company Information) are Admin-only and don't render at all for anyone else, not just hidden. Technical Configuration works the same way: hidden for Owner and Standard on every workflow, including ones they own, enforced on the server so it won't appear even via a direct API request. Ask your Admin if you believe you need broader access.
Workflow lifecycle
What does "In Development" status do?
It's the earliest point in a workflow's lifecycle (In Development → Active → Inactive → Archived) — fully functional and editable, but scoped out of the dashboard's Active-based counts and the list view's default filter, so unfinished workflows don't inflate what looks live to the rest of the org. Flip Status to Active once it's genuinely ready.
Who can create a new workflow?
Admin or Owner. If an Owner creates one, they automatically become its Owner. Standard is read-only and can't create workflows at all.
What's the difference between Archive and Delete?
Archive is reversible — change Status back any time — and keeps the workflow's full History intact but out of the default active list. Delete is permanent, and only allowed once a workflow is already archived — a deliberate two-step guard against accidental data loss.
Approval & staleness
Does "Save & Flag for Approval" block my changes until someone approves them?
No — the save applies immediately, exactly like a plain Save. Flagging it just creates an Approval Request so the workflow's Owner (or any Admin) can review it afterward and Approve or Reject. Rejecting doesn't undo the change — it's a sign-off trail, not version control or a gate.
What counts as "Stale," and can I change the threshold?
A workflow is Stale once it's gone a set number of days without an edit. Only Active workflows are ever counted — In Development, Inactive, and Archived workflows never show up as Stale, no matter how old their last edit is. Set the threshold at Settings → Company Information → Stale After (Days) — one org-wide value, used everywhere staleness is shown (the dashboard's Control card, the list view's Flags filter and Name-column badge, the record page's own badge). It's separate from each person's own reminder-email cadence, set individually via Settings → Notifications.
Bulk data: import, export & backup
Can Bulk Create update an existing workflow, or only create new ones?
Only create new ones — it's deliberately one-directional. No id is ever read from the uploaded file, so it can never match, and therefore never overwrite, an existing workflow or its History. To bulk-edit existing workflows, open each one on its own record page.
Can Bulk Create set Process Steps or Technical Configuration, not just the top-level fields?
Yes — that's the point of it being JSON rather than a spreadsheet. Each entry in the file can carry its own steps and tech_config arrays alongside Name/Channel/Stage/Department/Product/Owner/Status. See the starter template (Settings → Import / Export → Bulk Create) for the exact shape.
How do I get a complete backup of everything, including Steps, Tech Config, and History?
Settings → Import / Export → Full Data Export (Backup) downloads one JSON file with every workflow (any status), its full Process Steps and Technical Configuration, complete History, every Approval Request, and attachment metadata. It's export-only — there's no matching import — meant for backups, offline analysis, or compliance/records requests, not day-to-day editing.
Can I rename a Channel/Stage/Department/Product value without breaking existing workflows?
Yes — use the rename (pencil) icon on the chip in Settings → Workflow Options. It updates every workflow currently using that value (not just future ones) and logs a History entry on each one it touches. Renaming into a value that already exists in that list is rejected rather than silently merged.
Attachments
What file types can I attach to a Step or Tech Config entry, and is there a size limit?
Common documents (.doc, .docx, .xls, .xlsx, .pdf, .csv, .zip, .txt) and images (.png, .jpg, .jpeg, .gif, .webp) — screenshots can also be pasted directly into a Description field. 25 MB per file. Re-uploading a same-named file replaces it but keeps the previous version recoverable under that attachment's own History, not deleted outright.
Using Claude with your data
Can Claude actually use this data, and for what?
Yes — this is genuinely one of the more useful things to do with what's here, since ThroughLine structures your process knowledge instead of leaving it scattered across docs and tribal memory. A few concrete examples: draft a new-hire onboarding guide from one department's workflows, turn a workflow's Steps into a training checklist or SOP document, summarize what changed across a set of workflows in the last quarter for an audit, spot which workflows are missing an Owner or have gone stale, or draft plain-language answers to a compliance request straight from a workflow's History. Claude can read and reshape the data into whatever form is actually useful for the moment — a guide, a checklist, a narrative — without anyone having to build a new report or dashboard view for each new need.
What's the simplest way to hand data to Claude — no setup required?
Use the Full Data Export above (Settings → Import / Export → Full Data Export (Backup)) and share the resulting JSON file directly in a conversation with Claude — Claude Code, the desktop app, or claude.ai. That's a complete, point-in-time snapshot of every workflow's fields, Steps, Tech Config, History, and Approval Requests, which is normally everything needed for a one-off request like a new-hire guide or a records/compliance summary. No credentials, no server setup, works today.
Is there a way for Claude to query live data directly, instead of a point-in-time export?
Yes, for Claude Code specifically: this project has a local MCP (Model Context Protocol) server in mcp-server/, registered automatically when working in this repo, that exposes three read-only tools — list_workflows, get_workflow, list_picklists — backed by the live database. It's the better fit when you want Claude answering questions against current data repeatedly (not a snapshot that goes stale), e.g. during an ongoing project or a working session. It needs a one-time setup step (a scoped Cloudflare API token in mcp-server/.env) — see mcp-server/README.md for exact steps. Like the JSON export, it's read-only: Claude can analyze and draft from the data, but can't create or edit workflows through either path today.