Feature Idea - Lockable Segments

tdeahl

We're starting to rollout 6Sense at our org and as we're creating our TAM and ICP segments, one concern that came up is with so many users able to pop into the platform and build segments that someone will overwrite our Foundational segments - sending everything into chaos.

Anyone have creative ideas for solving this?

Lauren Skinner-Johnson, 6sense

Sure do love this idea!! These are not creative solutions but strict naming conventions, leveraging folders (and folder naming conventions) and over communicating all of that strategy to anyone with access to the platform. Also, you could leverage user role assignment.

Jana_Marketing_Maven

Instead of being able to lock segments, what about folder access management? that way 'locked' segments could be hidden away from those who do not need them?

tdeahl

@Jana_Marketing_Maven yes love that even more!

Hunter_Kincannon

Love this idea, @tdeahl! I submitted this as a feature request not too long ago. Also, any sort of change logs would be helpful to identify what was altered.

Rachel Zerilla

@tdeahl if you also create a feature request, the more we receive the higher priority it is :) This is a good one!

Deanna Graves

I'd love to raise my hand on this feature. This is a really crucial one especially with users who have custom 6qa's with segments that shouldnt be allowed to be unlocked.

Hunter_Kincannon

@Deanna Graves Submit a feature request!

Deanna Graves

@Hunter_Kincannon Thanks Hunter. I suppose that would be more helpful than merely yelling "Feature request" into the void of this post. I just submitted the case via Support. Wishing us all luck :)

Hunter_Kincannon

@Deanna Graves had to lol at that 😂