Public Documentation

Lawie Docs

how-toDifficulty: beginnerTime: 15mVersion: v1Reviewed: 2026-07-14Reviewer: Regulatory Intake ownerTags: help, integrations, regulatory-intake

Configure Datovka/ISDS Ingestion

Ingest Czech data-box traffic into compliance and matter pipelines with traceability.

Overview

Ingest Czech data-box traffic into compliance and matter pipelines with traceability.

Audience

  • Admin
  • Compliance

Product Area

Regulatory Intake

Prerequisites

  • Datovka credentials
  • Inbound mailbox approvals

Steps

  1. Set connector credentials

Configure credential material and polling intervals securely.

  1. Route message classes

Map message classes to obligations, matters, or inbox review queues.

Expected Result

The Regulatory Intake workflow completes without unresolved validation errors, and the result is visible to the intended roles.

Security and Audit Notes

  • Use the least-privileged role that can complete the task.
  • Confirm the resulting change or decision appears in the workspace audit trail when the workflow changes customer data or access.

Limits and Preconditions

  • Available controls depend on the tenant plan, enabled modules, jurisdiction, and administrator policy.
  • If a named control is not visible, confirm entitlement and role access before treating the behavior as a product failure.

Troubleshooting

  • Polling throttled: Tune polling interval and confirm message quota limits.

Related Articles

Escalation

If the documented result cannot be reached after the checks above, capture the workspace identifier, affected product area, timestamp, and a redacted error message, then use Support. Never include secrets, privileged legal content, or customer documents in the initial report.