-
Issue:
I have a playtester who is 21+ verified, the testing experience is showing as “Unavailable” for him.
-
Solutions tried:
i. Giving him playtest access inside Studio.
ii. Community tester role with the playtest access
iii. Setting audience setting as Limited to Playtesters
1 Like
Issue still occuring. Please help
Hey there!
This is a known issue that usually happens when there is a mismatch between the Group/Experience privacy settings and the user’s account privacy restrictions, even if they are 21+ verified.
Here is a breakdown of why this is happening and a few solutions you can try to get your playtester in.
- Check Account Privacy & Communication Settings
Even if the user is 21+ verified, Roblox has account-level filters that block unverified or unreleased experiences if their privacy settings are too strict.
The Fix:
- Have your playtester go to Settings → Privacy.
- Ensure their communication/privacy settings (such as who can invite them to private servers or join them) are set to Everyone or Friends instead of No one.
- If their account is a managed/under-13 account that was recently upgraded or still has parental controls enabled, certain beta experiences may remain locked.
- Verify Regional Restrictions & ID Verification Status
Sometimes ID verification succeeds, but regional compliance laws (such as those in the EU, South Korea, or the UK) block access to experiences that do not have a completed Experience Questionnaire.
The Fix:
- Go to Creator Dashboard.
- Select your experience.
- Complete the Questionnaire under Creations → Content Rating.
- If the experience doesn’t have a rating, Roblox may automatically block it for certain verified users depending on local laws.
- Group Roleset Permissions (If Using a Group)
If your experience is owned by a Group, the Playtester permission in Roblox Studio’s Team Create is separate from the Group’s role permissions on the website.
The Fix:
- Go to Group Admin → Roles.
- Select the Community Tester role.
- Make sure View group experiences is enabled. If they cannot view group experiences on the website, the Play button may appear as Unavailable, even if Studio grants access.
- Public Release with Access Code / Whitelist
If the Roblox permissions system continues to glitch, the most reliable workaround is to bypass the native Playtester audience setting.
The Fix:
- Set the game’s Audience to Public.
- Add a simple User ID whitelist script in ReplicatedFirst or ServerScriptService.
- If a player’s User ID is not on the whitelist, kick them automatically. This lets your specific playtester join while keeping everyone else out.
- Try a Private Server Link
Sometimes the main Play button is grayed out on the game page, but the user can still join through a direct Private Server link.
The Fix:
- Enable Private Servers for the experience (make them free).
- Generate a Private Server link and send it to your playtester. This often bypasses the standard page restrictions.
Hope one of these helps get your tester in! Let us know if the whitelist workaround or the privacy settings change fixes it.
To make this response even more accurate, let me know:
- Is your experience Group-owned or on a Personal profile?
- Has your playtester tried joining via a Private Server link yet?
- Is your experience currently using any 17+ or 21+ restricted assets?
Hey there!
This is a known issue that usually happens when there is a mismatch between the Group/Experience privacy settings and the user’s account privacy restrictions, even if they are 21+ verified.
Here is a breakdown of why this is happening and a few solutions you can try to get your playtester in.
- Check Account Privacy & Communication Settings
Even if the user is 21+ verified, Roblox has account-level filters that block unverified or unreleased experiences if their privacy settings are too strict.
The Fix:
- Have your playtester go to Settings → Privacy.
- Ensure their communication/privacy settings (such as who can invite them to private servers or join them) are set to Everyone or Friends instead of No one.
- If their account is a managed/under-13 account that was recently upgraded or still has parental controls enabled, certain beta experiences may remain locked.
- Verify Regional Restrictions & ID Verification Status
Sometimes ID verification succeeds, but regional compliance laws (such as those in the EU, South Korea, or the UK) block access to experiences that do not have a completed Experience Questionnaire.
The Fix:
- Go to Creator Dashboard.
- Select your experience.
- Complete the Questionnaire under Creations → Content Rating.
- If the experience doesn’t have a rating, Roblox may automatically block it for certain verified users depending on local laws.
- Group Roleset Permissions (If Using a Group)
If your experience is owned by a Group, the Playtester permission in Roblox Studio’s Team Create is separate from the Group’s role permissions on the website.
The Fix:
- Go to Group Admin → Roles.
- Select the Community Tester role.
- Make sure View group experiences is enabled. If they cannot view group experiences on the website, the Play button may appear as Unavailable, even if Studio grants access.
- Public Release with Access Code / Whitelist
If the Roblox permissions system continues to glitch, the most reliable workaround is to bypass the native Playtester audience setting.
The Fix:
- Set the game’s Audience to Public.
- Add a simple User ID whitelist script in ReplicatedFirst or ServerScriptService.
- If a player’s User ID is not on the whitelist, kick them automatically. This lets your specific playtester join while keeping everyone else out.
- Try a Private Server Link
Sometimes the main Play button is grayed out on the game page, but the user can still join through a direct Private Server link.
The Fix:
- Enable Private Servers for the experience (make them free).
- Generate a Private Server link and send it to your playtester. This often bypasses the standard page restrictions.
Hope one of these helps get your tester in! Let us know if the whitelist workaround or the privacy settings change fixes it.
To make this response even more accurate, let me know:
- Is your experience Group-owned or on a Personal profile?
- Has your playtester tried joining via a Private Server link yet?
- Is your experience currently using any 17+ or 21+ restricted assets?
