# Open WebUI deployment checklist

Proposed operator checklist; no deployment has been executed for this guide. Record actual results before checking items.

## Plan and record

- [ ] Name the operator, intended users, approved access method and required features.
- [ ] Record release/image tag and actual digest, architecture, runtime, database, storage and provider connections.
- [ ] Select the standard or slim image against feature requirements; include separate model-serving capacity.
- [ ] Review current release/security guidance when implementing the dated example.

## Private bootstrap

- [ ] Create a persistent data volume and persistent WEBUI_SECRET_KEY via protected configuration.
- [ ] Keep secret values out of repositories and exported examples.
- [ ] Restrict the first-run interface; use loopback/private access until administrator ownership is established.
- [ ] Choose interactive first-account setup or documented headless bootstrap on an empty user database.
- [ ] Verify actual signup, ordinary-user role and working authentication/recovery behavior.
- [ ] Confirm effective saved settings; changing an environment file alone may not change persisted configuration.

## Access and data flow

- [ ] Inventory global/group grants and resource sharing. Group permissions are additive, not deny overrides.
- [ ] Run role-action-matrix.csv with synthetic accounts and unshared resources; leave unrun results explicit.
- [ ] Treat UI_VISIBILITY as interface presentation, not authorization.
- [ ] Approve executable extensions and their execution/network scope separately.
- [ ] Map prompts, files, extraction, embeddings, inference, tools, logs and backups to actual services.
- [ ] Verify provider/gateway credential scope and real spending controls; application roles do not replace them.

## Operations

- [ ] Verify remote HTTPS/access proxy behavior using the actual topology.
- [ ] Complete a successful ordinary-user workflow and an isolated failure/recovery test.
- [ ] Use database-appropriate consistent backups, including external storage where configured.
- [ ] Restore into a new disposable target and rehearse upgrade/recovery before updating the shared service.
- [ ] Record tested version, date, operator, evidence and unresolved issues. Do not mark these items tested from documentation alone.