Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6159 Ideas

    MRosas
    MRosasContributor ⭐️

    Rate Limit for RepliesNew Idea

    Problem:We recently experienced more than 900 spammy replies from a single user within a day, creating a significant volume-management and moderation challenge. We would like a way to control how frequently individual users can create new topics or submit replies within a defined period.Requested Feature:Introduce configurable rate-limiting controls that allow community administrators to limit the number of posts or replies a user can submit within a specified time window.Suggested Functionality:Allow administrators to define a maximum number of posts/replies per user within a configurable time period. Support separate limits for new topics and replies, or allow the same limit to apply to both. Example configuration: 1 post or reply per user every 10 minutes. Provide different rate limits based on user roles or permission groups, if supported. Display a clear message to users when they reach the limit, including when they will be able to post again. Allow administrators to temporarily increase, decrease, or disable the rate limit when needed. Ideally provide reporting or monitoring so administrators can identify users who are frequently hitting the rate limit.Business/User Impact:A configurable posting rate limit would help prevent sudden spikes in community activity, reduce spam and abusive posting behavior, and lessen the moderation burden on community teams. It would also provide administrators with a proactive control that can be used without having to ban users or entire regions.Priority: High – The ability to limit posting frequency would provide an important safeguard against unusually high-volume activity while preserving legitimate community participation.

    katepalli
    Gainsight Employee ⭐️
    katepalliGainsight Employee ⭐️

    Allow Gainsight admins to configure the default state of the "Group by Company/Relationship” checkbox at the email template level.New Idea

    Hi Team,We got a request from one of the customers as below -Enhancement Request: Allow Gainsight admins to configure the default state of the "Group by Company/Relationship” checkbox at the email template level.Today, when a user selects "Send Email" and Group Send is used, the checkbox is enabled by default. Users who do not want emails grouped by Company/Relationship must remember to manually uncheck it each time.Ideally, when configuring an email template, an admin would be able to specify whether “Group by Company/Relationship” should default to checked or unchecked when that template is used for a Group Send. The user could still change the selection at send time; the template setting would simply determine the initial/default state.Why this would be valuable:- Different email templates and use cases have different intended sending behaviors, so a single system-wide default does not fit every workflow.- It reduces the reliance on end users remembering to manually change the checkbox for particular types of sends.- It helps admins design templates that reflect the intended workflow and provides a more consistent experience across users.- It reduces the risk of emails being unintentionally grouped when the business process calls for individual sends, or vice versa.Desired behavior: When an admin creates or edits an email template, provide a setting such as “Group by Company/Relationship by default”. If enabled, the checkbox is pre-selected when that template is used; if disabled, it is not pre-selected. Users can still override the setting before sending.