HumDAV client setup
HumDAV exports contacts through read-only CardDAV. Calendar synchronization is provided by the Calendar module's native CalDAV service.
Credentials and discovery
Open the HumDAV page while signed in. It shows your account's exact URLs and lets you create, rename and revoke device tokens. Use your HumHub username and a device token for contacts. All HumDAV tokens are now CardDAV tokens. Password authentication is available only when enabled by an administrator.
Automatic CardDAV discovery redirects /.well-known/carddav to /humdav/remote/. CalDAV discovery at /.well-known/caldav is handled by the Calendar module. Your web server must forward these requests to HumHub. The configured HumHub base path is preserved.
URLs use the user's GUID, rather than their username:
| Collection | URL relative to the HumHub base URL |
|---|---|
| Principal | /humdav/remote/principals/{user-guid}/ |
| Address books | /humdav/remote/addressbooks/{user-guid}/ |
| All visible users | /humdav/remote/addressbooks/{user-guid}/allusers/ |
| Followed users | /humdav/remote/addressbooks/{user-guid}/following/ |
| Space contacts | /humdav/remote/addressbooks/{user-guid}/space_{space-url}/ |
Enable Provide groups as separate addressbooks in your HumDAV user settings to expose the Following and space address books separately. Space address books also require the corresponding administrator option. Shared space memberships are included as vCard categories. The administrator controls which optional contact fields are exported.
Native CalDAV
Use the CalDAV URL and credentials from the Calendar module's export dialog. HumDAV displays the native service URL and can include a CalDAV account in Apple profiles. That account uses the Calendar module's token service and a username-based native principal URL, independently of the CardDAV account.
CalDAV access, synchronization permissions, credential expiration and revocation are managed by Calendar. Revoking a HumDAV device token revokes its CardDAV access; it does not revoke the separate Calendar credentials. Clients using the former /humdav/remote/calendars/ endpoints must be configured for the native Calendar service.
iOS and macOS
The Automatic Configuration Files tab provides Apple configuration profiles. Downloading a profile creates a dedicated CardDAV token. CardDAV is included in every profile. The Include CalDAV configuration from the Calendar module checkbox is selected by default when Calendar is enabled; clear it before downloading for a CardDAV-only profile. Without an enabled Calendar module the checkbox is disabled and the download contains CardDAV only.
CalDAV payloads contain a separate token generated by Calendar and the native Calendar principal URL. The generated profile uses the host, port and HTTPS setting of the current installation.
Exported contact data
Contacts contain the public display name and contact categories. Personal profile fields are exported only when the requesting user has the target user's View your about page permission and the individual profile field is visible in HumHub. Hidden address components, phone numbers and birthdays stay hidden. The birthday's hidden-year setting is respected.
All optional data exports are off by default. Administrators can enable postal addresses, profile images, birthdays, gender, phone numbers and URLs separately. E-mail additionally requires the Export e-mail addresses setting and a visible virtual E-mail profile field; enabling the module option never bypasses HumHub's profile visibility. The same e-mail restrictions apply to DAV principal metadata.
CardDAV copies contact data to external clients. Later permission changes affect subsequent server responses; copies already stored on devices may remain there. Restrict Allowed users in the module settings to control who may use this export.