October 2026: community updates
A clearer dashboard, more reliable Roblox ranking and join reviews, new membership tools, and fixes across Discord, events, and integrations.
Last updatedOctober brought a new community overview, better ways to follow Roblox requests, and fixes for everyday tasks such as updating Discord roles and hosting events. We also worked on faster page loads and clearer messages when something needs your attention.
Here is the month's round-up. Features still depend on your plan, permissions, and connected services. Some additions roll out gradually; check the availability shown in your dashboard.
A clearer home for your communities
- Community Pulse brings a 7- or 30-day membership trend to community management Home, alongside weekly summaries of completed events, attendance entries, and recorded rank changes. Connection indicators sit beneath the community name. Attendance totals count entries across events, not unique people.
- The Communities page is easier to scan, with larger artwork, more readable cards, and layouts that adapt to the space available. You can filter between all communities and those you own.
- Recent-community shortcuts help you return to up to four communities in this browser. They follow the signed-in account and selected Roblox account, and only offer access you still have.
- Settings and upgrade notices are more consistent, with clearer loading states, improved mobile spacing, and fixes for dialogs that reset or shifted when first opened.
- Eligible legacy communities have a clearer migration entry on community Home, with a link into the existing subscription-migration process.
- A consistent look across Clan Labs. The website, dashboard, and documentation share refreshed blue/navy styling, clearer Discord command labels, and improved navigation.
More reliable Roblox ranks and join reviews
- Track requests in Roblox operations. Rank changes and join decisions can be saved while waiting for Roblox capacity. The dashboard and Discord status actions help you distinguish a waiting request from a confirmed result.
- Better recovery from interrupted rank changes. Partially completed changes can recover automatically. Manual recovery follows the latest valid rank command; automatic progression checks the member's current progression rules. Requests that need an administrator's review are identified separately and no longer hold up the whole community queue.
- Safer handling of timeouts and busy periods. We fixed cases where queued work expired too early, profile lookups lost a pending rank change, or repeated requests competed with work already underway. A missing response still does not mean a change failed: check the saved request before trying again.
- Large pending-join lists load in smaller batches. The dashboard loads 20 applicants at a time instead of waiting for the full backlog. Search covers the applicants loaded so far; Check All Requests collects its own review list.
- Bulk reviews keep saved progress. Keep the page open while applicants are being collected and saved. Saved applicants continue processing after you leave or reload. You can pause further submissions and resume, and the results distinguish confirmed decisions from work still waiting or whose submission is uncertain.
- Confirmed join decisions have an audit trail. Accepted and declined requests identify the applicant and the staff member or community automation responsible, with the original request time when available. Individual, bulk, and scheduled decisions are covered. Queued or failed attempts do not appear as completed decisions; older decisions are not backfilled. You can choose a separate Discord delivery rule for these entries, which cannot be rolled back.
- Rank failures explain what needs attention. Messages distinguish Discord access problems, changed permissions or verified accounts, blacklist restrictions, rank hierarchy, locked ranks, and a promotion or demotion whose next rank has changed. Failed requests offer Support details with a request ID and a recognised failure code. For an unknown failure, check the member's current Roblox state and share the request ID with support.
- Roblox connections recover more reliably. Slow authorization refreshes and temporary provider failures are handled more carefully, while a feature-level permission denial no longer unnecessarily disconnects the community.
- Ownership and role checks match newer Roblox communities. Setup checks the actual community owner rather than assuming ownership from rank 255. We also corrected handling of private roles, multiple roles, Guest ranks, and suspension restoration.
For API status and retry guidance, see Roblox operations. For recruitment, see Pending join reviews.
New membership tools Pro
October's membership work adds four related capabilities:
- Starting-rank onboarding: assign a configured starting Roblox rank when an eligible new join is observed. Members who already hold a higher rank keep it, and moderation and rank restrictions still apply.
- Departure cleanup: mark an observed departure inactive without deleting the member's history, and optionally remove managed main-group rank roles in Discord. Verification roles, external group-bind roles, and unrelated roles are preserved.
- Join surge alerts: notify a selected Discord channel when distinct joining members reach your threshold within a chosen time window. A cooldown limits repeat alerts; an alert does not ban or remove anyone.
- Membership retention: review observed joins, departures, and 7- and 30-day retention in Community Analytics. Rejoining starts a new membership period, and members who have not reached a retention milestone are not counted in that milestone's percentage.
These tools require full Pro access, Roblox community audit authorization, and an enabled rollout. If Membership settings says awaiting release, you can prepare settings with actions disabled, but the feature is not active yet. Approving Roblox access or upgrading does not override that notice.
Where tracking is available, analytics run independently of the optional action switch. Reports reflect supported activity observed since tracking began, not a reconstruction of the community's entire history. Missing records and periods without tracking limit what retention figures can show.
Events that are easier to set up and run
- Mention several roles from the dashboard. Event hosts can select up to 25 allowed Discord roles, while configured defaults remain required.
- Describe your event types. Optional descriptions of up to 160 characters appear in the searchable event-type picker. Settings use collapsible cards so existing types are easier to browse and edit.
- Start scheduled events in the dashboard. If the start saves before Discord refreshes, the announcement update can continue without creating another event.
- Understand event history at a glance. Audit messages use event names and clearer wording for creation, starting, attendance changes, and deletion.
See Events and attendance for the full workflow.
Discord fixes you will notice
- Fewer stale ranks and nicknames. Automatic rank updates apply enabled nickname settings as well as roles. Rank names and XP requirements refresh after changes to the community's rank configuration. XP replies can show pending rank progress and update the same message when it completes.
- Verified non-members can update their profiles. We fixed cases where a missing Guest configuration prevented verified roles and nicknames from updating. The dashboard can restore the Guest row through Sync from Roblox.
- Roles shared by awards stay stable. A Discord role used by several medals or qualifications is kept while the member still qualifies through any active award or binding, rather than being repeatedly removed and re-added.
- Unverified-role cleanup is more consistent. Confirmed unverified users no longer keep roles they lost eligibility for. Temporary identity lookup failures are kept separate from a confirmed unverified state.
- Nitro boost XP no longer changes on every update. We fixed repeated deductions when boost status had not changed, including overlapping profile updates.
- Clearer command feedback. Longer-running commands show loading feedback, results stay in their embeds, and missing Discord permissions use readable names such as Manage Roles. Confirmed channel-access errors explain what an administrator should check instead of suggesting an unrelated Roblox reconnection.
- More accurate lists and settings. Pagination fixes correct page totals and prevent empty or overlapping page changes.
/settingsshows more of the configuration already available in the dashboard, including required applications, audit destinations, nickname rules, and eligible bot branding. - Explore community games from Discord. The Roblox Experiences button in
/communityswitches to public experiences with play links, descriptions, and visit counts, with a way back to community information.
Faster pages and fewer interruptions
Dashboard pages load less code up front and defer work that is not needed immediately. Member avatars and community artwork load more efficiently, and navigation, loading placeholders, audit views, and sidebar transitions have been refined to reduce jumps and flicker.
The website also shows its main content sooner, uses smaller font and icon downloads, and avoids unnecessary repeat pricing requests. Mobile menus, short-screen layouts, keyboard navigation, and reduced-motion behaviour received fixes across the sites.
Roblox requests share capacity more fairly during busy periods, with better handling of large join backlogs and recovery work. Update handling also supports temporarily pausing new rank and join requests while compatible parts of the service remain online. These changes reduce avoidable delays; Roblox and Discord availability still affect completion times.
Better guides and integration tools
- Test API endpoints from the reference. Every documented endpoint has a Test endpoint panel for entering a request and inspecting its real response. Requests go to the configured API, so writes affect real data. Credentials stay in browser memory and clear on reload or Clear credentials.
- Follow longer-running API requests. Integrations can queue a Roblox rank change, read its saved status, and cancel unsent work. Acceptance is separate from completion, and timeout guidance explains how to avoid duplicate changes.
- Older profile URLs work with a trailing slash again. We fixed a compatibility issue that incorrectly returned a not-found response for those requests.
- Roblox API SDK 1.2.0 adds queue, status, and cancellation helpers for Roblox operations. The SDK covers all 58 public API v2 operations and includes server-side examples. Download the Roblox SDK and importable model (.rbxm).
- Find practical guides more easily. The website has new walkthroughs for managing a Roblox community from Discord, syncing rank roles, and tracking XP and quotas through events, alongside clearer feature links and updated screenshots.
- Experimental browser-assistant support helps compatible browsers find documentation, compare published plans, and read permitted community information. Existing sign-in, plan, and staff-permission checks still apply; browser support is required.
Privacy, permissions, and account safety
- One browser analytics choice across Clan Labs. The website, dashboard, and documentation share optional-analytics preferences. Use Cookie preferences to review or change your choice. This is separate from your community's operational analytics.
- Clearer data-request progress. Retryable export and erasure problems are distinguished from requests that have exhausted their retries and need attention.
- Membership data controls. Observed membership records are included in the relevant export and erasure workflows. The Membership tracking reset clears that history, inactive status, and automation settings; it does not undo external Roblox rank or Discord role changes.
- More precise owner safeguards. Division setup requires Super Owner access to the parent community. Confirmed Owners and Super Owners are exempt from membership-based community blacklists in supported checks; direct user blacklists, global bans, and active suspensions still apply.
- More reliable Discord permission synchronization, including recovery when members have left, role assignments are stale, or a successful retry should clear an earlier warning.
- Security and migration maintenance. We updated dependencies, tightened request validation and privacy protections, and improved checks around legacy migration and cleanup to protect existing records.
More community improvements
- Browse members and edit their profiles in one place. Select a roster row to open the profile beside it, with a simple way back to the roster on mobile. Edit the experience, quota, medals, or qualifications your permissions allow, then Save changes or Discard the draft. Recent activity is expanded by default, and award selectors are searchable. See Members and profiles.
- See who holds each award. Medal and qualification pages show recipient counts and paginated holder lists. Authorised staff can search members, add awards, Award again for another medal copy, or Remove one. Copy counts make repeated medals clear; qualifications remain unique per member. See Medals and qualifications.
- Attendance saves as you work. Events use a list and detail workspace, show linked Roblox experience names, and save attendee changes automatically for started events. Wait for All changes saved, or use Retry if needed. Export event CSV downloads event timing and participant roles with Roblox names and IDs, excluding Discord IDs, proof links, notes, and account links. See Events and attendance.
- Application tools are easier to reach. Copy a link, edit, duplicate, save a template, or delete a permitted form directly from its card. Response review keeps its separate permission, and required join forms remain protected from deletion. See Applications.
- Pending API rank checks avoid unnecessary replacement requests. Automatic rank checks can reuse matching active work while permissions remain valid. Pending responses tell integrations to keep checking the saved status, with a two-second polling delay where supplied. Do not repeat an XP change or event finish to resolve a pending rank: those points or awards may already be saved. This does not make every write safe to repeat. See API status and retry guidance.
- Owner blacklist checks are more consistent. Confirmed Owners and Super Owners retain the supported group-blacklist exemption when requesting queued rank changes. Direct user blacklists, global bans, and restrictions on the target still apply. Warning - Blacklisted now makes the affected person clearer. See Blacklist rules.
- A Discord delivery failure causes less disruption. The bot handles blocked DMs, missing channel access, and expired interactions without stopping its other work. An enabled verification prompt is still attempted if a welcome message fails. Delivery still depends on Discord permissions and privacy settings; missed messages are not guaranteed to be replayed. See Welcome message checks.
Need help with a specific change? Start with Troubleshooting or contact Clan Labs support with the affected community and the message you see.