2 results found

1. Audience Visibility Control

   Role: Technology Specialist - Product Architect

   What we you trying to solve:

   We manage a multi-OpCo organization using a single Optimizely instance with isolated production environments per market/region. I've submitted a separate feature request for environment visibility control to address UI clutter and prevent users from seeing irrelevant environments.

   Following that solution, audiences/segments also need OpCo-scoping. Currently, audiences remain globally shared across all users, creating problems in multi-OpCo setups:

   1. Cross-OpCo interference - OpCo A can accidentally modify or delete audiences used by OpCo B
   2. UI pollution - users see irrelevant audiences from all markets when configuring targeting
   3. Risk of mis-targeting - OpCo representatives might accidentally select the wrong audience (e.g., "premiumusersgermany" instead of "premiumusersnetherlands")
   4. No access control - cannot restrict who can modify specific audiences
   5. Namespace confusion - as OpCo count grows, finding the correct audience becomes increasingly difficult

   For example, when a Netherlands OpCo representative configures feature targeting, they must navigate through audiences for Germany, Myanmar, and other markets, increasing cognitive load and error risk.

   Outcome we're trying to achieve:

   Enable audience/segment visibility scoping so users only see and can interact with audiences relevant to their role. Ideally through environment-scoped audiences where:

   • Audiences created in production_netherlands are only visible when working in that environment
   • Netherlands OpCo representatives cannot view, modify, or accidentally select audiences from other OpCos
   • Audience isolation follows the same pattern as environment visibility control
   • No additional permission management overhead required

   This would:
   - Prevent cross-OpCo audience interference
   - Reduce cognitive load when configuring feature targeting
   - Eliminate risk of mis-targeting features to wrong markets
   - Provide natural isolation aligned with environment access patterns
   - Complete the multi-OpCo isolation story started with environment visibility control

   Role: Technology Specialist - Product Architect

   What we you trying to solve:

   We manage a multi-OpCo organization using a single Optimizely instance with isolated production environments per market/region. I've submitted a separate feature request for environment visibility control to address UI clutter and prevent users from seeing irrelevant environments.

   Following that solution, audiences/segments also need OpCo-scoping. Currently, audiences remain globally shared across all users, creating problems in multi-OpCo setups:

   1. Cross-OpCo interference - OpCo A can accidentally modify or delete audiences used by OpCo B
   2. UI pollution - users see irrelevant audiences from all markets when configuring targeting
   3. Risk of mis-targeting… more
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  0 comments  ·  UX  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Environment-Based Visibility Control for Multi-OpCo Organizations

   Role: Technology Specialist - Product Architect

   What are we trying to solve:

   Currently, all users see all environments in Optimizely regardless of relevance. For our multi-OpCo setup with 40+ isolated production environments (one per market/region), this creates:

   1. UI clutter - users must navigate through dozens of irrelevant environments
   2. Training overhead - OpCo representatives need extensive onboarding to identify their specific environments
   3. Poor UX - cannot create role-specific views for different markets
   4. Risk of confusion - users might accidentally interact with wrong environment

   We cannot use separate Optimizely instances per OpCo because with 100+ flags across 40+ instances, this would require 4,000+ API calls per deployment, hitting rate limits and making emergency rollbacks impossible.

   Outcome we're trying to achieve:

   Enable environment visibility scoping so users only see environments relevant to their role. For example, a Netherlands OpCo representative should only see acceptancenetherlands and productionnetherlands environments, while all other OpCo environments remain completely hidden from their view.

   This would:
   - Reduce cognitive load and training time for OpCo representatives
   - Eliminate risk of users accessing wrong environments
   - Enable role-specific dashboards tailored to each market
   - Maintain centralized flag management while providing isolated user experiences
   - Match functionality already available in competitor tools like ConfigCat

   Role: Technology Specialist - Product Architect

   What are we trying to solve:

   Currently, all users see all environments in Optimizely regardless of relevance. For our multi-OpCo setup with 40+ isolated production environments (one per market/region), this creates:

   1. UI clutter - users must navigate through dozens of irrelevant environments
   2. Training overhead - OpCo representatives need extensive onboarding to identify their specific environments
   3. Poor UX - cannot create role-specific views for different markets
   4. Risk of confusion - users might accidentally interact with wrong environment

   We cannot use separate Optimizely instances per OpCo because with 100+ flags across 40+ instances, this would require… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  0 comments  ·  UX  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating