Home / Product / DAV-style access

Use familiar collection clients

Give compatible clients a familiar way to work with files and collections.

Expose basic WebDAV-style operations under CalDAV and CardDAV paths while keeping the supported scope honest and bounded.

See what it changes Technical guide ↗

DAV-style access in a product

A compatible client connectsUse a DAV-aware tool

Browse a permitted collectionWork with files inside the available scope

Keep product contextStore content in Daptin's document foundation

Standards help existing tools participate

01Expose supported files and collections through Daptin’s DAV-style endpoints.Use familiar HTTP-based collection operations.

02Connect files to application recordsKeep the stored content inside Daptin's wider model.

03Adopt within a clear scopeKnow that basic file and collection access is supported.

Why it matters

Interoperability is useful only when its limits are as clear as its possibilities.

Teams may already use clients that understand WebDAV-style collections. Teams test required WebDAV, CalDAV, and CardDAV operations against each client before adoption.

Daptin exposes scoped file and collection operations under CalDAV and CardDAV routes. Those paths build on document and collection storage.

The deliberate boundary matters: this is basic DAV-style access.

Meet compatible tools where they are

Use established client behavior for basic collection access.

Keep content in the same backend

Connect DAV-accessible material to documents, collections, files, and permissions.

Evaluate honestly

Adopt Daptin for the documented DAV operations after testing each required calendar and address-book workflow.

How it fits

Part of one connected backend.

DAV-style access does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Connect

A compatible client reaches the configured DAV path.

Step 2Authenticate

Establish the account and permitted scope.

Step 3Operate

Read and manage files or collections within supported behavior.

Step 4Share

The underlying content remains part of the application model.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Shared document collection

Open and manage a bounded set of files from a compatible client.

Personal content access

Give a user a familiar path to their own collection.

Existing-tool bridge

Connect a workflow that already speaks basic WebDAV operations.

Connected by design

Let compatible file clients reach document and collection storage through familiar paths.

These capabilities share the same application context, so each one makes dav-style access more useful.

Know the boundary

What Daptin leaves in your hands.

Adopt Daptin for its documented DAV operation set and test every required calendar or contact client operation. Test discovery, locking, metadata, client expectations, and every operation your chosen tool requires before treating it as compatible.

Understand the operating responsibility →

Build from one foundation

Connect compatible file clients to the same documents, collections, and permissions used by your application.

Run Daptin locally, explore the live administration surface, and follow one complete application path.

Get Daptin Explore all capabilities