Matruno

Administration

Last updated September 21, 2026

Operate Matruno workspace settings, admin-panel controls, billing surfaces, support routes, system health, and legal-governance practices grounded in the repo.

Implemented admin surfaces#

Matruno has both workspace administration in the main app and a separate admin panel.

The main app includes workspace settings, member management, integrations, webhooks/tools, templates, usage, support, and profile/settings pages. The backend exposes workspace, settings, usage, billing, support, error monitoring, and admin billing routes.

The admin panel under admin-panel/ is a Next.js app for platform-level surfaces such as workspaces overview, usage snapshot, credit control, webhook health, and system health. It runs on port 5679 in Compose.

Governance is an operating practice#

The repo does not implement a complete policy-management product or formal change-approval system. Use governance docs to describe how legal operators should review workflow definitions, templates, integrations, permissions, billing controls, and observability alerts before production use.

Treat workflow and template changes as legal-process changes: they can alter attorney-review gates, generated legal documents, and who can see confidential matter data.

Review high-impact changes#

Review changes to legal workflow definitions, document templates, connector credentials, webhook endpoints, external tools, role assignments, billing/credit controls, and production environment variables. Keep decisions tied to matters, audit logs, support tickets, or change records where possible.

Do not enable auto execution for a legal workflow until intake fields, confidentiality handling, and attorney-review checkpoints are understood.

Was this helpful?