There was much well deserved excitement around this finally being released: However, one very critical, and very key component of this was not only left out, but there was no indication it was left out at all and what the expected behavior should be - the fact the lookups don’t actually *dynamically update*. They refresh at the tenant level every 12 hours.Here is an example:You set up a Data Designer (DD) that has a lookup to the Company MDA, which itself has been turned into an MDA object. You have a rule updating the Status of your Company records After this rule runs, your DD refreshes (within say 1 hour) You run a report on Company>Status and a report on the DD with Company>Status and whatever other fields you need You compare the two “Status fields” between the two objects - they will not match for as much as 12 hours. Any records that were updated by the rule, will not reflect in your DD even if the DD was refreshed right after the rule ran, and it is referencing the Company table via the new lookup method and there is nothing you can do about it*.What does this mean?Refreshing your Data Designs will no longer give you the most up to date data on *any* object you have set up this lookup to. To be clear, if you’re not using the new lookups, the DD work as they always have as far as I can tell. Testing new data becomes more challenging, because if you need to use a lookup, then you have to wait 12 hours for everything to refresh??? There is (as of this writing) no documentation on this limitation on what the delay is, how it works, when the syncing is, if it can be changed. Nothing. As bad as this lack of refresh is, it’s made worse by the fact it was not communicated in any way. What is the ask?First and foremost - lookups should refresh on a per DD basis. If a data design refreshes, the expectation is that the data in there is accurate *at runtime*. Secondly - this needs to be documented, and *proactively* communicated to admins. Even just the current state. Adding the documentation is one thing, but making sure there is proactive outreach to admins is critical. In the short term, at the very least, reduce the time for this syncing This is a glaring problem that undermines the one of the main utilities of this being released in the first place, and the fact that it is not documented anywhere is extremely disappointing to say the least. *support has indicated it might be possible to reduce this time on a per tenant basis.
I’ve been thinking about scheduling PX engagements and the snooze option. I don’t use it often because it counts as a view, so it doesn’t change the schedule. So, when a user gets their last view in the schedule and they click snooze, they are expecting to see that engagement again, but with the current functionality, they won’t see it again.A couple potential solutions:Make the click on snooze not count as one of the views. For example, if the schedule is set to show the engagement 3 times with at least 7 days between views: Upon first view, user just closes engagement; that counts as their first view and they have 2 left. Upon second view, user clicks snooze. This should not count as a view and they should still have 2 left If user continues to click snooze on their third view, they should qualify to see it again in 7 days; potentially indefinitely if they keep clicking snooze. Add a SNOOZED option to the In App Engagement audience rule. This would give us the opportunity to target users for a “last chance” at the engagement. If the user has previously only VIEWED or COMPLETED the engagement, they wouldn’t qualify to see the last chance engagement. My assumption here is that if a user is clicking snooze, they want to see the engagement again and just may not have time to review it at that moment. (That is my thought when I’m presented with a snooze option.) Add SNOOZED option to the Event category I’m referencing this article: cc: @Lake1211 @Gainsight2022 @woodlande @wheelern @rterakedis @aroberts @jmobley @aharkut
Hello GS, with the changes to the AI bot deleting spam, it would be beneficial to get these two columns added to the user overview page. This will allow admins to instantly see accounts that were recently created and posted spam right off the bat.
In our community, the author of a question, some trusted power users and moderators have the permissions to mark any answer in a topic as "Best answer" (solution). The issue: Currently it is not possible to analyze which user marked a "best answer" (solution). So we can't see in Analytics if the author of a question marked it, showing he/she is satisfied with an answer, or if a power user or moderator marked his/her own answer as "best answer", thinking it was the correct answer. This makes quality control harder. Solution: We would like to have the user name as a data field in the exports available. This way we can better check if solutions have been marked for the right reasons. Also a data field for who marked a solution could be used for future gamification purposes. This way it is possible to have an incentive for authors of questions to mark a solution or to have an incentive for users with the permissions to mark solutions.
When creating a new Rank, you can set requirements around minimum number of logins (screenshot below). This tells me that the data exists and is accessible by the system. I propose making that login data (and why not points too while you’re at it, idea below) a standard part of all user data exports.
As an admin, we’re looking to set up a new customer C360 view that is assigned to any customer in our instance with a type of Prospect or a New Customer created in the last 30 days. Our hope is that, for these customers, they have a much simpler layout that focuses on their onboarding & the handoff between Sales & CS before we introduce additional C360 items.However, it doesn’t appear that Created Date (or any date field) is available as a filter on the layout.This means that, to accomplish what we wish, we’re going to use some other field type (either Stage functionality for standard or a custom field we load to) with rules handing that load. It ultimately adds to the complexity for something that should really be more seamless.Please allow us to use date fields as filterable criteria for C360 layouts to streamline this.
We’ve had an SEO audit done on our community. There are a number of improvements we’ll present here as ideas. This one is about linking.Google has shown to ignore robots.txt on more than on occasion, so simply blocking these in robots.txt is not a surefire solution. A more robust solution is relying on rel=nofollow and robots meta tags to guide crawler / indexation behaviour. Hence we propose a few ideas that would be beneficial in assisting crawler behaviour and guiding crawlers to the most relevant content. Ideally these would be integrated as toggle-able functions in order to allow users to customize crawl behaviour based on their needs.Sorting urls - Allow a rel="nofollow" to sorting <a hrefs>, and Add meta robots noindex/nofollow directive to pages with ?sort query present. This'll stop crawlers from having to go over multiple iterations of the same pages. PostId - Allow a rel="nofollow" to certain <a hrefs>, namely for links featuring ?postid queries and add meta robots noindex/nofollow directive to pages with ?postid query present. Member pages - Allow a rel=nofollow attribute for URLs referring to them Search pages: Allow a meta robots noindex/nofollow directive to search pages. Pagination - Add a "jump to last page" button as part of pagination
The Gainsight community platform supports several external SSO providers like OpenID, SAML etc., but logout is being handled insufficiently. Standard end_session / logout urls are missing from these integrations. One can configure a logout url for their community with the help of support, but the platform only supports one logout url.In the future we want to have two SSOs in use in our community: one for end users and one for staff members. We have ran into a challenge while configuring this as the Gainsight community portal only supports one logout url.With separate logout urls we'll make sure the sessions are ended upon logout. Without separate logout urls the sessions are not ended correctly. This creates a risk for example for users using shared computers.
Our organization uses a Many-to-Many structure of Person-to-company. Meaning, a Person can be assigned to more than one company within Gainsight. This creates the problem of the BCC to Timeline feature not working very well. It basically logs every single email to drafts because the Person’s email address is associated with multiple companies. We would like the ability to select an option with the BCC to Timeline menu to only log BCC-to-timeline activities to the P360 and not have to deal with the Company object at all. Currently, a company is necessitated to have the timeline activity log correctly through BCC-to-timeline, but we would like a selectable option to bypass the company and have the activity log directly to the Person’s P360 that the email address is associated with. This would eliminate the need for our CSMs to go to drafts and attach a company to every email logged through BCC-to-timeline.
ScenariosCustomer churns User is banned Inactive user managementAs a CC Admin, I want Profile fields for specific inactive users to not be public (current state: all user profile pages are public if the community visibility is public) To maintain the user’s data in the community I do not want to erase this user I do want to keep all records of this user’s past activity Posts Visits and activity data Likes, Helpfulness votes, etc Profile fields and meta data (roles, etc) So thatInactive user’s public profile data isn’t available to be crawled, indexed etc Maybe the user was okay using their First and Last name as their username when active on the community, but now they’re inactive after churning n months ago and they don’t love that their community profile is still out there I don’t have to change/delete data that may still be useful or relevant to me Username Other profile meta data Badges and points Banned users don’t appear to still be part of my community
Hi Team, There has been a request to support transparent chart backgrounds in Success Snapshots so charts better align with and do not interfere with template themes. This enhancement would improve overall design flexibility and visual consistency. Thanks in advance for your consideration!
As a Gainsight Admin with a “fervor” for reporting and metrics, it would be nice to be able to edit a series of reports en mass as a maintenance and possibly deployment tool. . Primarily, I would like the ability to remove/add “Show me” fields and filters. Use Case: I have X number of reports that feature a field from Data Source Y. When that field is retired and/or replaced, I would like the ability to “swap” fields without having to touch every report is resides in. Anyone else have a case for this or support this capability? Has this been requested previously? (I can’t find anything on community) @darkknight @john_apple @travis_floyd @taylor_arrington @dan_ahrens
Hello!It’s not yet possible to export or import phrases in CC (see here for background), so I’m submitting this idea: Enable the export and import of phrases. There are several benefits of exporting and importing phrases = UI text:Efficient management: easy way to manage phrases → save time and effort in handling especially large volumes of text. Enhanced collaboration: translation/review/QA/editing of phrases by various experts outside the community (for example language professionals and marketing teams) → easier collaboration. Professional translation: use professional translation tools/translation memory tools and industry-standard formats → accuracy and consistency in localized versions. Consistent language: maintain consistency in language and terminology across a community → cohesive user experience for all users. Centralized repository: store all phrases in one file for easy access, without manual searching and editing of individual phrases → increased efficiency. Quick updates: make quick changes to specific concepts/technical terms/names through search and replace functionality → workflow efficiency.Thanks!
Currently, when a Timeline activity is updated via the API, the “Modified By” field is attributed to the user who last authorized the External Connection or updated the API key: Timeline UI This creates significant friction for our team and end users:Auditing & Compliance: It is currently impossible to distinguish between a manual intervention by an Admin and an automated system update. For auditing purposes, these should be distinct. User Confusion: When automated updates are stamped with a human name, it creates the illusion of manual intervention, causing confusion for end users and forcing the Ops team to waste time explaining system behavior.Context & Impact: In our specific use case, these Timeline activities contain highly sensitive information and we use an External Action to toggle a boolean to True once a dependent process completes.Despite this being a minor, binary background update, the system stamps a human name on the record. This makes a routine automated handshake look like a manual manual override of sensitive data, which is misleading and complicates our debugging and oversight processes. Requested Change: Please ensure system consistency by attributing these automated changes to "System Administrator" rather than the individual user who happens to hold the connection credentials. This would align the Timeline behavior with other automated system logs and provide the clarity required for sensitive data management.
When working across multiple Sandbox tenants, it’s difficult to visually identify which Sandbox I’m currently in because the Sandbox badge in the top-right looks the same for all environments.RequestPlease add an option to customize the Sandbox indicator (e.g., badge color and/or label) per Sandbox.Reduces mistakes (changes made in the wrong tenant).Improves admin efficiency and confidence during testing and validation.Provides a quick visual cue without needing to check URLs or tenant IDs.Nice-to-have detailsThank you for considering this enhancement.
Our team needs to make updates to their activity timeline entries to log information like the meeting location, products discussed, etc. With the Gong syncs taking 2+ hours, they are finding it difficult to make time to update their activities.A real-time (or every 15 minute) sync would really unlock the potential of this integration for us.
Use Case: I need to populate a field on the MDA User object when a user is assigned to one or more Sharing Groups.Example:User Named 'Jeremy Johnston' is a member of the Sharing Group 'XYZ Team'.I want to set MDA User object --> field name 'User Team Membership' value as 'XYZ Team' via Rule. I maintain this field value on MDA User to more easily share C360 views, reports and dashboards across multiple users.Note: I'm interested specifically in 'Sharing Groups', not 'User Groups'. I am aware there is a MDA object for 'User Groups' and I’d like to see the same option be made available for 'Sharing Groups'.
Thanks for the new Course Families feature! This is really helpful. I’m finding it a bit prohibitive that the descriptor is required when adding courses to a family and that each course requires a unique descriptor.For example, we use those separator hack courses on catalog pages and I wanted to group all them together into a Course Family called “Skilljar Hack Separator Courses” and that would be sufficient enough (no descriptor necessary). Since it was required, I tried entering the same descriptor (e.g., “Separators for Catalog Pages” for all of them) but couldn’t save it until I made them each unique. Another example would be a group of courses on a certain product (in a Uni that offers training on multiple products) and I wanted to create a family of Product A courses, Product B courses, etc. Also didn’t feel like each course required descriptors, so copied the names into each to make them unique so it’s just duplicative info displaying.Perhaps I’m missing the importance of unique descriptors for each, but wondering if others might find these requirements a bit restricting as well. Any reason they can’t be set to optional and the unique descriptor criteria lifted?
It would be very beneficial to have Gainsight Assist Analytics/Reports available to track the following information:The number of times each template has been used Who used the templates When the templates were used Who the templates were sent toWe have created numerous effective emails, but we lack insight into their use without reviewing individual timelines to confirm whether someone was contacted. Having access to these reports would also help those using the templates by reducing duplicate email sends. While CSMs can check the timelines, having a report would significantly streamline their efforts.
ProblemGainsight CS displays execution history and related time-sensitive data using inconsistent time zones across different features, leading to confusion, wasted time, and the need for manual time zone conversions. Lack of time zone parity across features creates an unnecessary cognitive load for users trying to understand the status and timing of critical processes and workflows.When investigating why a specific user was missing on my end, I checked the execution time of the relevant Job (Salesforce connector). The Job's history showed the last run was yesterday at 7:00 AM. Knowing it’s a daily run, I expected it to have already executed today as it was 8:45 Upon checking the Job's configuration, I realized the execution time was set to 7:00 AM PDT (the application's time zone), which corresponds to 4:00 PM in my local time. This caused me to mistakenly believe the execution was missing and required me to manually trigger the job; all because the displayed time was not in my local context. Connectors → Activities UIThe root cause of this confusion is that I spend most of my time in the Rules Engine, where the execution history is displayed in my local time zone. When I switch to Connectors 2.0, the time zone shifts to the application's default. This broken experience forces users to perform "mental gymnastics" and consult external converters just to confirm the expected run time. Proposed Solution I request a feature to allow users to select the time zone for displayed data within each feature that shows execution history or timing (e.g., Jobs, Rules List, Rule Chain, etc.).Ideally, this would function similarly to the Rules Engine → Activity view, but be integrated directly into the feature's interface, not as a separate activity section. Rules Engine → Activity allows users to select the time zone for displaying dataExample Implementation:Introduce a prominent UI element (like a toggle or dropdown) that allows the user to switch the display of time-stamped data between: Application Time Zone (e.g., PDT) User's Local Time Zone (The time zone of the user browsing the app) Mockup: Allow the user to select the display time zone, dynamically adjusting all dates and times shown in the UIStandardizing the display across all features will prevent user error, reduce support inquiries, and greatly improve the overall user experience.#adminQoL
Hi!It seems like setting the recurring settings on a CTA is only possible when creating it manually but not:Via rules in the Create CTA action Via success plans when adding CTAs to a success plan templateIt would be more effective than building a rule to recreate a CTA every X to meet that need. Furthermore, it should be possible to edit an existing CTA to make it recurring when the CTA type has the recurring toggle on. ThanksA.
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.