Creating and Managing Custom Calendars via the CalDAV Creator Tool

Created by Curtis Hammock, Modified on Sun, 15 Nov at 7:22 PM by Curtis Hammock

In addition to each user's default calendar, administrators can create additional custom CalDAV calendar collections for any user mailbox (see How to Sync Calendars Across Devices using CalDAV).


How to Create a Custom Calendar

  1. Log into the Account Admin portal (purelymail.com/manage/login).
  2. Navigate to Tools > CalDAV Calendar Creator (or go directly to https://purelymail.com/manage/createCaldavCalendar).
  3. Select the target user mailbox from the dropdown.
  4. Enter a name for the new calendar collection and click Create.

The tool generates a new CalDAV calendar collection (https://purelymail.com/webdav/<userId>/caldav/<calendarName>/) that automatically appears in connected CalDAV clients such as Apple Calendar, Mozilla Thunderbird, and DAVx⁵.


How to Delete a Custom CalDAV Calendar

Because the CalDAV Calendar Creator tool only creates new calendars, unwanted calendars are deleted directly from any connected CalDAV client application:

  • Apple Calendar (macOS / iOS): Right-click (or tap the info icon next to) the calendar name in the calendar list and select Delete.
  • Mozilla Thunderbird: Open the Calendar tab, right-click the calendar in the left sidebar, and select Delete Calendar.
  • DAVx⁵ (Android): Open DAVx⁵, select your Purelymail account, tap the menu icon next to the calendar collection, and select Delete collection.

Deleting the calendar in your client sends a standard CalDAV DELETE request to Purelymail and permanently removes the calendar collection and its events from the server.


Still Need Help?

If you've followed these steps and are still running into trouble, check our Purelymail Support guide.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article