Book a demo
Book a demo
Login

App workflow Paperless-ngx + Docker workloads

Deploy Paperless-ngx for document archiving

Confirm storage, OCR, import, and backup requirements before moving records. Check the named site's prerequisites, task result, backup scope and recovery handoff with xCloud.

Technical review: · Source reviewed; no production deployment test claimed

Published · Updated · xCloud editorial

Read this guide as Markdown

Requirements and responsibilities

Illustrative situation

A back-office team wants Paperless-ngx for scanned invoices. It needs to confirm OCR, metadata and export without losing original documents on restore.

Choose the approach

Dashboard and application procedure

Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.

Step 1 of 5

Define document rules

Where
Records owner and Paperless administration docs
Permissions
Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
Inputs
Sample PDF, retention, tags, access groups
Action
Choose a harmless sample and decide how originals, OCR text and metadata should be classified. Set access expectations for staff.
Expected result
An intake and retention plan.
Verify
Ask a user to identify the expected search term and document owner.
If it fails
If retention requirements are unclear, keep real invoices out of the pilot.

Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Paperless-ngx administration and exporter

Step 2 of 5

Inspect template storage

Where
xCloud One-Click Apps catalog
Permissions
Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
Inputs
Paperless template, Docker server, volume paths
Action
Confirm current app template, database/media storage and consumer directory behavior. Choose sufficient disk for originals and OCR derivatives.
Expected result
A storage plan covering all document state.
Verify
Inspect template form and free space.
If it fails
If consumer path is not persistent or backed up, correct design before import.

Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Paperless-ngx administration and exporter

Step 3 of 5

Deploy and secure users

Where
xCloud dashboard; Paperless admin
Permissions
Authorized xCloud site owner with dashboard rights for the exact setting, backup, staging or restore action and a reviewed target.
Inputs
HTTPS domain, admin and limited clerk account
Action
Install through dashboard, complete app administrator setup and restrict access to approved staff.
Expected result
A reachable archive with least-privilege test account.
Verify
Sign in as clerk and verify permissions.
If it fails
If a clerk sees restricted material, repair app roles before ingestion.

Sources: xCloud One Click Apps catalog · xCloud agent capability boundaries

Step 4 of 5

Import and retrieve a sample

Where
Paperless consume flow and search
Permissions
Authorized Paperless Ngx application administrator or delegated role with rights for this task; hosting access alone is insufficient.
Inputs
Sample PDF, expected tag/correspondent
Action
Import one non-sensitive PDF via the selected intake path. Wait for consumption/OCR, assign metadata, search its text and download the original.
Expected result
A document that can be found and exported with correct metadata.
Verify
Match original file and search result to the sample.
If it fails
If OCR fails, inspect task queue and language/settings before bulk import.

Sources: Paperless-ngx administration and exporter

Step 5 of 5

Test export and restore scope

Where
Paperless document exporter and xCloud Backup
Permissions
Authorized xCloud team/site operator with the discovered write scope for this exact operation and owner approval for its target and interruption.
Inputs
Export location, database, media, config
Action
Run the app exporter for the sample and inspect files. Check a Completed Docker backup of all persistent state; plan an isolated restore.
Expected result
A recoverable archive plan.
Verify
Verify export includes document plus metadata and backup row completes.
If it fails
If an app export omits configuration, retain it through an additional documented backup.

Sources: Back up and restore Docker apps · Docker backup operations and storage constraints · Paperless-ngx administration and exporter

Maintenance

Recovery decisions

AI handoff

Connect an authorized xCloud MCP profile and discover its exact tools and team scope. The packaged REST wrapper is GET-only; use dashboard or app controls for undocumented writes.

Supported scope

  • Confirm requirements and inspect resources mcp · read

    Discover the connected profile and operation schema first; only teams granted to the connection are visible.

    Checkpoint: Confirm exact team, server and site identity. Use dashboard_url returned by the resource; do not invent a dashboard link.

    Operation identifiers and scopes to discover

    teams.index, servers.show, sites.show

    Scopes: read:servers, read:sites

    xCloud MCP documentation and connection profiles · xCloud agent capability boundaries

Copyable agent brief

Manual checkpoints

  • Approve exact site, target, cost and any write or maintenance window after inspecting the proposed plan.
  • An authorized Paperless Ngx administrator must configure and test app users, content, integrations and business rules in the app.
  • Native WordPress staging, backup schedule/settings, push/pull and all restores are dashboard-only; Docker restore is dashboard-only and replaces state.
  • Reconcile data created after the chosen recovery point before any destructive restore.
Feature coverage

Sources

Continue

Explore all use cases