Pretty sure they intentionally leave that up to our interpretation to emphasize that we can establish our own rules
At this time, users must be present in the community before they can be banned. It’s possible in the future we may add preemptive banning capabilities. Thanks for the suggestion!
The community owner must manually grant out the Ban Members permission to rolesets before the feature is shown to community admins/moderators.
Note: a community owner in this case is defined as the singular Roblox user who holds the community.
If a community has co-owner roles, the community owner must grant the permission to those rolesets first before those users can use the feature.
Currently, it is not possible to disable alt blocking.
Hiya! Between the flow of both owned and non-owned communities, a lot of history sits on the site, and I can imagine alike the old ROBLOX Forums, someone will likely scrape all the group walls like the public had done with the Forums.
I am curious on tool workflows for exporting this information on 1. owned community level and 2. communities not owned by us / even locked communities.
In finding out specific information on the founding of a community I cater to from 11 years ago, group walls provided information on the founding and naming of a Bloxy Award participant community. In this paradox, it becomes apparent that certain degrees of information should be able to be gathered for those wanting to understand their community’s history in a time manner. There are quite a few communities I would like to export group walls from, and this would be WAY easier than running code on the APIs to get it.
Will Roblox support export options for group walls? And, if so, could individuals outside groups be allowed to as well?
It would be extremely convenient to allow walls to be exported by those who can read them on the public page. I understand though if that’s not possible for public export options, it’s probably taxing. Either options would be most fruitful though!
Mixed feelings about the word “Communities” (takes longer to type), but I’ll take it. However, it’s nice to see an advancement in these communities especially for those groups that depend on them like army and clothing styled ones.
thats not only on the app. its also the site. the app uses the roblox site for links like groups
Can you ban users from communities through the API? Can’t find a reference. Also what does it mean by group membership?
thanks for that message to me!
Is this why /communities/configure?id={communityId}#!/revenue/sales
doesn’t show sales anymore?
Is there a way to ban someone who isn’t inside the group currently, as we may not want such person in the group in the future? Cause current API endpoint doesn’t allow banning non-members for some reason, even tho that should be an option.
It should be allowed to ban users in general, not limited to members.
The feature is still in testing and not yet enabled on public groups. The only group that has it is a testing group.
It’s been put into discussion, but wholeheartedly agree. Staff have been posting responses here, and I think the only reason we have this currently without guest banning is due no UX/UI added for it yet. Hopeful we get an update on this though soon.
Edit
It is strange we can’t ban guests, I wonder why checks for membership were put into the code for that. Communities have lengthy history, so accounting for this is important.
Edit again
I guess it does have to do with checks on the Ban button, as they might’ve copied code checks from the Exile button which required membership. That’s my best guess on why it’s like this.
what if we don’t have a membership?
What endpoint are you using for ban?
Exactly. I hope this comes in the future. I can’t wait for the day when all the pages will get native support for the App so the annoying web pop-up will be gone.
They are probably saying that you shouldn’t use your real full name, including both the first and last name. If you use just the first name it’s probably fine.
I love these new features, a great update from Roblox! Thank you.