Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6159 Ideas

    kaponteContributor ⭐️⭐️⭐️

    Auto-subscribe community members to categories/product updatesOpen

    InSided is software missing one very important piece of functionality - the ability to auto-subscribe new registrants to specific forum categories, resource categories, or product updates. Lacking that, there is no way to if anyone is getting notifications. How many people are getting notifications when we publish an article in the Community? How many people are subscribed to Product Updates?Getting return visitors is paramount to the success of the Community and getting notifications drives engagement and return visits. Otherwise, people sit at the bottom of the engagement pyramid and never convert to Followers, Endorsers, etc.Community Engagement Pyramid This graphs tells me that just isn’t happening and we have a pretty good amount of activity in the Community.Cohort Analysis from GA  It would also be great to be able to manage my subscriptions via my settings page as a user. I can control whether or not I get notifications from topics, categories I am subscribed to but it doesn’t tell what those are. Previous Community software I have used gives user a panel with all the potential categories they can subscribe to and whether or not they want instant notifications, daily digest, weekly digest, or none.Notification Management for Users I have already spoken with your product team about this on a call. I just wanted to make sure it was documented in case I wasn’t articulate during the call. 

    lyndarContributor ⭐️

    Granular & bulk subscription management (Resources, sub-boards, and tags)Open

    The ProblemManaging content subscriptions is currently high-friction and restrictive. Limited scope: Users cannot subscribe directly to the Resources Board or its specific sub-boards, only to discussions and events. Click fatigue: Users must navigate to every individual page to hit "Subscribe," making onboarding or updating preferences tedious. No topical subscriptions: There is no way to follow specific Tags across the community. Proposed Solution Expand subscription scope: Enable full subscription capabilities for the Resources Board, including all nested sub-boards and resource categories. Bulk subscription preference center: Create a centralized "one-click" subscription overlay or page. When a user clicks subscribe, present them with a clean table of checkboxes so they can opt into multiple categories, boards, and sub-boards en masse. Subscribe to tags: Allow users to follow specific tags (e.g., #ProductUpdates or #BestPractices) to receive notifications whenever that tag is used community-wide. Value & Impact Higher content adoption: Users can easily follow high-value Resource documentation, driving self-service success. Improved retention: A bulk-subscription center reduces setup friction, ensuring users opt into the content they care about immediately. Personalization: Tag subscriptions allow users to curate a hyper-relevant notification feed based on topics rather than rigid folder structures.

    Jean Walters
    Jean WaltersContributor ⭐️⭐️

    Enable idea creation and status tracking within Groups (for beta feedback)New Idea

    Description:We use Groups extensively to run both open and closed product betas. Groups work well for this because they let us embed Skilljar tutorials/live training schedules via widgets, control access to sensitive/pre-release features, let PMs post directly to participants, and let participants share feedback through posts — all in one contained space.The gap is idea management. When a PM converts a beta participant's post into an Idea, it moves entirely out of the Group and into the general Ideas space. For closed betas especially, this is a problem: the idea (and its status updates) is no longer visible to the people who raised it, and it's disconnected from the confidential context it came from. Participants lose visibility into whether their feedback was actioned, and PMs lose the ability to close the loop from within the same space they're already using to manage the beta.What we'd like: a way for Ideas to live in — or be visibly synced with — the Group they originated from, so that:Beta participants can see the status of ideas raised during the beta without leaving the Group PMs can convert a post to an Idea (or link a post to an existing Idea) without losing the Group context This works for closed/private Groups just as well as open ones, respecting the same access controlsWhy it matters: Idea tracking is currently the one piece of the beta feedback loop that breaks the otherwise-seamless Group experience, and it's a growing pain point as we scale the number of concurrent betas we run through Groups.