Starting October 15th, Discourse updates include a new option to set a chat channel as the site’s default homepage. This feature allows administrators to select a specific channel via a secondary setting; if a user cannot access the selected channel, the homepage falls back to the first item in the top menu (typically /latest or /categories). Administrators can also enable read-only previews for anonymous visitors by adding anonymous users to the chat allowed groups setting.
While Vsekraski requested visual examples, awesomerobot clarified that there are no visual changes other than a sign-up prompt for logged-out users. A discussion followed regarding whether the channel list page could be set as the homepage; awesomerobot noted that while possible, the current implementation only renders on mobile screens.
tobiaseigen highlighted a use case for client portals, expressing interest in directing clients to specific private channels within secure categories rather than general topic lists. They proposed potential implementation ideas, such as linking primary categories to specific chat channels or allowing user-specific preferences for preferred chat destinations.
When you select “Chat channel” as an option you get a secondary setting to choose a channel. If the channel selected isn’t available to someone, the homepage falls back to the first option in the top menu setting (often /latest or /categories).
If you’d like anonymous visitors to have read-only preview of the homepage channel you can add anonymous users to the chat allowed groups site setting.
This makes it a little easier to start a new community with a chat-first approach
Sure! I’ve added a couple screenshots to the original post. There’s no visual change, chat continues looking the same as it does when not set as the homepage. Logged out visitors get a prompt to sign up instead of the text input.
I am using Discourse as a client portal where I mostly work one on one (and in small groups) with my clients in their secure category. They can additionally join community discussions and chat if they feel comfortable doing so.
I really like this new opportunity to drop clients into a chat channel instead of the topic list, but would like to drop them into their own channel that is part of their secure category. I would be waiting there for them.
Realizing this is not possible now and am not sure how it would be implemented.. some ideas that came to me:
by primary group - specify a category as “primary category”, and then specify a chat channel as the “primary chat” for the category. That’s alotta primaries!
by user preference - allow members to specify their preferred chat channel, with the ability to set this automatically for new members in the invite, based on a custom user field, or some other automation