Design the n8n workflow ownership and safety model #2

New issue

Open

opened 2026-08-23 17:07:45 +00:00 by stanta · 0 comments

stanta commented

2026-08-23 17:07:45 +00:00

Owner

Outcome

Approve how n8n stores workflows and secrets, how it is backed up, and which actions require operator approval.

Current state

n8n is planned for services-internal LXC 201. No workflow source-of-truth or change-authority model is approved.

Work

Choose Git, database, or combined workflow ownership.
Define database and encryption-key backup.
Classify read-only and mutating workflows.
Require explicit approval for media deletion and infrastructure changes.
Define the first read-only workflow.

Validation

The approved design covers storage, backup, secrets, authority, and rollback.
The first workflow has concrete acceptance tests.

References

README.md
iac/guides/roadmap-phase-2.md

## Outcome Approve how n8n stores workflows and secrets, how it is backed up, and which actions require operator approval. ## Current state n8n is planned for services-internal LXC 201. No workflow source-of-truth or change-authority model is approved. ## Work - [ ] Choose Git, database, or combined workflow ownership. - [ ] Define database and encryption-key backup. - [ ] Classify read-only and mutating workflows. - [ ] Require explicit approval for media deletion and infrastructure changes. - [ ] Define the first read-only workflow. ## Validation - [ ] The approved design covers storage, backup, secrets, authority, and rollback. - [ ] The first workflow has concrete acceptance tests. ## References - `README.md` - `iac/guides/roadmap-phase-2.md`

stanta added the

area/automation

type/decision

priority

labels

2026-08-23 17:07:45 +00:00