Understanding config-driven design
Document Blueprint treats workspace behavior as configuration, not code — which means you can reshape a workspace without a developer.
Last updated
Document Blueprint treats workspace behavior as configuration, not code — which means you can reshape a workspace without a developer.
Other tools expose a few knobs (template name, folder path) and hide the rest behind menus or custom code. Here, almost every behavior-defining decision lives in UI-editable configuration.
What config-driven means in practice
The dashboard is configured per workspace
Columns, filters, the default sort, which sections show on a case detail page — all from workspace configuration. Edit, save, and the dashboard updates live.
Templates are live
Change a field's source from question to extracted, save, and the next autofill run uses the new logic. No build step.
Categories route files
A file category decides which templates can process a file and which collaborators can see it. Re-link a category and every new matching file flows through the new path.
Filter presets are saved views
A filter preset is a saved set of filter clauses (status=review, due_date < today, assignee=me) layered over the mailbox you're viewing. Presets have no schema of their own — they're views over the same case data, defined entirely in workspace config.