How can you share documents with customers in the spaces? If we have certain ppts and guides around our product or new updates which we may want to share with the customers in the spaces.
Hi! I am trying to test out Spaces welcome email that a customer will receive. I have gone into the backend to try sending the email to several different email addresses (my work email and personal email and tried resending it to internal users who already have access) and when I click “send” I continue to get the “unable to send email at this time” error message. I have gotten this a few times the last couple of days. Is there something I am doing wrong? The same error happened when our GS admin tested it to try to send to me as well. Thanks
I just configured and published a Spaces Layout. But Spaces is still not visible on the 360-layout settings to add it to C360
Hello,Is there a way to customize the Spaces email invite that goes out to the customers?
CSQLs are a core part of our qualification workflow, but they currently lack a couple of capabilities No shareable deep link – We cannot generate a direct URL to a specific CSQL record for collaboration with Sales or leadership. No inline editing in reports – Updates require navigating into each C360/R360, making bulk hygiene or status updates inefficient. This creates operational friction, especially in high-volume environments.Request: Enable unique, permission-controlled deep links for individual CSQL records. Allow inline editing (including bulk updates) for CSQLs within Report Builder/Dashboard These enhancements would significantly improve collaboration, data hygiene, and scalability of the CSQL process.
I’m not sure if this is a recent change and it seems that it is, but even if not what possible reason is there to clip the rule names and then have all this blank space next to it? I use a wide monitor, but this is a window taking up only half my screen. It looks the same on my smaller laptop. This is not a screen resolution problem, this is a design problem.This kind of design does not seem to indicate the users experience is considered at any point, but instead some arbitrary aesthetic. @ophirsw I know you’ve seen my various posts on whitespace and I’m sure are thrilled to see another :) I don’t search these things out and I’m not particularly jazzed about writing these but it seems that this issue of gratuitous whitespace at the expense of product usability seems to keep happening. Is there a better way we can communicate how inconvenient these changes are? Is there some other method we can employ that will have a substantive impact on the way these changes are considered to better take the user into account before implementing? Not trying to be dramatic, but more and more screens we jump to are getting increasingly irritating to use. Thanks :)
Currently we’re in the process of updating our Partner process from sharing a simple Success Plan with them to utilising the Partner licenses and through Partner Customer Success options. One major issue that we have uncovered is that you are unable (or at least I can’t find a way currently) to hide certain email templates or template folders. This means that partner users can have full access to your entire library of email template assets. I don’t think we will be able to release this to our Partner users until this is rectified via adding some permissions to the folders so that we can manage these and keep them out of sight of the partners and only share those that are applicable to them. If anyone has a workaround please share as I’d love to get this running.
Following the completion of our gamification revamp, we require enhanced reporting capabilities to track user progression between ranks over defined time periods. Specifically, the ability to quantify how many users move from one rank to another within selected time frames would provide meaningful insights into engagement levels, performance trends, and the overall effectiveness of the new gamification structure.I’ve reached out to support, but once again encountered limitations around reporting within the Gainsight platform. It’s increasingly challenging that such fundamental reporting capabilities are not readily available. Our leadership team is requesting these metrics, and at the moment, we’re unable to provide clear answers, which is becoming a significant concern.
It would be great if we could implement a 'remember me' feature in the community login flow. Right now your login expires once you close your browser, which means that users that switch a lot between devices or browsers, like our super-users have to login each time they visit our community. It can get really annoying for our community members, because as we all know, the number of visits a day -especially for super-users- can get really high. And we all want our communities to be as easy accessable as possible of course, so it would be great if you could built this feature in.
To level-up analytics insights in Gainsight, it’d be awesome if we could set colors for fields based on their field values in tabular reports. Just like you can do this in Conditional Formatting in Google Sheets or Excel, where it highlights a cell value based on the conditional criteria assigned to it. Related Posts
Hello Gainsight Community!I’m your friendly, neighborhood Gainsight Support Agent, submitting this Feature Request on behalf of a customer:The current filename format includes too many information: “Success Snapshot title, Account Name, Date Time, AM/PN, Timezone” This causes issues with opening the file with error “filename too long”. CSMs currently have to rename the zip file first to open the file.It would be great to have an option of modifying the filename format such as another data e.g. BU number instead for Account Name, or remove Time and Timezone, ie “Success Snapshot title, BU, Date”
Would it be possible to put variable values into the Timeline Integration sync jobs? The use case here is that some users log activities for the future in Salesforce, but the CS team does not want them synced to the Gainsight Timeline until the date arrives. We would prefer the filters behave similar to the way Reports/Data Designer filters work so that we can have the right data synced over at the right time. The ability to select “Due Date Only <= Today” is a prime example of how we could use these enhanced filters here to only sync activities that do not have future dates. Currently, we only have the option of “Custom” for the date filter, meaning which is better for one time or manual syncs, but not recurring automate syncs.
Hi all, I would like to be able to further segment community content by "labelling" topics under predefined "tags". A Label is not a Public Tag or a Mod Tag, it's a tag that we have pre-defined, and suggest the user to add to his/her topic when posting. Ultimately we want to make relevant content easier to find in busy boards, or in boards with a broad title. For instance, we have a board called "Wireless Speakers". Being able to label each topic with for instance: Play:1, Play:5, SUB will make it easier for other users to find content that is relevant to them. "Controllers and Software" could have the labels: Pandora, Spotify, Sonos, etc. In our "Troubleshooting" board we can ask users what they are having problems with, at the time of topic start: Is your troubleshooting request related to "Speaker", "No sound", "Wireless", "Controller", etc. This will also allow our superusers to cherry-pick the topics that they are experts in. In addition to the labels being available on front end, we'll need an API to be able to call the content into relevant support articles. Ultimately these labels will transfer to Post fields automatically. Best, Ditte
Hello again! I have another idea that I would like to share: -> the possibility to see (on the back office) the changes that either the moderators or the users did on the replies. For instance, the Google Play Console allows you to see it and it´s very useful to understand the full extent of a conversation. What do you think guys?
Moving a whole topic to another topic is a weird process, since you can checkmark all posts but the first posts. Am I missing something, or is this an unnecessarily cumbersome process?
We’d love to see more advanced automation capabilities within Gainsight CS, specifically around configurable error handling and conditional branching within Rules.Today, when a rule partially succeeds or fails, the primary option is notification-based visibility. What would be incredibly valuable is the ability to: Identify and categorize specific error types (e.g., lookup_failed) Filter on those error outcomes directly within Rules Trigger secondary actions or follow-up automations based on specific failure conditions Configure conditional branching logic similar to tools like Zapier For example:If a rule fails due to a lookup_failed error, I’d like to: Filter records by that specific error type Automatically trigger a secondary rule or action in the same rule Define a follow-up workflow (e.g., initiate an Account creation process) This would allow teams to move beyond notifications and manual error resolution and into true exception-based automation handling.
The playbook UI is becoming overwhelming when too many playbooks are in use.What I really need is the ability to organize a long list of playbooks into folders.Filtering by CTA type is helpful, active vs. inactive, somewhat useful too, but it’s not enough. We need folders for playbooks—just like we have folders everywhere else. We need to be able to organize them by success plan (for example) or by product or by anything else. Adding prefixes isn’t a real solution, especially since the UI doesn’t handle that well—the differentiating info ends up buried at the front. Suffix wouldn’t be visible… So, simply put: please give us folders.
It would be incredibly valuable to introduce layout elements such as section dividers and static text blocks within Adoption Explorer dashboards.As dashboards grow and include multiple reports, it can become difficult to visually group related metrics or clearly communicate the story behind the data. The ability to insert customizable dividers (e.g., section headers or visual separators) would make it much easier to organize reports into logical groupings such as Product Usage, Engagement Trends, Adoption by Segment, etc.Additionally, having the option to add static text blocks would allow admins to include context, definitions, metric explanations, or executive summaries directly within the dashboard. This would reduce confusion, improve stakeholder understanding, and eliminate the need for separate documentation to explain what viewers are seeing.Providing simple formatting options (bold text, header sizing, spacing) would further enhance clarity and create a more polished, presentation-ready dashboard experience.This enhancement would significantly improve usability, storytelling, and executive readiness within Adoption Explorer.
It would be incredibly helpful to have greater flexibility with report headers in Adoption Explorer. Currently, the report name appears smaller than the data points displayed beneath it, which can make the overall visualization feel slightly unbalanced and reduce clarity at a glance.It would be lovely to have the ability to adjust the font size of report names so they can be scaled appropriately for different dashboard layouts and presentation needs. In some cases, especially when the context is already clear from the surrounding view or filters, it would also be valuable to have the option to remove the report name entirely.Providing the ability to both resize and optionally hide report headers would improve readability, create a cleaner visual experience, and allow teams to better tailor dashboards for executive reporting and internal reviews.
Please enable a way to group report widgets from multiple objects into the same C360/R360 report section so we can keep related insights together without creating separate sections/tabs per object.ProblemOur “logical” views (Health, Adoption, Support, etc) often require reports that come from different objects. As we add more objects and reporting needs, the current approach becomes cumbersome: We end up creating many separate widgets/sections/tabs to surface everything Related insights get split across the page and/or tabs based on object boundaries, not how CSMs work Reporting sections are so white space heavy that if you only have one or two reports on a section, it takes up half the page and you have to scroll to get to the next part Impact Harder for CSMs to consume: related insights aren’t co-located Higher admin maintenance: more widgets, more layout work, more updates over time Scaling issue: adding more data increases UI complexity disproportionately Why this mattersThis aligns C360/R360 layouts with how teams reason about customers (“show everything relevant to this outcome”), and prevents layout sprawl as the data model grows.The following example is all one tab on a C360 that shows data related to Instances. This is all coming from 4 different objects, and now I have to add a couple more sections to this page due to dependency on new data designers that require some calculation before I can create a report. It becomes unwieldy. Would be so much better if I could group reports logically as opposed to by object.
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.