Environment Controls
Last updated September 21, 2026
Use environment controls as deployment practice for Matruno legal workspaces; the repo does not include a built-in promotion pipeline.
What is and is not built in#
Matruno has environment variables, Docker Compose services, workspace-scoped data, workflow import/export, template import/export, migrations, and admin settings. The repo does not include a built-in multi-environment promotion pipeline.
Recommended practice#
Use separate deployments or workspaces for experimentation and production-like validation of legal workflows. Validate workflow imports, connector credentials, webhook endpoints, template changes, role assignments, and attorney-review gates outside production before enabling auto execution.
Confidential matter data, evidence, and generated legal documents should not be copied into shared demo environments without an explicit retention decision.
Record governance decisions#
When a legal workflow is promoted or an approval threshold changes, capture why in your change process. Matruno can show saved workflow definitions, audit events, and matter history, but your organization still owns the approval policy around those changes.
Stable promotion paths reduce incidents
Many workflow incidents are not code failures. They are legal-process changes that were correct in intent but insufficiently validated in a production-like environment.
Was this helpful?