Managing Users & Permissions

## Control Who Can Do What on the Platform User and permission management is one of the most important responsibilities of a Spaghetti Showdown superadmin. This guide covers how to manage superuser access, assign blog editor permissions, grant tournament organizer status, and handle common administrative scenarios. ### Permission Levels Spaghetti Showdown uses a role-based permission system with several tiers: **Regular User (Default):** Every registered player starts as a regular user. They can: - Create and manage their player profile - Register for tournaments and compete - Earn Spaghetti Points and purchase store items - Join communities and participate in matchmaking **Tournament Organizer:** Users with tournament organizer status can: - Everything a regular user can do - Create and manage tournaments - Access the tournament dashboard with bracket, seeding, and streaming tools - Use the widget system for OBS overlays **Blog Editor:** Users with blog editor permissions can: - Everything a regular user can do - Access the blog editor and create new posts - Edit and publish their own blog posts - Manage tags on their posts **Superadmin:** Users with superadmin privileges can: - Everything all other roles can do - Access the full Admin Panel - Manage other users permissions - Moderate content across the platform - Configure platform settings ### Managing Superuser Access Granting superadmin access should be done with extreme caution, as superadmins have unrestricted access to all platform functions: 1. **Navigate to the Users tab** in the Admin Panel 2. **Search for the user** by name or email 3. **Click on their profile** to open the user details view 4. **Toggle the Superadmin switch** — confirm the action when prompted 5. **Notify the user** that they now have admin access and brief them on responsibilities To revoke superadmin access, follow the same steps and toggle the switch off. The change takes effect immediately — the user will lose access to the Admin Panel on their next page load. ### Blog Editor Permissions Blog editor access is less sensitive than superadmin but should still be given thoughtfully. Blog editors can publish content that represents the platform: 1. **Find the user** in the Users tab 2. **Toggle Blog Editor** — the user immediately gains access to the blog editor 3. **Communicate expectations** — let them know about content guidelines and the review process Blog editors can only edit and delete their own posts. They cannot modify other editors content or access admin-only features. ### Tournament Organizer Status Tournament organizer status enables users to create and run tournaments. This is commonly granted to community leaders and event organizers: 1. **Find the user** in the Users tab 2. **Toggle Tournament Organizer** — the user can now create tournaments 3. **Point them to documentation** about tournament creation and management Tournament organizers only have control over their own tournaments. They cannot affect other organizers events or access the Admin Panel. ### Common Administrative Scenarios **A user reports inappropriate content:** Find the offending content (post, comment, or profile) through the Admin Panel. Review it against platform guidelines. Remove or archive the content if it violates the rules. Notify the content creator with an explanation. **A community needs a new leader:** If a community leader becomes inactive, you can transfer community ownership in the Communities tab. Select the community, find the current owner, and reassign ownership to a nominated member. **A tournament organizer is having technical issues:** Use the impersonation feature to view the platform as that user. This helps you reproduce and diagnose the problem without needing remote access to their device. **A user requests account deletion:** Handle account deletion requests from the Users tab. Ensure you understand the implications — deleting an account removes their tournament history, store purchases, and community memberships. ### Best Practices - **Keep the superadmin list small** — only grant admin access to people who genuinely need it - **Review permissions regularly** — remove access from users who are no longer active in their roles - **Log significant changes** — document when and why you changed someone permissions - **Respond to user requests promptly** — permission changes should not bottleneck community activity Effective user management keeps the platform secure while empowering community leaders to run great events.