Feature Requests

We desperately need more customization of landing pages. Removing buttons, changing location of buttons, changing titles on various buttons, placing text in different areas and different fonts. The pages should be fully customizable.

Typically, when a member leaves our community on Heartbeat, as community owner/admin of a community, we receive a notification email that alerts us of their departure from the community. Currently, such notification email only provides the name used by the member at the point of departure (Megan P in the example provided). Given that we handle a lot of members' administrative issues manually on our backend, can we please request that when a member leaves a Heartbeat community (and opts to delete all their personal information), such outgoing member's registered email be added to this notification email that community owner/admin receives? We'd be grateful if you could kindly consider the implementation of this request as it would help us greatly in managing our community more effectively. Appreciate your kind consideration in this matter. Cheers, Chriss Lim

Feature Request: Role/Group-Based User Directory Access Control We need the ability to restrict User Directory viewing access based on roles or groups, not just management permissions. Current Issue: Cancelled members (with basic "Members" role) can still view the full User Directory and see all active paying members, creating privacy concerns. Requested Solution: Add User Directory access permissions to roles, similar to how other features work - so we can restrict directory viewing to paying members only while keeping cancelled members in the community with limited access. Business Impact: This affects member privacy and our ability to maintain a secure environment for paying members. Current Workaround: None available - directory is all-or-nothing (completely hidden or visible to everyone). This has been on my list of challenges for a while. We don’t want to completely remove/ deactivate our cancelled members from Heartbeat as we want to encourage upsells at a later date. But currently even though the majority of the channels are locked to them the directory is not. And whilst I understand removing specific group attributes from the directory maybe a challenge I do think that there should have limited viewership of the directory after they stop paying. Mainly from a privacy perspective more than anything. We need to protect our paying members privacy.

To avoid accidentally deleting entire Courses and Channels without the ability to recover it

It would be awesome to be able to change the "Post in Channel" button in Course Assignments as well as hide the Channel name beside it.

I want to be able to pin specific members to the top of my directory

At the moment, only administrators and moderators can @ mention an entire group. I'd like users to be able to do so too. This could be a setting that the administrator can enable / disable depending on the needs of his community. This would be very useful for my community, as currently, users tag me personally so that I set the @mention manually whenever necessary (several times a day).

If a user has a role that allows them to create a channel, they can by default see all category titles (even if those categories only have channels they can't see/don't have access to it) I understand the reason for this is so they can theoretically add new channels to those categories. It would be great if the admin could tie the group permissions for channel visibility to the parent category so that they match. For example, I have a remote only team and we use our heartbeat community as a workspace. All of our channels are under a "team" category. There's no scenario where one of our customers would need to add channels to that category (but we do want them to have that permission for other categories). Thanks!

I'd like to be able to create a lower ticket subscription offer where DMs are disabled so customers are forced to post on the channel. This will allow engagment to increase and ability to build an FAQ that point to the post rather than answering the questions over and over again in the DMs. Note, it should be if member is in this group, DM access is disabled no matter what other groups they are in. and no, I wouldn't like to disable DMs across the board, higher paying clients should still have DM access. 😊

I'd love the ability to add html code to our entire community. This would allow admins to add features such as embedding support chat boxes (rather than having to go through DMs), using site tour apps (embedded with the html), and incorporate tools like WisdomAI to provide even more support to our members. I'm sure there are many other applications for this as well.