Skip to main content
Open

Engagement audit trail in PX

Related products:PX Engagements
john_apple
jordan_cook
jean.nairon
jake_ellis
matthew_lind
+58
  • john_apple
    john_apple
  • jordan_cook
    jordan_cook
  • jean.nairon
    jean.nairon
  • jake_ellis
    jake_ellis
  • matthew_lind
    matthew_lind
  • heather_hansen
    heather_hansen
  • spencer_engel
    spencer_engel
  • ablnsj
    ablnsj
  • lori_dinardo
    lori_dinardo
  • sainyam_sandhu
  • liam_nicholls
    liam_nicholls
  • curtis_6604aa
    curtis_6604aa
  • gunjanm
    gunjanm
  • andreammelde
    andreammelde
  • Jef Vanlaer
    Jef Vanlaer
  • tammy_c
  • Kate
  • bradley
    bradley
  • kendall.roberson
  • nicole.stanford
  • coryedwards
  • Jamie10smith
  • mumali
  • twildeck
  • sarahmiracle
    sarahmiracle
  • romihache
    romihache
  • carolyndibuono
    carolyndibuono
  • rho_ran_experian
    rho_ran_experian
  • kelly.nissl
  • alizee
    alizee
  • Molly.McQ
    Molly.McQ
  • jrich
    jrich
  • yaslongoria
    yaslongoria
  • Jack_Darley
  • chiggitt
  • bnopel
  • sean.berg
  • JessicaV
  • simonechen
    simonechen
  • stevepost
    stevepost
  • Veronica.Moore
  • tmillican
  • joshua.greenberg
    joshua.greenberg
  • bfoleyHS
    bfoleyHS
  • ajprince
    ajprince
  • joshrg
  • birkelzack
  • joshmanuel
  • tkapshey
  • catarinacardoso
  • JRey
    JRey
  • Becki
    Becki
  • JillBriggs
  • alliheller
  • elyna.k
  • andyh
  • anitat
    anitat
  • CristianaF
    CristianaF
  • Rebecca Finney
  • Catyguerrant
  • DStreet
  • CatherineP
  • Pascal Van Huffel
    Pascal Van Huffel

VBennyGainsight

My organization has a lot of people collaborating on building engagements. As our product is also new, there are often changes to the audience and scheduling based on new criteria or occasionally changes in custom user attributes our product is storing.

We would like there to be an audit trail on how engagements change over time. Ideally, this would contain who/what/when information on changes to the following areas, from highest priority to lowest priority:

  1. Launch status
  2. Audience
  3. Schedule
  4. Engagement content
  5. Engagement name and description
  6. Templates (can be captured by content)

This would help people understand who has been working on what engagements and why, and how they’ve evolved over time.

In many ways, this would be a similar effort to the Field Level Audit Trail from Gainsight that was built for CS - I’m not sure if we’d need the full field level audit trail, but close.

 

  • Contributor ⭐️
  • May 12, 2023

We are an ISO27001 certified organization where security is a top priority. Preferably every change that affects what our end users see should have who/what/when/why, why being our internal ticket number (a free text comment field could be used for that) and the data should be available through an API so that it could be fetched and fed into our SIEM.


susan_parker
Forum|alt.badge.img+1
  • Contributor ⭐️⭐️⭐️
  • April 1, 2025

To build on Benny’s request, we have products that must conform to SOC2 audit requirements.  We also have corporate requirements to follow acceptable software development lifecycle procedures (SDLC?).

When we publish any code to our Production environment (this includes engagements and the KC Bot), we must have a code review by engineering and restrict the publication process to a small OPS team.  Because Gainsight PX does not have an internal audit trail for publication, we have to use a complicated workflow in Jira to build an acceptable audit trail.  This can add days to the publication of an engagement.

Please add a review/approval process for publication to the production environment.  It needs to include date/time stamps with person taking action, and have the approvers controlled by role.  A good model to follow is Split (who is a Gainsight customer) for feature flag control.



Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings