Frequently asked questions

Doconax is an enterprise document management and document control platform. It helps engineering, construction and regulated teams register documents, control revisions, run approvals and collaborate with external partners — with an audit trail at every step.

Teams that manage governed documents: construction, engineering, manufacturing, government, infrastructure, corporate records and professional services.

Any file-based document — drawings, contracts, procedures, calculations, records and more. Documents are controlled through registers and statuses rather than by file format.

The interface is offered in English, Arabic, Urdu, Dutch and French, with full right-to-left support for Arabic and Urdu.

Yes. Arabic and Urdu use full right-to-left layout, and the interface follows logical properties so content reads correctly in both directions.

Each document stores its full revision history, and one revision is flagged as current. Only released revisions are marked ready for use, and superseded revisions remain retained and visible.

A register is the single list of truth for a document set: every document appears once with a number, a category, an owner and a current status.

Search and filters work on register metadata — number, title, category, owner and status — as well as full document content.

AI capabilities are planned, not released. OCR, classification and semantic search are described on the roadmap and are clearly marked as coming soon.

Yes. Approval templates are attached to document categories, with sequential and parallel steps, SLAs, escalation and role-based assignments.

Typical states are draft, submitted, under review, approved, revision requested, released, superseded, returned, on hold and pending. The vocabulary is configurable.

Yes. Every version, status change, approval, sharing action and access event is recorded with a timestamp and an actor.

Yes. External organizations are invited into scoped workspaces with role-limited access, and their activity appears in the same audit trail.

Sharing is scoped to a document, folder or team, use-controlled with expiry and optional passcodes, and revocable at any time.

Access is assigned through roles (role-based access) and can be refined by document attributes (attribute-based access), with least-privilege defaults.

We use TLS encryption in transit, storage-level encryption at rest, least-privilege access and complete audit logging. Security statements on this site are limited to what we can verify.

Documents are stored in managed cloud storage. Deployment and data location options are confirmed during evaluation with your team.

Import, export and API access are part of the platform, and integration points are documented. Specific integrations are evaluated with your team.