Hi Creators,
As part of our ongoing effort to expand the capabilities of Roblox Communities, we are preparing a number of changes that may impact third-party developers. Please review the details below and prepare your code for these changes where necessary.
Member List Privacy
This January, we will be releasing a new community privacy setting that will let communities control whether their member list is visible to non-members. When this update rolls out, all existing communities will automatically have the Members list publicly visible setting enabled, while all new communities will have the setting disabled by default. Owners will be able to change this setting at any time.
Non-members making requests to groups with this setting disabled will now receive a 403 (Forbidden) response. See below the impacted routes:
Open-cloud-groups
ListGroupMemberships: GET /cloud/v2/groups/{groupId}/memberships
A member of a community with the setting disabled will see no difference in response.
Example
Request: https://apis.roblox.com/cloud/v2/groups/{groupId}/memberships?maxPageSize=10
Response for a member
{
"groupMemberships": [
{
"path": "groups/{groupid}/memberships/{membership1}",
"createTime": "2023-01-30T18:59:55.563Z",
"updateTime": "0001-01-01T00:00:00Z",
"user": "users/{userId1}",
"role": "groups/{groupid}/roles/{roleid2}"
},
{
"path": "groups/{groupid}/memberships/{membership2}",
"createTime": "2023-02-10T17:54:59.160Z",
"updateTime": "0001-01-01T00:00:00Z",
"user": "users/{userId2}",
"role": "groups/{groupid}/roles/{roleid1}"
},
{
"path": "groups/{groupid}/memberships/{membership3}",
"createTime": "2024-08-12T17:12:33.670Z",
"updateTime": "0001-01-01T00:00:00Z",
"user": "users/{userId3}",
"role": "groups/{groupid}/roles/{roleid1}"
}
],
"nextPageToken": "id_2zwAAAZLuuVOdxBBpFVwTAv9O96AU245oYHoS"
}
Response for a non-member
Error with status code: 403 (Forbidden)
Groups-api
GetGroupMembersInRole: GET /v1/groups/{groupId}/roles/{roleSetId}/users
GetGroupMembers: GET /v1/groups/{groupId}/users
Similar to the above example, the response for a member of the community using the above endpoints will remain unchanged.
Response for a non-member
Error with status code: 403 (Forbidden)
We’re targeting a release of this update for the week of January 12th, 2026, so please review and revise any impacted code prior to January 12th to avoid any disruption to your tools.
Display Names in Audit Logs
Currently, audit log descriptions feature Roblox Display Names for acting users, and Roblox Usernames for the target users. To reduce confusion, all users in audit log descriptions will be shown as their Roblox Display Name. This change is reflected in the Groups API endpoint’s TargetName field, which will soon return the user’s display name when one is set instead of their username.
Current audit log example
{
"actor": {...}
"actionType": "...",
"description": {
"TargetId": ...,
"TargetName": "MyAwesomeUsername"
},
"created": "..."
}
Updated audit log example
{
"actor": {...}
"actionType": "...",
"description": {
"TargetId": ...,
"TargetName": "MyDisplayName"
},
"created": "..."
}
Updates to the Groups-API audit log endpoint will go into effect December 11th. Please review the changes and prepare accordingly.
Rate Limit Adjustments
The Groups API today supports a number of routes that provide necessary information for our clients to function properly, but are also used by third-party developers to integrate with Roblox. In order to better protect the health of our services while also ensuring continuous availability for developers, we will be fine-tuning our rate-limiting parameters which will result in an overall reduction for most routes. These new limits have been adjusted on a per-route basis to generously accommodate traffic consistent with average daily patterns.
While we do not anticipate a vast majority of third-party developers will notice any changes, some high-volume callers may experience elevated 429 (Too Many Requests) responses.
These rate limit adjustments will go into effect beginning December 11th.
Please let us know if you have any questions or concerns regarding these changes, and thank you for your support!