Moderation capabilities are determined by user roles, ranging from basic users to global administrators with full platform control.
Role Hierarchy Overview
User Roles
Member, Moderator, and Super-Moderator roles with escalating privileges
Admin Roles
Global Admin and Super-Admin roles for platform administration
Custom Roles
Create custom roles with tailored permissions for specific needs
Permission Management
Granular control over user actions and moderation capabilities
User Roles
- Role Types
- Role Comparison
Standard User Roles
Member (Default)
Member (Default)
Basic User Role:
- No moderation privileges
- Standard content creation and interaction
- Subject to all moderation rules
- Can report inappropriate content
- Create posts and comments
- Join communities and channels
- React to content
- Send direct messages
- Update profile information
Community Moderator
Community Moderator
Community Moderation Role:
- General moderation privileges
- Can moderate assigned communities/channels
- Subject to moderation from Super-Moderators and Admins
- Enhanced reporting and review capabilities
- Delete inappropriate content
- Mute and unmute users
- Ban users from channels/communities
- Review reported content
- Pin and feature content
Global Moderator
Global Moderator
Enhanced Moderation Role:
- All community moderator privileges
- Exempt from moderation by regular moderators
- Cross-community moderation capabilities
- Advanced moderation tools access
- Global content moderation
- Cross-community user management
- Advanced analytics access
- Escalation handling
- Policy enforcement
Admin Roles
- Admin Types
- Admin Management
Administrative Roles
Global Admin
Global Admin
Platform Administrator:
- Full moderation privileges across platform
- User role assignment capabilities
- Exempt from all moderation actions
- System configuration access
- Assign roles to other users
- Create and manage admin accounts
- Configure platform-wide settings
- Access to all analytics and reports
- Global ban/unban capabilities
Super-Admin
Super-Admin
System Administrator:
- Highest level of access
- Reserved for critical system operations
- Cannot generate Admin API tokens
- Used for system-level configurations
- Push notification certificate management
- Core system configuration
- Infrastructure-level settings
- Emergency system access
Super-Admin access is automatically granted when accessing console from the social.plus Portal. Create separate admin accounts for regular administrative tasks.
Role Management
- Changing User Roles
- Custom Roles
User Role Assignment
1
Navigate to Community
Go to Community → Communities and select target community
2
Access Members
Click the Manage Members tab to view community members
3
Select User
Choose the user whose role you want to change
4
Change Role
Click Change user role button and select new role
5
Confirm Change
Review selection and click Confirm to apply changes
Role Change Considerations
Promotion Guidelines
Promotion Guidelines
Member to Moderator:
- Verify user’s community engagement
- Assess understanding of community guidelines
- Consider user’s history and behavior
- Provide moderation training and resources
- Evaluate moderation performance
- Assess cross-community needs
- Verify advanced understanding of policies
- Consider platform-wide responsibilities
Demotion Procedures
Demotion Procedures
Role Reduction:
- Document reasons for demotion
- Communicate changes to affected user
- Review moderation history
- Implement gradual privilege reduction
- Monitor post-demotion behavior
Communities must maintain at least one moderator. The last remaining moderator cannot be demoted to member status.
Moderation Tools
- Content Moderation
- User Actions
Automated Moderation
Blocklist Management
Blocklist Management
Reject content that contains words or phrases you don’t want in your community.How rules match:
- Each rule is a word or phrase, matched case-insensitively.
- Rules match as plain text. Characters such as
*or.are literal, not patterns. - Partial match (default): the rule matches anywhere in the text, including inside longer words.
- Exact word match (
isMatchExactWord: true): the rule matches only as a whole word. - Each rule can be enabled or disabled without deleting it.
content(default): checked against chat messages, posts, comments, and polls. For posts, the title is checked too.user: checked against user display names and descriptions.
- The request is rejected with error
400308(HTTP 403). - For chat messages, the sender can also be muted in the channel when a blocklist mute duration is configured. The duration is one network-wide value, not set per rule.
global-admin or super-moderator role skip the check for chat messages. Posts and comments are always checked.Manage rules with the blocklist API. Test text against your rules with POST /api/v3/blocklists/verify:Allowlist Management
Allowlist Management
Keep links in your community limited to sources you trust. When link moderation is on, any link that doesn’t match a rule on your allowlist is rejected.Enable or disable:
- Link moderation is on by default. With an empty allowlist, every link is blocked.
- Toggle it with the network moderation setting
isWhitelistEnabled. When off, all links are allowed.
- Each rule is plain text, matched case-insensitively against every link found in the content.
- A link is allowed if it contains the text of any enabled rule.
- Wildcards and patterns aren’t supported.
*.example.commatches only the literal text*.example.com. To allow a domain and its subdomains, addexample.com. - Protocols get no special treatment.
https://example.comallows only links containing that exact text, sohttp://example.comis still blocked. - Because matching is by substring, a rule can also match text in another link’s path or query string. For example,
example.comallowshttps://other.site/?ref=example.com. Use a more specific rule, such ashttps://example.com/, to reduce this. - Each rule can be enabled or disabled without deleting it.
- The request is rejected with error
400309(HTTP 403). - For chat messages, the sender can also be muted in the channel when an allowlist mute duration is configured. The duration is one network-wide value, not set per rule.
global-admin or super-moderator role skip the check for chat messages. Posts and comments are always checked.Manage rules with the allowlist API. Test links against your rules with POST /api/v3/allowlists/verify:Platform Integration
- UIKit Support
- API Integration
UI Framework Integration
iOS & Android UIKit
Full Moderation Support:
- Network-level moderation
- Community-level moderation
- Enhanced moderator menus
- Real-time permission updates
Web UIKit
Community-Level Support:
- Community moderation only
- Basic moderator interface
- Limited cross-community features
- Standard web interactions
Best Practices
Role Assignment Strategy
Role Assignment Strategy
Effective Role Management:
- Gradual Progression: Promote users through role hierarchy gradually
- Performance-Based: Base promotions on demonstrated moderation skills
- Community Fit: Consider user’s understanding of community culture
- Training: Provide moderation training before role assignment
- Regular Review: Periodically assess role effectiveness
- Active community participation
- Positive user interactions
- Understanding of platform guidelines
- Demonstrated leadership qualities
- Availability for moderation duties
Moderation Consistency
Moderation Consistency
Uniform Policy Enforcement:
- Clear Guidelines: Establish comprehensive moderation guidelines
- Decision Documentation: Record moderation actions and reasoning
- Team Communication: Coordinate between moderators
- Policy Updates: Keep moderation policies current
- Training Programs: Regular moderator training sessions
- Define clear escalation paths
- Set response time expectations
- Establish appeal processes
- Document complex decisions
- Review controversial actions
Community Trust Building
Community Trust Building
Transparent Moderation:
- Clear Communication: Explain moderation actions to users
- Fair Application: Apply rules consistently across all users
- Appeal Process: Provide mechanisms for users to appeal decisions
- Feedback Collection: Gather community feedback on moderation
- Policy Transparency: Make community guidelines easily accessible
- Consistent rule enforcement
- Responsive to community concerns
- Clear communication about policy changes
- Fair handling of disputes
- Regular community engagement
Troubleshooting
Common Role Issues
Common Role Issues
Role Assignment Problems:
- Permission Errors: Verify admin privileges for role changes
- Role Conflicts: Check for conflicting role assignments
- Community Minimums: Ensure communities maintain minimum moderator count
- API Failures: Verify token permissions and API endpoint access
- Use Global Admin accounts for role management
- Resolve role conflicts before new assignments
- Promote additional moderators before demoting existing ones
- Check API token scopes and expiration
Moderation Action Issues
Moderation Action Issues
Common Problems:
- Ban Not Effective: Check user connection status and ban scope
- Content Still Visible: Verify soft deletion vs. hard deletion
- Permission Denied: Confirm moderator privileges and scope
- API Timeouts: Retry operations and check system status
- Verify user role and permissions
- Check action scope (global vs. channel)
- Confirm API token validity
- Review system logs for errors
- Contact support for persistent issues