Parameters
Permission Requirements
Deletion is permission-gated by the backend. In most products, deletion controls are shown only to community creators, moderators, or administrators, but the SDK call is still validated server-side.Delete a Community
Call the delete-community method with acommunityId. TypeScript, Android, and Flutter use deleteCommunity; iOS uses deleteCommunity(withId:).
Client Impact
After successful deletion, handle the client-side effects explicitly:- Remove the community from any local list or cached UI state.
- Navigate away from deleted community detail screens.
- Stop showing actions that require the deleted
communityId. - Refresh affected discovery or membership queries when needed.
Pre-deletion Considerations
Product Policy
Before exposing deletion, decide how your product handles:- What data is retained or recoverable outside the client SDK.
- Whether members should be notified before deletion.
- Whether archive, privacy, or moderation actions are safer than deletion.
Member Management
Refresh membership and discovery views after deletion so users do not see stale references to the deleted community.Best Practices
Implementation Guidelines
- Require multiple explicit confirmations.
- Make users type the community name to confirm.
- Verify user permissions before showing delete options.
- Show clear progress during deletion operations.
- Provide clear confirmation of successful deletion.
User Experience Considerations
- Emphasize the permanent nature of deletion.
- Offer data export before deletion if your product supports it.
- Provide tools to notify community members.
- Handle post-deletion navigation appropriately.
Related Topics
Update Community
Modify community settings as an alternative to deletion
Community Moderation
Manage communities with moderation tools instead of deletion
Create Community
Learn about community creation to understand deletion impact
Member Management
Handle member relationships before community deletion