Changelog
Changes that affect developers using the admin panel API or the SentinelShare bot. Fields are only ever added to the API, never renamed or removed.
26 October 2026
- Staff alerts. The SentinelShare bot warns a staff channel when someone with an active ban joins your Discord, and when another community bans someone already in it. Set the channels on your community's page or with
/setup alertsand/setup notifications. See Staff alerts. - Community pages. Every community has a page with its staff, activity, bans filed and track record, plus its Discord settings.
- Appeal tracking. Appellants get a private link to follow their appeal, with a message from the community that decides it. Appeals are decided by the community that filed the ban, or by network staff.
- Discord scans and Reports.
/bans scanchecks every member of a Discord for SentinelShare bans, 1,000 at a time. It replies with how many have bans and a link to the report, which is saved under Reports on the website with every matched member, their player profile, ban types and the communities that filed them. See Scan your Discord. - Developer docs. These pages, each downloadable as Markdown, plus llms.txt and the whole set as one file for AI assistants.
- SentinelShare bot.
/bans check,/bans add,/bans remove,/bans verify,/staff add,/staff remove,/staff list,/whoamiand/setup notifications. Commands run as the staff member who typed them. See Add the SentinelShare bot. - Lifting bans. Staff who can file bans can now lift bans filed by anyone in their own community, on the website, in Discord and through the API.
- Admin panel API launched. Community API keys,
GET /integration/bans(change feed) andGET /integration/lookup. See Admin panel API. - One profile per player. Arma UIDs, Discord IDs, IP addresses and names now live on a single player profile, so a ban record's
playerlists every known identifier, and profiles that may be the same person appear inother_matches.