Contents

Custom roles

Scope Launch actions to a project and environment with custom member roles.

How it works

  • Permissions cover flag create, edit and archive, targeting, kill, approvals, segments and project administration.
  • Each permission can name a project key and environment key, or * for either scope.
  • Owners and admins are never restricted. An editor without a binding keeps existing behavior.
  • A bound editor or viewer gets exactly the bound permissions, which can restrict an editor or lift a viewer.
  • Every Launch write route checks the same guard, including kill, approvals, triggers, rollouts, pipelines and scheduled changes.

Read the Launch overview or the SDK guides.

We use only essential cookies to keep you signed in and the app working. With your consent we may enable optional analytics to help us improve e-volv. See our Privacy Policy and Terms.