One of the challenges we face in our community is relying on other tools to issue points and badges related to activities outside of the community. I would like to have the ability to issue points and badges in a simple and flexible via MCP. This skill will save hours of work.
I love being able to use Rule chains to tie rules that need to run in a specific order together under one common schedule. The problem I have is that may times a reporting Data Design is dependent on the Rule jobs finishing. We solve this by just offsetting the Data Design Execution time to run and hour after the Rule Chain finishes, but the amount of dependant schedules that we have is getting out of hand.It would be awesome to expand Rule Chains to a larger feature that could include Data Designs as part of flow so we can run some of these more complex workflows under a single schedule.
I attempted to post this to the comments thread on this post, but I feel it warrants its own idea post.After reviewing the June 2026 on-demand release notes for both MCP enhancements, I want to respectfully share some honest concerns because, based on what I’m reading, I think both designs seem to share the same structural problem.THE CORE ISSUEThe release notes describe this directly:"Existing reports now serve as a knowledge layer for Gainsight CS MCP" because "reports encode your organization's terminology."There's an important distinction here: a knowledge layer describes what exists. A semantic layer — what's actually needed to ground an LLM — governs what data means, and who can see it. Reports provide the former. This design, however, assumes to provide the latter. FEATURE 1: QUERY USING EXISTING REPORTSWhat the docs appear confirmMCP searches reports you have access to, matching on names, descriptions, and filter logic Once a report is identified, MCP can dynamically: incorporate fields not in the report, add/modify/remove unlocked filters Only MDA-connection reports are included (SFDC and external connections excluded) Only reports run in the last 90 days qualify Reports without meaningful names or descriptions may not surface at allWhy this creates a potential governance riskThe report isn't a boundary — it's a discovery hint. Because MCP can add fields and strip unlocked filters at query time, a deliberately narrow report becomes an unscoped query template. Locked filters are honored (a real control worth acknowledging), but locked/unlocked filter status was designed for usability, not as a security perimeter. Few orgs have audited this with "an LLM can remove unlocked filters" in mind. Data and metadata hygiene becomes a functional dependency. Report naming, descriptions, field selections and filter quality now directly determine AI accuracy. In environments with reporting sprawl — inconsistent naming, legacy artifacts, overlapping definitions or (heaven forbid) self-service reporting access — the matching surface becomes both unpredictable and high-maintenance. The 90-day heuristic is a poor proxy for curation quality. Frequently run doesn't mean accurate. QBR and annual planning reports — often the most carefully curated assets — can fall out of scope. What counts as a "run" is also undefined in the docs (dashboard render? scheduled export? any user?), making the effective discovery surface hard to predict. Cross-team report access is additive, not clarifying. Different teams may hold reports built with different filter logic, field selections, and naming conventions. MCP matching across that surface doesn't neutralize those differences — it inherits them.FEATURE 2: QUERY YOUR PORTFOLIO DATAWhat the docs appear to confirmPortfolio scope is determined exclusively from Gainsight Home filters No other Gainsight surface or configuration is read At least one Home filter must be configured — or the feature doesn't workWhy this creates a potential governance riskFilter state is invisible in the query interface. Results change silently when Home filters change, with no documented indication to the user that a filter is shaping the response False negatives are a design outcome, not a bug. Relevant accounts outside the current filter simply don't appear. Not every team uses Gainsight Home. For those that don't, the feature is inert. A UI personalization preference is not a book-of-business definition. Using Home filter state as the ownership model is a fragile abstraction for anything downstream that matters.BOTH FEATURES CAN FAIL IN OPPOSITE WAYS — FOR THE SAME REASON In both cases, admins have no surface to adjust the behavior to their environment. ADDITIONAL POTENTIAL GAPS WORTH FLAGGINGDerived field behavior under dynamic modification is undocumented. In-report formula fields exist only at render time. What happens when MCP modifies the report's logic first is unclear. Data Designer outputs that overlap with base fields have no documented precedence model. Associated record resolution is an open question. Associated Record WHOID/WHATID lookup relationships aren't consistently resolved even across core Gainsight features today. How MCP would handle this when those objects become relevant is undefined. Absence of inclusion on a Gainsight report is not evidence of unimportance.It's often evidence of the opposite — the analysis mattered enough to do properly (or with broader visibility) which meant doing it outside Gainsight. GS data is exported and surfaced in a BI tool because Gainsight's reporting layer couldn't handle the logic required. Those are often the highest-stakes analyses: compliance rates, portfolio-level KPIs, multi-source metrics. No Gainsight report exists precisely because the answer required something more capable. The MCP's discovery model inverts this. It treats a Gainsight report as the signal of relevance. So the analyses your org trusts most — the ones sophisticated enough to require a BI tool — are systematically invisible to it, while simpler, natively-built reports qualify.No audit trail. Neither the release notes nor the admin guide indicates who to know which report was matched, or what filter/field modifications MCP applied to produce a given answer. The tool surfaces changes outside admin change management. This release alone requires users to disconnect/reconnect (Claude) or an admin app refresh (ChatGPT). MCP capabilities shift between releases, outside any change process the admin controls.And these are just the things that came to mind for me. WHAT'S ACTUALLY NEEDEDThe release notes describe, at a high level, what each feature does — reports are matched on names, descriptions, and filter logic; locked filters are honored; only MDA-sourced reports run in the last 90 days qualify. However, it falls short on important details like how matches are ranked when multiple reports qualify, what counts as a "run," and how filter modification decisions are made at query time.Admins are being asked to govern a surface they can observe but neither directly affect nor predict.What's needed is a purpose-built MCP configuration layer where admins can:→ Explicitly define which objects and fields are exposed→ Attach business meaning to fields — definitions, context, caveats→ Designate authoritative sources (Data Designer or otherwise) rather than inheriting whatever reportsexist→ Declare ownership logic directly, rather than inheriting Home filter state→ Decouple AI context from UI state and report library condition entirelyThe MCP Server has real potential; however until admins can explicitly define context and tune it to our own unique business requirements — rather than inherit it from artifacts that require that business context to understand and interpret — the orgs with the most mature and customized environments are the ones who will trust it the least.
This feature request aims to automate the validity of the topics sitemap by including or excluding specific URL based on website indexing rules at post/topic level or category level.The idea is simple:All URLs with a 200 HTTP status code are included in the sitemap by default. (Already live) directories for categories and pages that have been set to noindex should be automatically excluded The sitemap is automatically generated and updated whenever there is a change in URLs, robots meta tagsThis improves SEO quality, reduces administrative overhead, and helps search engines crawl only content intended for indexing.
The Weekly AI Digest is basically the first thing users see when they log into Staircase directly.Despite what this copy below says, according to Gainsight it evidently doesn’t matter what accounts you are assigned or, if you’re a manager, what accounts your reports are assigned, it will just summarize the business in general: As a first impression, given it also says it is *for me*, that’s neither super intuitive nor all that great an experience.I would like the ability to have the digest tailored to either the filters on my dashboard, or, at the very least, have the option somehow for it to do what it says on the box: have it related to ‘my’ accounts and/or those of my reports.
Member Group Owners really need to be able to see members email addresses. When people request access to a user group currently the group owner cannot see their email addresses in the front or back end. This is important for validating if they are actual customer, and in some cases to see which company to ensure there is no issue with competitors accessing a specific area. Thank you, Sara
Is there a way to apply a Success Plan template to multiple Success plan types? Or even change the type after added? I am finding it difficult to move things around as an admin and and end-user after something has been created. For Example: I have multiple success plans and one of the templates for success plan type 1, I'd like to also have available for success plan type 2. Is this doable? Or an enhancement request?
I don’t know if there is an idea out here for this already or not, but admins need the ability to deselect dependencies when creating an X-Org 2.0 migration bundle because the scope of the default dependency generator is too broad. As an example, I created two Playbooks associated with a single CTA Type and two Success Plan templates associated with a single Success Plan template. Nothing wild, no custom fields, or anything.The Migration tool identifies 128 dependencies including CTA Types and Success Plan Types that are unrelated to any of these that I am attempting to migrate (including ones that are INACTIVE in my sandbox), in addition to other fields under Company, Call to Action, Task, etc. that did not require/have any changes made to them as part of the generation of these assets. I understand Gainsight is trying to ensure that any dependent assets that may be different/have been adjusted as part of the process are carried over, but this control needs to be given to the admin to determine which dependencies are relevant and which aren’t.For many of us, our Sandboxes are not necessarily 1:1 matches to Production. We often use them as “scratch pads” for testing new features, processes, etc so some of the dependencies the migration tool automatically selects could contain values/components that are not intended for promotion to production.We need more granular control over it. --------Success Plan Template I’m trying to migrate, under the “Extend Product Onboarding” Success Plan type: Migration dependencies include irrelevant SP Types: Including ones that are deactivated:Which it does attempt to insert, since it does not exist in my Production environment: And then attempted updates/insertions to DA Picklists which the logs don’t even define to which picklist they are related to forcing me to try and deduce it but also are either not different between Sandbox and Production and is unclear why they are attempting to update OR are, again, values related to deactivated assets:
Users should be able to synchronize UI settings from Production to Sandbox and vice versa, depending on their workflow.Please provide one or more of the following capabilities :Export/Import of layout and theme settings One-click synchronization between Production and Sandbox (in both directions) Bidirectional migration of appearance-related settings (Production → Sandbox and Sandbox → Production) API support for backing up and restoring these settings
Hi Team, a customer has requested the ability to upload an image in the CTA comments field. They’ve included the attached screenshot illustrating the error message their team receives when attempting to upload the image to the CTA comments.
With the recent automatic email capture feature it appears CSMs can only associate individual emails to Gainsight objects in Timeline, not an entire email thread at once. This enhancement would enable end-users to associate an entire thread to another record (r360, etc) instead of having to handle the association of each email manually.
We would like to have the possibility to edit the meta title separately from the topic title.In the SEO world the lenght of the title is restricted but the heading 1 can be longer, so being able to edit them separately would give us a bit more room in optimizing. @timcavey suggested earlier that editing meta descriptions should be editable → this idea is for the same purpose but we’d also like to be able to edit the title and the heading.
Add the ability to hide/remove a post from the “activity feed”. This would be useful when doing campaigns which require many posts, but where we don’t want each post to crowd out other posts from users.
It would be great if Gainsight Assist and Playbooks supported multi-version email templates. We are rolling out Gainsight to our Client Success Managers that manage International accounts/clients that speak different languages where this is needed. As a work around, we set up a JO but there are some touch points where this would be helpful. Rather than having multiple individual email templates for each language, or a playbook for each language, we would like to group them.
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK