This section refers to a deprecated version of the product. The new version is FE&R. To access FE&R, contact your CSM.
πŸ“˜ To learn more, read the FE&R documentation.
LogoLogo
PlatformsPricingRessources
  • User documentation
  • Onboarding
  • Help Center
  • Release Notes
  • Flagship - Deprecated
  • Feature Experimentation & Rollout (ex-Flagship) is evolving!
  • GETTING STARTED
    • πŸ‘‰Managing multiple environments
    • Using the trial version of Flagship
  • First steps with Flagship
    • Quick start guide
    • Glossary
  • Implementation
    • Sending transactions from the AB Tasty Shopify app directly to Feature Experimentation & Rollouts
  • Integrations
    • Heap Analytics integration (Push)
    • Tealium AudienceStream (receive audiences)
    • FullStory integration (segment exports)
    • Heap Analytics integration (Pull)
    • Google Analytics integration (pull audiences)
    • Segment Integration (receive traits)
    • Mixpanel integration (cohort exports)
    • πŸ‘‰Retrieving your third-party tools’ audiences in AB Tasty - Feature Experimentation & Rollouts
    • Zapier integration
    • Segment integration
  • Steps configuration
    • πŸ‘‰Configuring Sequential Testing Alerts
    • πŸ‘‰Configuring your Flags
    • πŸ‘‰Using the scheduler
    • πŸ› οΈ[Troubleshooting] How to target a large number of users at the same time?
    • πŸ‘‰Configuring KPIs
    • πŸ‘‰Using the automatic rollback option
    • πŸ‘‰Targeting configuration
    • πŸ‘‰Dynamic allocation
    • πŸ‘‰Traffic allocation
  • Team
    • Access Rights, Teams & User Management
    • πŸ‘‰Defining rights per project
  • DEMO
    • AB Tasty - Feature Experimentation & Rollouts Demo - How to use it
  • Navigating the interface
    • πŸ‘‰Archiving use cases from the dashboard
    • πŸ‘‰Flags page
    • πŸ‘‰Running a search on the dashboard
    • Navigating the Flagship interface
  • REPORTING
    • πŸ‘‰Verifying your hit setup
    • πŸ‘‰Exporting reporting data
    • Understanding the "Chances to win" indicator
    • πŸ› οΈ[Troubleshooting] How can I know my test is reliable and my data significant enough to be analyzed?
    • Reporting - A/B Test
    • πŸ‘‰Using the reporting filters
  • API keys & Settings
    • πŸ‘‰Acting on your account remotely
    • πŸ‘‰Using Experience Continuity
    • visitor experiment option
  • FEATURES SETUP
    • πŸ‘‰Bucket allocation
  • SDKs integration
    • πŸ‘‰Managing visitor consent
    • πŸ‘‰Understanding the use of SDKs
  • FAQ
    • Can I make a comparison for each reporting?
    • Can I use Flagship even if my SDK stack is not available?
  • Platform integration
    • πŸ‘‰Webhooks page
  • Decision API
    • Decision API for non-techie users
  • Account & Profile
    • πŸ‘‰Configuring account restrictions with MFA
    • πŸ‘‰Configuring a FA on your profile
  • RELEASE NOTES
    • October - Flagship becomes Feature Experimentation & Rollouts
    • February - Release Notes
    • πŸ“…January - Release Notes
    • πŸŽ‰December - Release Notes πŸŽ‰
    • πŸ¦ƒNovember - Release Notes
    • September Release Notes 🎨
    • June Release Notes 🐞
    • 🍸May Release Notes β˜€οΈ
    • Flagship Release Notes April πŸ‡
    • Flagship February release notes πŸ‚
    • Flagship January release notes πŸŽ‰
    • Flagship November release notes πŸ¦ƒ
    • Flagship October Release Notes πŸŽƒ
    • Flagship September Release note πŸŽ’
    • Flagship August Release Notes 🐬
    • Flagship Release Notes July β˜€οΈ
    • Flagship Release notes June 🌻
    • Flagship Spring Release May 🌸
    • Flagship Release Notes: Fall
  • Use cases
    • πŸ‘‰Duplicating a winning variation
    • πŸ‘‰Configuring a Feature Toggle/Flag
    • πŸ‘‰Configuring an A/B Test
    • πŸ‘‰Configuring a Progressive rollout
    • πŸ‘‰Configuring a Personalization
  • VIDEO TUTORIALS
    • [Video Tutorial] AB Test
    • [Video Tutorial] Feature Flag
    • [Video Tutorial] Progressive Deployment
Powered by GitBook
LogoLogo

AB Tasty Website

  • Home page AB Tasty
  • Blog
  • Sample size calculator
  • Release note

AB Tasty Plateform

  • Login

Β© Copyright 2025 AB Tasty, Inc, All rights reserved

On this page
  • πŸ“– Definition
  • βš™οΈ Configuration
  • Creating environments
  • Managing existing environments
  • πŸ’‘ Use case

Was this helpful?

Edit on GitLab
Export as PDF
  1. GETTING STARTED

Managing multiple environments

πŸ“– Definition

Environments are organizational units which allow you to manage your use cases throughout the entire development lifecycle, from local development to production, in order to minimize bugs, facilitate QA and accelerate your team development capacity. By default, you only have access to the PROD and PREPROD environments, but Flagship enables you to create new environments and to manage and personalize the existing ones directly from the platform.

βš™οΈ Configuration

Creating environments

Adding multiple environments on your Flagship account can be helpful as it enables you to have the same environment configuration as your engineering team and to reproduce the same workflow. To create a new environment, you must have a Super Admin role.

⭐ Good to know

  1. Once an environment is created, all projects (use cases not included) and persona keys from your PROD environment are duplicated to your new environment. From the dropdown menu displaying all your current available environments, click Create an environment: A pop-up appears.

  2. Fill in the name of your new environment.

  3. Click CREATE: You are redirected to your new environment.

The same quota as the PREPROD default environment is applied. To be able to use your new environment, you must enter its specific Environment ID and API key in your codebase.

⭐ Good to know

The new environment can be accessed by its creator only. To add other members, go to Settings > Teams and enter the email address and role of the desired member(s).

Managing existing environments

You can also manage your existing environments.

From the dropdown menu displaying all your current available environments, you can:

  • Edit an environment’s name by clicking the edit icon.

  • Delete an environment by clicking the delete icon (except PREPROD).

These actions do not apply to the PROD default environment.

🚩 Heads up

Once an environment is deleted, it cannot be retrieved.

πŸ’‘ Use case

Let’s say you have a development lifecycle made of three different environments: Staging, Pre-production and Production. To make it easier for you and your team, you want to reproduce the same workflow on Flagship and want to add the staging environment, as the Pre-production and Production ones already exist by default on your account. To do so:

  1. From the dropdown menu displaying all your current available environments, click Create an environment.

  2. Enter the name of your new environment.

  3. Click CREATE.

  4. Go to Settings > Team.

  5. Add the email and role of your team members.

You can now duplicate your existing use cases from the Production and Pre-production environments to the Staging one, or create new use cases from scratch.

Need additional information?

Submit your request at product.feedback@abtasty.com

Always happy to help!

PreviousFeature Experimentation & Rollout (ex-Flagship) is evolving!NextUsing the trial version of Flagship

Last updated 2 days ago

Was this helpful?

The multi-environment feature is available for the only. To benefit from it, please contact your dedicated CSM or KAM.

πŸ‘‰
[plan name] plan