Timeline Pinning should NOT require Timeline Editing Permissions

This is a bit swing and a miss that could have been spotted a mile away, and was likely implemented because it was easier to do, without much consideration on the usability impact it would have. If adoption of pinned Timeline activities seems low, consider this exhibit A.

Yeah, I can’t roll this out like this.  I like the feature, but not worth it if we have to give edit permissions to users to use it.

+1 to this! Coupling Pin Activity directly to Edit Activity permissions creates a major security and data integrity risk.

Requiring full edit access just to pin an item forces admins into an impossible "all-or-nothing" trade-off: expose historical data to accidental edits across all timelines, or abandon the pin feature entirely  (I bet most if not all of us are in the second group!).

Separating these permissions, as Amanda suggested, is essential for actual adoption.
 

cc ​@Molly.McQ ​@vineshgvk 

100%; opening Timeline edit functionality to our general user base would be a nightmare. We definitely won’t be enabling this feature until Gainsight provides a separate permission set for this.

Our users can’t even pin the Timeline entries they created. 

Agreed this needs it’s own permission set, but also there’s defo a bug where users cannot even pin their own entries as according to documentation that should be possible. 

Thank you for creating this thread!  We will not be using Pinning until this is changed and the ability to unpin any activity is available to all.

Agreed, this is a real blocker. Tying pinning to full Timeline Edit Activity permissions means we'd have to hand out broad edit access just to let people flag important entries. That's not a permission tradeoff we can make for our users.

The comparison to Cloning makes sense to me. If pinning is meant to be a lightweight, low-risk action (which it should be), it shouldn't require the same permission level as editing or deleting timeline entries. Either tie it to the General Settings toggle like Cloning, or split it into its own dedicated permission. Either approach beats forcing admins to discover this dependency through trial and error.

Please reconsider the permission model here. This is currently unworkable for orgs that need to control edit access closely.

Just chipping in my support for this idea. Pinning an activity should not require “edit all” permissions. We cannot roll this out to our users in the current state. And like others have pointed out, even though users can edit their own activities, they cannot pin them.

Echoing the sentiments of everyone else in this thread. How in the world could this have been missed?

It is beyond tiresome that Gainsight continues to demonstrate an inability to think about the practical implications of the features they build and the decisions they make.