Omniloq

Security, export and deletion

Secrets stay encrypted and are never re-displayed; export is secret-free and deletion actually runs.

Before you start

  • An OWNER role for security and settings surfaces.

Steps

  1. Manage secrets

    The vault is tenant-scoped; a value is only entered at creation or rotation.

  2. Export

    The export excludes secrets; cancellation and concurrency are handled explicitly.

  3. Delete

    A deletion removes source data; a restored backup is validated in an isolated environment.

Expected result

A secret is never re-displayed or logged, and an export never contains a key value.

Errors and solutions

  • Export too large

    Narrow the requested scope; the export worker reports a bounded failure.

  • Deletion pending

    Stopping a concurrent mutation is explicit; a user data record with the same name is never removed.

Screens

/settings/secrets — Vault: tenant-scoped secrets, rotation, no value re-display.

Reference of the console screen to capture (redacted) during the browser recipe (XP14). No fabricated image is shown.

Limits and dependencies

Placeholder “leave empty to keep” is distinct from the explicit choice “use platform key”.

Provider documentation

—