# How can I set up a read-only iCal feed to share to my non-stalwart friends and colleagues?

**URL:** https://support.stalw.art/t/how-can-i-set-up-a-read-only-ical-feed-to-share-to-my-non-stalwart-friends-and-colleagues/1970
**Category:** Questions
**Created:** [October 19, 2026, 4:48pm UTC](https://support.stalw.art/t/how-can-i-set-up-a-read-only-ical-feed-to-share-to-my-non-stalwart-friends-and-colleagues/1970 "2026-10-19T16:48:51Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Disrupt](https://support.stalw.art/user_avatar/support.stalw.art/disrupt/32/278_2.png) [@Disrupt](https://support.stalw.art/u/Disrupt)
#### Post date: [October 19, 2026, 11:09pm UTC](https://support.stalw.art/t/how-can-i-set-up-a-read-only-ical-feed-to-share-to-my-non-stalwart-friends-and-colleagues/1970/3 "2026-10-19T23:09:02Z")

</div>

> [@Public Webcal/CalDav calendar url?](https://support.stalw.art/t/public-webcal-caldav-calendar-url/1946/3):
>
> Stalwart can’t publish a calendar anonymously. Every CalDAV request has to authenticate, sharing works between accounts on the server ([sharing](https://stalw.art/docs/collaboration/sharing)), and a GET on a calendar collection doesn’t return the whole calendar as one .ics file, so a webcal subscription has nothing to point at. For a public feed today I’d run a small job that pulls the events over CalDAV with a dedicated account and writes a static .ics file somewhere your web server serves it; subscribers then use that URL. If the audience …

---

_[View the full topic](https://support.stalw.art/t/how-can-i-set-up-a-read-only-ical-feed-to-share-to-my-non-stalwart-friends-and-colleagues/1970)._