What prompted the decision not to provide Early Access to Release Notes document? This seems to move in the opposite direction of what Gainsight recently committed to with regard to better communication regarding updates and releases.

Can someone explain the S3 enhancements?

• How will S3 key access be restricted? You need to be a superadmin to access that part of the platform anyways, so what is the concern? How will this be implemented?
• Who will get the alerts? What format will they be? Can we configure who gets them?

@bradley , pls find the explanation below

1. Today, if a non-super admin has access to connector’s page through permission bundle, then they can access S3 keys, and so for such users, going forward, we don’t show the keys (show icon and rotation icon will be disabled). For super admins there is no impact.
   Also gainsight support team used to have access to S3 keys (when granted access to gainsight support is used) going forward, even support teams will not access these S3 Keys. 
2. Its a system generated email alert that will be sent to super admins, it will be triggered only when S3 key isn’t rotated/updated in the past 6 months. There is no configuration for this alerts

Many companies, including ours, have multiple super admins, some of which are in leadership and not active admins. Not every super admin needs an email - this ends up with admins getting forwarded emails from non-admin super users either panicked about the language in the email, making sure we do it, sending the email as an FYI, or some combination of the above.

As a self proclaimed customer centric company, I sincerely hope Gainsight considers these potential issues both in the language of the messaging, and in consideration of who should get the emails.

Thks @bradley for sharing your comments

As mentioned, the email will be triggered only if the keys are not rotated regularly, and language in the email will be of a friendly reminder. We are also going to display in connector’s UI on when keys are last rotated/updated, so that admins can proactively rotate the keys. In the current release, we don’t have the customisation to choose specific email ids, and can be considered in future. Thanks 

Thanks for bringing this up Jeff. Given the Q3 release will be relatively small with minimal impact to end users, we've opted to share this advanced detail within our community as opposed to our typical early access release notes. We intend to share Early Access Release Notes for Q4 and future releases. Phrased differently, this sneak peek serves as the early access notes, but please let me know if there are additional details that we can provide to assist you in planning for this release.

Are you only going to restrict S3 key access or other similarly sensitive keys like the Gainsight API Access Key which is accessible in plain text via the Connectors 2.0 configuration page?

How exactly is Create Person/Company Person from CE & CC via Unification going to work — particularly regarding updates from CC affecting Person and Company Person data in CS? Unification and Enrichment from CC into CS is already not fit for purpose (only supports a single Company Person record per CC User) and is undocumented so we need more details on this please

I would really like more information about the Calendar Context Resolution Update.  How will this ensure that the correct company and contact are automatically assigned when creating activities, and create consistency across calendar and other meeting integration solutions?  We have a Company record where all employees have a company person record.  This is used for case creation and other function in SF.  What we find is that the calendar defaults to that company most of the time.  When the user changes the company in the activity, all the external attendees are wiped out.  This is super frustrating.  Our RMs have a score card that is driven by the persona of the contacts they engage with.  When all those contacts are wiped out it defeats the purpose of using the calendar integration because adding them back in manually is the equivalent of creating manual activity.  Will this upgrade resolve that kind of issue? This issue is a major pain point and efficiency drag for my team.  

Hey @ChiragJ Could you please help with the above Timeline query? 

Looping in @rakesh and @Kartheek  for insights. 

@jake_ellis I get it, though this linear community format doesn’t seem the best approach as questions are already getting posted across each other in the comments thread vs. directed tied to the specific item in question (like you can do with Google comments).  Makes it harder to find and align question/answers.

Basically what our enhancement does is - provide an easy way to bring people into person model of CS from CE / CC. We can target great journeys only for the contacts in Person in JO effectively. Creating persons from Gainsight CC, CE, and PX with minimal setup is what we are aiming here.

1. CE/CC: Requires no additional setup, just a simple toggle to enable auto-creation. (Default is off)
2. PX: Works seamlessly if the email address is used as the identifier for customer products.

This isnt going to solve the one person multiple companies use case we discussed @jparker. Else I would have definitely brought it up. We are still white boarding that problem. 

For this release it’s only S3 Keys that are masked for non super admins

Thanks for sending this in @rho_ran_experian , we were solving for partner use cases primarily where one email is associated with multiple companies but we did realise we were not able to address all problems. So we had decided to hold back sending any changes this release. 
Can I request you to explain your use case in detail and how often do you see the need to change the company while trying to log it via calendar?

General Comment: It may be worth updating the Release Notes calendar to indicate the quarter each release is associated with. I would have expected that the quarter matched to the calendar month. i.e.

Q1: February

Q2: April

Q3: July

Q4: October

However, it appears that the release calendar aligns with Gainsight’s fiscal year

Q1: April

Q2: July

Q3: October

Q4: January

Adding a column to the table would be helpful for quick validation

Hi @Veronica.Moore That’s a very fair ask, and thank you for highlighting it. We will update the release process docs to make this clearer. 

FYI @shayerisen