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:
- Cross-OpCo interference - OpCo A can accidentally modify or delete audiences used by OpCo B
- UI pollution - users see irrelevant audiences from all markets when configuring targeting
- Risk of mis-targeting - OpCo representatives might accidentally select the wrong audience (e.g., "premiumusersgermany" instead of "premiumusersnetherlands")
- No access control - cannot restrict who can modify specific audiences
- 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