Open Creator Dashboard > Creations and select the experience. Use Audience > Access Settings to change its minimum age or allowed regions, Configure > Places to select the start place, and the group's roles when another creator needs edit or publish permission. Save the specific page, then test the landing page with a non-owner account.
Sign into Creator Dashboard, select Creations, and open the experience. Check the owner before editing: a user-owned and group-owned experience can have different permissions even when their names are similar.
Open Audience > Access Settings for minimum age or geographic availability. Open Configure > Places when the start place or a place-level setting is wrong. For a group-owned experience, use the group's Collaboration roles when a creator needs playtest, edit, or publish access.
3
Set the minimum age and regions
Under Audience > Access Settings, choose the youngest age allowed to enter the experience and enable only the regions where it should be available. Select Save Changes, then reopen the page and confirm the same values remain selected.
4
Confirm the start place
Open Configure > Places. The place with the star is the start place that players enter from the experience landing page. Select it to edit its Basic Settings; do not change a secondary place when the problem is the initial spawn.
5
Give a group member only the needed permission
For a group-owned experience, open the group's Settings > Roles, select the role, and enable the specific experience permission required, such as Playtest, Edit, or Edit and publish. Select Save Changes. Edit and publish is broader than Edit, so do not grant it merely for playtesting.
6
Check the landing page from outside the owner account
Copy the experience URL from its Creator Dashboard menu and open it with a non-owner account in the intended age and region. Select Play. Success means the allowed account reaches the starred start place and a deliberately excluded account remains blocked.
7
Publish Studio changes separately
Access and dashboard settings do not upload unpublished scripts or map edits. If the start place itself changed, open that project in Roblox Studio and use File > Publish to Roblox, then verify the new version on the same landing page.
If it does not work
If Access Settings cannot be saved, confirm that the signed-in account owns the experience or has the group permission needed to configure it.
If a collaborator can edit but cannot publish, check whether the role has Edit and publish rather than Edit only, then save the role again.
If the landing page opens but joins the wrong map, return to Configure > Places and confirm which place carries the star.
If an age or region change appears saved but the test account remains blocked, check that account's actual age group and region before widening the experience setting.
ⓘ Sources and verification
Checked against official documentation on . Scope: Roblox Creator Dashboard.
Source-checked against Roblox's current Creator Dashboard configuration and group-role documentation. No live experience access or collaborator permission was changed during review.
