The title says to “simplify”, but what that really means is to “unscramble”; to unscramble the scrambled egg known as the system that manages access & privacy settings for experiences/places.
A year-old repost/bump of this original post from April 2021.
As a human being with a somewhat functional frontal lobe, it is impossible to comprehend the access and privacy settings for experiences and places, not to mention the four separate interfaces that house the controls & options for these settings. It’s overcomplicated and some access/privacy options don’t even work as intended. Turning some settings on will turn others off, and turning some settings off will turn other settings off. Experiences appear publicly when they should not, and conversely don’t appear when they should.
Attempts to interact with this convoluted system is most comparable to playing Uno with a deck of all +4’s. It’s brain-melting, time-consuming, and there is no winning.
Any fix to this problem would give developers actual, real, true control over the front-frontend presentation and delivery of their experiences to their audience, and comprehensible privacy settings for test and collaboration environments.
/places/placeId/update/
/universes/configure?id=universeId#/#basicSettings
note: the description says “see”, but the “Public” setting will also allow everyone to PLAY the experience.
Studio → Game Settings → Permissions
When website settings conflict, both of the options will be grayed out.
Studio → Collaborate
Four interfaces. Four. Interfaces. This needs to be addressed.
Thanks.