Welcome to ZiplineOS training. This is the front door for everyone getting up to speed on the platform — whether you're an engineer who'll be shipping code, an operator or support agent who'll be running and explaining the product, or a broker or end customer who just needs to get a deal done.
You don't have to read the whole knowledge base. This hub points you at a learning path — a curated, ordered doc that walks you through the platform in the right sequence for your role. Pick the path that matches you, work through it top to bottom, and you'll come out the other side knowing where everything lives and how the pieces fit together.
How to use this section
The Training section is the curated, narrative part of the knowledge base. We don't re-explain features here — the deep reference lives in Guides, Portals, Architecture, and API. Instead, each path below is a standalone doc that tells you, step by step, what to read and what you'll be able to do once you've read it.
This overview is just the chooser. Find your role below, then follow the link into the full path.
Treat your path like a checklist. Open the linked doc, work through its steps in order, and tick each one off. Most paths take a focused half-day to a few days; you can stop at any point and you'll already be useful.
A few things are worth bookmarking no matter who you are:
- Feature Walkthroughs — short, audience-tagged, end-to-end task tours (create a contact, send a campaign, build a workflow, submit an application). Great for "I just need the steps for this one task."
- Getting started — the day-one setup checklist for new engineers and operators.
The hands-on Getting Started with the Input Portal tutorial — build a form, a workflow, and a live test deal from scratch — is the single best way to feel how ZiplineOS works. It lives in the internal and technical spaces, so it's only reachable if your account has that access. If you can't open it, the broker/end-user path below covers the same ground in reading form.
Pick your path:
- Path A — Engineer · you'll be writing or reviewing code for the platform.
- Path B — Operator / Support · you'll be running an org, configuring portals, or helping users.
- Path C — Broker / End User · you'll be working deals, or you're an applicant filling one in.
Path A — Engineer
Who it's for: developers joining the platform team or a portal team.
By the end you'll have a working local environment, a mental model of the architecture, and you'll know where the code, the data, and the runbooks live well enough to ship your first PR.
The full path is a Day 1–5 walkthrough — environment setup, the codebase and architecture tour, the data model, testing, and shipping your first change — with the right doc linked at each step.
→ Start here: New Engineer — Your First Week (internal)
Keep the Runbooks Overview bookmarked. The day something is on fire — a 401 loop, an AlloyDB hiccup, a stuck deploy — that's where the step-by-step recovery lives, and Incident Response is the front door.
Path B — Operator / Support
Who it's for: ops staff, admins, and support agents who configure orgs and help users.
By the end you'll understand what each portal is for, how to set up forms and workflows, how access and licensing work, and how to triage the questions users bring you — plus the runbooks, incident response, and compliance you'll lean on.
The full path takes you through the portals in the order you'll meet them, the Input Portal building blocks, identity and access, and the support playbook for the questions you'll field most.
→ Start here: Ops & Support — Onboarding Path (internal)
When a user is stuck, reach for Feature Walkthroughs first — it has copy-paste-ready step lists for the exact task they're trying to do, grouped by audience.
Path C — Broker / End User
Who it's for: brokers and operators who work deals day to day, and applicants who've been sent a link to fill in.
By the end you'll be able to create and progress a deal, build and shape the forms behind it, and understand what your clients see on their side — or, as an applicant, complete and submit an application with confidence. No technical background needed; you won't be touching code.
The full path starts with the vocabulary (form, workflow, deal), tours the Input Portal, has you build a deal hands-on, and finishes with the client-side experience.
→ Start here: Brokers & End Users — Getting Productive
If you just want orientation rather than the full path, two quick public reads:
- What is the Input Portal and how do I get started? — a plain-language intro to what the Input Portal is for.
- Feature Walkthroughs — start with the Daily Operations and Client-Facing sections; the Submitting an Application via Magic Link (Collect) walkthrough has the step-by-step for what an applicant sees and does when you send them a link.
Stuck on access, a login loop, or something that looks broken? You don't need an engineer — start with How do I get access?, Why do I keep getting logged out?, or Something's broken — how do I report it?.
Where to go next
- Finished a path and want the deep reference? Browse the Guides Overview and Portals Overview (internal).
- Need a one-off task recipe? Feature Walkthroughs is the fastest route.
- Building forms and workflows seriously? The Input Portal guide set — forms, validations, display modes, and workflows — is your reference shelf.
You're never expected to memorise the KB — just to know it's here and how it's organised. Bookmark this page, pick your path, and follow the next unticked step. Welcome aboard.