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.

01Avoid a proprietary client requirementUse 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—not complete calendar semantics.
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. Offering a familiar path can avoid building a custom synchronization client for basic file access.

Daptin exposes scoped file and collection operations under CalDAV and CardDAV routes. Those paths build on document and collection storage rather than creating a separate data island.

The deliberate boundary matters: this is basic DAV-style access, not a claim of full calendar or contact server compatibility.

01

Meet compatible tools where they are

Use established client behavior for basic collection access.

02

Keep content in the same backend

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

03

Evaluate honestly

Adopt for the supported operation set without assuming every calendar or address-book feature.

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.

Know the boundary

What Daptin leaves in your hands.

Daptin does not claim complete CalDAV or CardDAV semantics. 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

Make dav-style access part of the product—not another disconnected service.

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