Knowledge Base
Task-shaped articles, troubleshooting guides, and FAQs. If Documentation is the reference manual, the Knowledge Base is the field guide — answers to "I'm trying to do X" and "this error message means what?".
Most-read articles
Reduce flow runtime
Six-lever performance triage when a flow takes longer than it should. Filter early, cache, parallelize, pick the right recipe.
Read the recipe →Permission denied after LDAP sync
The four places this breaks, in diagnostic order. Sync, group membership, permission grant, cache.
Diagnose →Seat types vs. group permissions
The two-axis access model. Why a 'builder' with no group memberships can't actually edit anything.
Read the concept →Browse by section
Recipes
Five step-by-step recipes for common operational tasks. Start here when you know what you want to do but not how.
Browse recipes →Troubleshooting
Four diagnostic ladders for connection failures, slow dashboards, stuck flows, and LDAP-after-sync issues.
Find a fix →FAQ
Audience-segmented Q&A — admin, builder, developer, evaluator. Skim before opening a support ticket.
Read FAQs →Concepts
Four explainers covering the model: seat types, recipes vs. flows, connections vs. connectors, refresh strategies.
Read explainers →How this differs from Documentation
- Documentation describes what something is and how it's configured (reference)
- Knowledge describes how to do a specific thing or why something broke (task-shaped)
- Developer is the same idea as Documentation, but for code-level integration
When in doubt, use the search bar in the navbar — it indexes all three properties at once.