# Exposing LiveKit status in site settings serializer

**URL:** https://meta.discourse.org/t/exposing-livekit-status-in-site-settings-serializer/411428
**Category:** Support
**Tags:** voice
**Created:** [September 1, 2026, 11:23pm UTC](https://meta.discourse.org/t/exposing-livekit-status-in-site-settings-serializer/411428 "2026-09-01T23:23:01Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [September 2, 2026, 12:38pm UTC](https://meta.discourse.org/t/exposing-livekit-status-in-site-settings-serializer/411428/6 "2026-09-02T12:38:24Z")

</div>

> [@nicolsdennis](#):
>
> after reviewing for past 5hrs I tagged the members from the core commit/merge of voice.

If you think 5h is too much to wait, you may be new to the concept of async comms in forums. Welcome!

> [@nicolsdennis](#):
>
> RoomSerializer#expected\_transport covers the per-room case nicely, but that requires fetching rooms first, and it comes back empty when voice\_public\_access is off, even on a site where LiveKit is fully configured.

I will investigate this and come up with something we can use.

---

_[View the full topic](https://meta.discourse.org/t/exposing-livekit-status-in-site-settings-serializer/411428)._