Merge pull request #107 from AdobeDocs/floodgate

Floodgate

Author: Alicesnk

help/experience-rollouts/TOC.md

@@ -21,15 +21,8 @@ user-guide-description: Learn how to use Adobe Experience Rollouts to manage fea
 + Guides {#guides}
   + Getting started with the console {#console}
     + [Log in to the Experience Rollouts console](guides/console/log-in-to-the-console.md)
-    + [Environments overview](guides/console/environments-overview.md)
+    + [Select your sandbox](guides/console/environments-overview.md)
     + [Request access](guides/console/request-access.md)
-    + [Teams and their admins](guides/console/teams-and-admins.md)
-    + [Create a new team](guides/console/create-a-new-team.md)
-  + Teams {#teams}
-    + [Manage teams](guides/teams/manage-teams.md)
-    + [User roles](guides/teams/user-roles.md)
-    + [Add members to your team](guides/teams/add-team-members.md)
-    + [Team management FAQ](guides/teams/team-management-faq.md)
   + Applications {#applications}
     + [Manage applications](guides/applications/manage-applications.md)
     + [Onboard your application](guides/applications/onboard-your-application.md)
@@ -43,19 +36,13 @@ user-guide-description: Learn how to use Adobe Experience Rollouts to manage fea
     + [SDKs](guides/integrate/sdks.md)
     + [Integration steps](guides/integrate/integration-steps.md)
     + [Subscribe to the API application in Adobe Developer Console](guides/integrate/subscribe-to-api-application.md)
-  + Feature flags and releases {#feature-flags-releases}
-    + [Features, feature groups, and releases](guides/feature-flags/features-feature-groups-releases.md)
+  + Feature flags {#feature-flags}
+    + [Features and feature groups](guides/feature-flags/features-feature-groups-releases.md)
     + [Create your first feature flag](guides/feature-flags/create-your-first-feature-flag.md)
     + [Set a feature to gradually roll out](guides/feature-flags/set-feature-gradual-rollout.md)
     + [Create a feature group](guides/feature-flags/create-a-feature-group.md)
     + [Set a feature group to gradually roll out](guides/feature-flags/set-feature-group-gradual-rollout.md)
     + [A/B testing with feature flags](guides/feature-flags/a-b-testing.md)
-    + [Releases and cross-team feature groups](guides/feature-flags/releases-and-cross-team-feature-groups.md)
-    + [Release workflow end-to-end](guides/feature-flags/release-workflow-end-to-end.md)
-    + [Request a release](guides/feature-flags/request-a-release.md)
-    + [Update release audience rules](guides/feature-flags/update-release-audience-rules.md)
-    + [Release states](guides/feature-flags/release-states.md)
-    + [Create a cross-team feature group](guides/feature-flags/create-cross-team-feature-group.md)
     + [Release management FAQs](guides/feature-flags/release-management-faqs.md)
     + [Analytics](guides/feature-flags/analytics.md)
     + [Schedule](guides/feature-flags/schedule.md)

help/experience-rollouts/guides/applications/manage-applications.md

@@ -22,10 +22,8 @@ Each application is owned by exactly one team. Only members of that team can man
 This ownership model also affects how you structure feature groups:
 
 * **Within your team** — A Product Release Owner can group feature flags across applications owned by the same team. See [Feature groups to control multiple features](../../concepts/feature-groups-to-control-multiple-features.md).
-* **Across teams** — If you need to group feature flags from applications owned by different teams, use a cross-team feature group, which requires the **Feature Admin** role.
 
 ## See also {#see-also}
 
 * [Onboard your application](onboard-your-application.md)
 * [Feature groups to control multiple features](../../concepts/feature-groups-to-control-multiple-features.md)
-* [User roles](../teams/user-roles.md)

help/experience-rollouts/guides/applications/onboard-your-application.md

@@ -5,7 +5,7 @@ exl-id: d88c27a5-f490-4504-9764-5e4ce98fdf20
 ---
 # Onboard your application {#onboard-your-application}
 
-You must have the **Admin** role to add a new application. See [User roles](../teams/user-roles.md) if you need to verify your role or request it from your team admin.
+You must have the **Admin** role to add a new application. Contact your team admin if you need to verify or update your role.
 
 ## Add a new application {#add-application}
 
@@ -39,5 +39,4 @@ Once your application is onboarded, your team can start creating feature flags:
 ## See also {#see-also}
 
 * [Manage applications](manage-applications.md)
-* [User roles](../teams/user-roles.md)
 * [Log in to the console](../console/log-in-to-the-console.md)

help/experience-rollouts/guides/audience/complex-rules.md

@@ -30,4 +30,3 @@ This is the same mechanism used for percentage rules in combination with other c
 
 * [Audience in feature flags and feature groups](audience-in-feature-flags-and-feature-groups.md)
 * [Add percentage rules in audience criteria](adding-percentage-rules.md)
-* [Update release audience rules](../feature-flags/update-release-audience-rules.md)

help/experience-rollouts/guides/audience/using-enterprise-org-data.md

@@ -35,5 +35,4 @@ DMA orgs use org IDs in the format `XXXXXXXXXXXXXXXXXXXXXXXX@ADOBEORG`. When ent
 ## See also {#see-also}
 
 * [Audience in feature flags and feature groups](audience-in-feature-flags-and-feature-groups.md)
-* [Update release audience rules](../feature-flags/update-release-audience-rules.md)
 * [Complex audience rules](complex-rules.md)

help/experience-rollouts/guides/console/create-a-new-team.md

@@ -1,37 +1,17 @@
 ---
-title: Environments overview
-description: Learn about the Stage and Production environments in Adobe Experience Rollouts and when to use each.
-exl-id: 84b6b640-7f43-4e51-a3b1-29f4efd3670f
+title: Select your sandbox
+description: Learn how to select the correct Adobe Experience Platform sandbox when working in Adobe Experience Rollouts.
 ---
-# Environments overview {#environments}
 
-Experience Rollouts provides separate environments so you can validate your feature flags before promoting changes to your live users.
+# Select your sandbox {#sandbox}
 
-## Available environments {#available-environments}
+Experience Rollouts is built on Adobe Experience Platform. Before working with feature flags, select the sandbox that corresponds to your current environment, just as you would in any other Adobe Experience Platform application.
 
-| Environment | Purpose |
-|---|---|
-| **Stage** | Testing and validation. Use this environment to configure and test feature flags before enabling them in Production. |
-| **Production** | Live rollouts. Feature flags configured here are evaluated against your real user base. |
+## How to select a sandbox {#how-to}
 
->[!IMPORTANT]
->
->Changes made in Stage do not automatically carry over to Production. Feature flags and audience rules must be configured separately in each environment.
-
-## Selecting an environment {#selecting}
-
-After logging in to the Experience Rollouts console, select the environment from the environment switcher at the top of the interface. Make sure you are working in the correct environment before creating or modifying feature flags.
-
-## Best practices {#best-practices}
-
-Follow these recommendations to avoid configuration errors and protect your production audience:
-
-* Always create and test feature flags in **Stage** first.
-* Validate audience rules, percentage rollouts, and targeting logic in Stage before replicating in Production.
-* Use the [cross-environment workflow](../cross-environment/cross-environment-concept.md) to view and manage flag status across environments.
+Use the sandbox switcher in the top navigation bar of the Experience Rollouts console to select the correct sandbox before creating or modifying feature flags.
 
 ## See also {#see-also}
 
 * [Log in to the console](log-in-to-the-console.md)
-* [Associate environments to an application](../cross-environment/associate-environments.md)
-* [View feature flags across environments](../cross-environment/view-feature-flags-across-environments.md)
+* [Request access](request-access.md)

help/experience-rollouts/guides/console/environments-overview.md

@@ -11,7 +11,7 @@ Getting started with Experience Rollouts involves three steps: finding or creati
 
 Experience Rollouts is organized around **teams**. Each team owns one or more applications and manages feature flags for those applications. Before you can log in, you need to belong to a team.
 
-Check with your product or engineering lead to find out whether a team already exists for your project. If it does, ask the team admin to add you with the correct [user role](../teams/user-roles.md). If no team exists yet, follow the steps in [Create a new team](create-a-new-team.md).
+Check with your product or engineering lead to find out whether a team already exists for your project. If it does, ask the team admin to add you with the correct user role. If no team exists yet, contact your organization's Experience Rollouts admin.
 
 ## Request access {#request-access}
 
@@ -25,7 +25,7 @@ After access is granted:
 
 1. Go to [https://experience.adobe.com/](https://experience.adobe.com/) and sign in with your organization credentials.
 2. Select **Experience Rollouts** from the application switcher.
-3. Select the appropriate environment — **Stage** for testing, **Production** for live rollouts. See [Environments overview](environments-overview.md) for details.
+3. Select the correct sandbox. See [Select your sandbox](environments-overview.md) for details.
 
 ## First steps after logging in {#first-steps}
 
@@ -37,4 +37,4 @@ After logging in, verify that your application is listed in the console. Applica
 |---|---|
 | **Team** | A self-managed group that owns applications and manages feature flags. Teams have a flat structure with different user roles and permission levels. |
 | **Application** | The application you want to control with feature flags. Each application is owned by a team. |
-| **Feature flag / Feature group / Release** | The artifacts created in Experience Rollouts for feature testing and release management. |
+| **Feature flag / Feature group** | The artifacts created in Experience Rollouts for feature testing and controlled rollouts. |

help/experience-rollouts/guides/console/log-in-to-the-console.md

@@ -11,7 +11,7 @@ Access to Experience Rollouts is managed at the team level. To use the console,
 
 Before requesting access, confirm the following:
 
-* You know which team to join. Check with your product or engineering lead, or refer to [Teams and their admins](teams-and-admins.md) to identify your team and its admin.
+* You know which team to join. Check with your product or engineering lead to identify your team and its admin.
 * You know which environment you need access to — **Stage**, **Production**, or both.
 
 ## Request access {#request-steps}
@@ -29,12 +29,12 @@ You will receive a confirmation once the request is submitted. You can monitor t
 
 ## Available roles {#roles}
 
-The role assigned to you determines what actions you can perform in the console. See [User roles](../teams/user-roles.md) for a full description of each role and its permissions.
+The role assigned to you determines what actions you can perform in the console. Contact your team admin if you are unsure which role to request.
 
 ## After access is granted {#after-access}
 
 Once your request is approved, log in to the Experience Rollouts console and verify that your team and applications are visible. See [Log in to the console](log-in-to-the-console.md) for next steps.
 
 ## Need help? {#need-help}
 
-If you are unsure which team to join, or if no team exists for your project yet, see [Create a new team](create-a-new-team.md) or contact your organization's Experience Rollouts admin.
+If you are unsure which team to join, or if no team exists for your project yet, contact your organization's Experience Rollouts admin.