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