Virtual Report Suite Curation: Impact on user created components prevents use

My organisation has been trying to move to using curated Virtual Report Suites.  However, we have had to abandon these plans because of the following 2 main problems:

• 1) Segments can either be shared to everyone or no one
• 2) Users who create segments metrics are unable to see what they create

Details of the issues encountered...

There are now 3 administrative capabilities relating to segments:

• User admin control over creation of segments
• Sharing of segments (e.g. clicking “share”)
• Customization of Virtual Report Suite Components (VRS Curation)

Unfortunately, they interact with each other in bizarre and contradictory ways.  However, all the problems seem to stem from the “Customization of Virtual Report Suite Components” capability.

Issues observed:

• The sharing of segments becomes all or nothing.

          This is because:

• Any segment that has been included in VRS curation become visible to all users of that virtual report suite (even if the segment is not “shared”)
• Shared segments that are not included in VRS curation cannot be seen by any users
  

This means:

• Either everyone gets a segment, or no one gets a segment
• The segment “share” functionality in analytics becomes completely redundant

• Users who have been granted access to create segments suffer a poor/degraded experience

When a user creates a segment it is not a curated segment within the virtual report suite and is therefore blocked from appearing in the left-hand rail.

This break a well establish workflow leading to much confusion as segments do not appear where users expect them.

(Note: users aren't actually blocked from using segments they've created as they still have the capability within the panels to create segments in the project.)