Skip to main content
Solved

What permissions does LaunchDarkly Cohort sync really need?


The instructions for setting up syncing of Amplitude cohorts to LaunchDarkly suggest creating an access token with Writer permissions, which has write access to pretty much everything except account members and billing. That seems like much more than is needed to do what the sync needs, as AFAICT it just creates and updates Segments in LD.

 

Does anyone know what access is actually required, to what objects, in order for the sync to work? I’m considering creating a custom role that only has write permissions to Segments, for instance.

Best answer by Ben Kloester

I was able to find the answer in LaunchDarkly’s docs here.

The access token must have the actions createSegment and updateIncluded on segment resources (eg "proj/*:env/*:segment/*") to sync segments from Amplitude.

View original
Did this topic help you find an answer to your question?

3 replies

Esther Trapadoux
Community Manager
Forum|alt.badge.img+9

@Ben Kloester welcome to the community! I’m pulling in someone from our support team to help dive into more detail on this! You should receive a message from them soon.


  • Author
  • New Member
  • 1 reply
  • Answer
  • May 29, 2023

I was able to find the answer in LaunchDarkly’s docs here.

The access token must have the actions createSegment and updateIncluded on segment resources (eg "proj/*:env/*:segment/*") to sync segments from Amplitude.


Esther Trapadoux
Community Manager
Forum|alt.badge.img+9

@Ben Kloester really appreciate it. Looks like @Thao Nguyen also alerted our eng team to update documentation on our side. 🙏


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