Meet compatible tools where they are
Use established client behavior for basic collection access.
Home / Product / DAV-style access
Use familiar collection clientsExpose basic WebDAV-style operations under CalDAV and CardDAV paths while keeping the supported scope honest and bounded.
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.
Use established client behavior for basic collection access.
Connect DAV-accessible material to documents, collections, files, and permissions.
Adopt for the supported operation set without assuming every calendar or address-book feature.
DAV-style access does more when it can reuse the records, people, access rules, and workflows already in your application.
A compatible client reaches the configured DAV path.
Establish the account and permitted scope.
Read and manage files or collections within supported behavior.
The underlying content remains part of the application model.
Start from the experience you want to create; the backend capability supports the work behind it.
Open and manage a bounded set of files from a compatible client.
Give a user a familiar path to their own collection.
Connect a workflow that already speaks basic WebDAV operations.
These capabilities share the same application context, so each one makes dav-style access more useful.
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.
Run Daptin locally, explore the live administration surface, and follow one complete application path.