Tell us how we could make Heartbeat better for you.
Feature Requests
Allow members to join multiple cohorts of the same course
Allow Members to Access Multiple Cohorts of the Same Course Simultaneously Introduce a setting or permission structure that allows returning members (e.g., from past cohorts) to join and view a new course cohort without losing access to their original/past cohort space. Currently, Heartbeat restricts a member's view to a single cohort, meaning that if a member wants to participate in an updated course run, administrators are forced to move them out of their previous cohort group, overwriting their historic access. Grant access to concurrent or multiple cohorts of the same course so members can reference past materials while engaging with new ones.
Indefinite option for recurring events
Add an "indefinite" option for recurring events so they do not have to be set with an end date. Alternatively, provide a drop down for the year so that setting a far-off end date does not require clicking and moving through hundreds of months one by one.
Make recurring Events public
Allow recurring Events to use Public visibility, so a regular series (weekly meetups, monthly calls) can be shared with people outside the community who can then view and RSVP to it. Today the Public option under Visibility & Discovery is disabled once a repeat frequency is set, so the only way to promote a recurring session publicly is to duplicate each date as a separate one-off public Event.
Assistant Admin role with access to manage specific channels or groups only
We run a community with around 100 local town groups (not all added yet), each with its own private channel and a volunteer Latte Leader. We'd love a role, such as an 'Assistant Admin', that can manage who has access to specific channels or groups (for example, a leader adding members to their own town's channel and group) without having access control over ALL groups across the community. At the moment leaders can't grant access themselves without much broader group permissions, so every request comes back to the admin. At 100 groups that doesn't scale. A role that is scoped to chosen groups or channels would let us hand local control to volunteers safely. Our reply from the support team will come to your email.
Automatically remove RSVPs when someone leaves a group invited to the Event
RSVPs aren't removed automatically when someone leaves a Group invited to the Event
Customizable right side panel in channels
Allow customization of the right side panel in channels, which typically shows upcoming events, trending posts, etc., so things can be pinned to it — for example a big event a month out or new resources or courses.
Option to disable comments platform-wide, especially in Courses
Provide admins with the option and ability to turn off comments anywhere on the platform. In Courses specifically, clients should be able to go through the course content and have their own experience without being distracted or influenced by anyone else's thoughts, opinions, and reactions.
Option for admins to turn off comments in discussions
Ability to Turn Off Comments in Discussions Add an admin-level option to turn off comments anywhere on the platform. In a discussion thread specifically, this would allow creating a read-only broadcast channel.
In Progress
[Narratively] Voice Channels: let admins and moderators mute everyone in a call at once
Add Mute all for Voice Channel participants with Moderate other Members permission. Narratively runs weekday Daily Quiet Writing Hours and Weekly Tech Office Hours; individual open mics disrupt sessions. Zoom's Mute All is the suggested workaround, moving their most frequent sessions off Heartbeat. Ticket Info Community ID: dfeaf696-48ee-47df-b6a8-5e3402c41db9 (Narratively Community) User email(s) for those affected: james@narratively.com (Administrator) Issue details (include screenshots and steps taken): Mute all should mute every other participant, including guests and mobile participants, leaving the initiating moderator's mic unchanged. Reuse Moderate other Members; members without that permission must not see the action. Existing individual Mute and Kick must remain unchanged. Keeping participants muted and joining with mics off are separate requests, outside this issue. Implementation context on master: apps/heartbeat/src/features/voice/VoiceChannelMember.tsx: Mute/Kick menu gated by Permission.Moderate. apps/api/src/sockets.ts, voice/muteMember: publishes MuteSelf to one member's PubNub user channel, or the voice channel for guests. libs/heartbeat-frontend-data/src/lib/redux-middleware/handleIncomingMessages.ts: MuteSelf calls changeMuteStatus(self, true); recipients can immediately unmute. Related demand: Featurebase “Mute everyone (for admin)” has 29 votes and has been open since June 2022; Zendesk 51896 also requests bulk mute. Default-off microphones are separately requested in Zendesk 55648 and Featurebase “Mute Mic on Voice Calls by default.” Repro Current behavior: on web/desktop, a moderator joins a Voice Channel, hovers over each member in the sidebar, opens the three-dot menu and selects Mute, repeating for each person. Muted members can immediately unmute. Mobile moderators have no Mute or Kick option. Acceptance: in a call with at least three participants, including one on mobile, a moderator clicks Mute all. Every other participant's mic turns off and displays the muted icon; the moderator's mic remains unchanged. A member without Moderate other Members does not see the action.
Watch list for saving masterclass recordings
Add a watch list feature so members can save masterclass recordings they want to come back to, similar to watch lists on streaming channels. The library contains over 200 masterclass recordings.
Admin-editable helper text to clarify passwordless sign-in screen
Allow community admins to add a short custom line of text to the sign-in screen. Heartbeat is used for the paid membership community, and members arrive from the website's "Member Login" link at community.newvolutions.com; signed-out visitors land on a screen that asks for their email. Because sign-in is passwordless, existing members often think it is a "create account" or sign-up page and hesitate or leave. Suggested example text: "Already a member? Enter the email you joined with and we'll send you a sign-in link." It would be even better if the sign-in screen had a clear "Sign in" heading and a separate "Join" link that points to the community's landing page.
Mobile App Feature Request — Community & Channel Banners
Hi Heartbeat Team, I wanted to share some feedback from my experience building my community on the platform. I love what you've created, and I want to see it shine even more on mobile! Currently, when members open the Heartbeat mobile app, the community banner and channel banners are not visible. On desktop, these visuals are a significant part of the member experience — they set the tone, communicate the brand atmosphere, and give members an immediate sense of where they are. For community builders like me who have invested heavily in creating a warm, visually intentional experience, this means half the atmosphere is invisible to mobile users — and the majority of members today are accessing communities primarily from their phones. My specific requests are: Display the community banner on the mobile app home/feed view Display channel banners within individual channels on mobile If full banners aren't feasible, even a condensed or thumbnail version would make a meaningful difference Thank you for the incredible work you do. This platform has given my community a true home, and I'm grateful for the thoughtfulness behind every feature. I just want our mobile sisters to get the full garden experience too! 🌸 Warmly, Robyn Starr
Voice to text in pulse
Would it be possible to have the little ‘voice to text’ converter in the pulse control chats, please? I find it quite frustrating to have to type all the commands that are needed to be able to style a page the way I would like. I am currently using Gemini to dictate the instruction and then copying and pasting into pulse. Being able to tweak the text before submitting it is a good thing so ‘just’ getting it to turn voice to text in that field would be so helpful. Alternatively being able to manually adjust, edit and style a page would also help. Thank you.
Restricted API keys and granular permissions for chatbots
Restricted API keys and more granular administrator permissions, specifically for AI chatbots that only need access to direct messages is a key feature for both automation and data privacy. I believe this would be a valuable feature for other community owners who want to integrate AI while keeping their members' data secure, given the existing API constraints.
Find your own posts and comments
There's currently no quick way to find your own posts and comments. You have to remember where you posted. This compounds in communities with course-sized channels carrying 40+ threads, where members lose track of their own contributions and stop exploring as a result.
Option to have the document navigation panel closed by default in Resources
When a member opens a document in a Resource, the navigation panel beside it opens by default and lists the other documents in the same folder. Today the panel only hides itself, for members, when the Resource holds a single document, so an admin who links members straight to one document has to restructure into one Resource per document to stop the others showing. Request: a setting, per Resource or community-wide, to have the navigation panel start closed (or be hidden) when a document opens, so admins can send members to a single document without restructuring their Resources.
Emoji search for reactions
Enable emoji search Add emoji search to the reaction picker so a specific emoji can be found by typing its name (e.g. searching "heart" to find the heart or heart hands) instead of browsing through the emoji sections. Without search, quickly supporting or engaging with community posts loses its appeal.
MCP Connector 🤖
This will allow Claude or Codex to update our community spaces, easily create content, and understand community trends. I think it's worth fast tracking as it will benefit all the communities in Heartbeat. Please, please….and Mucho Thanks 🙏
Return event host in event info API
API for reading events: return event host The API call for getting event information should return (the name of) the event hosts. https://heartbeat.readme.io/reference/getevent