Skip to content

USL Discord Server Guide

Welcome to the USL Community!

The USL Discord server is your primary communication channel during the Early Adopter Program. Here you'll find support, connect with other early adopters, and get real-time updates from the USL team.

Server Invite

Invite Link: https://discord.gg/usl-early-adopters
(Provided in your onboarding email)

Server Structure

📢 Announcements & Updates

#announcements

  • Purpose: Official announcements from USL team
  • Read-only: Only team can post
  • Check: Daily
  • Content: Product updates, office hours schedule, important dates

#changelog

  • Purpose: Technical changelog and release notes
  • Read-only: Auto-posted from GitHub
  • Check: Weekly
  • Content: New features, bug fixes, breaking changes

#pilot-updates

  • Purpose: Pilot program specific updates
  • Read-only: Team only
  • Check: Weekly
  • Content: Program milestones, deadlines, events

💬 General Channels

#early-adopters

  • Purpose: Main discussion channel for pilots
  • Who: All early adopters + USL team
  • Use For:
  • General discussions
  • Sharing progress
  • Asking quick questions
  • Community building
  • Celebration of wins! 🎉

#introductions

  • Purpose: Introduce yourself and your project
  • Use Once: When you first join
  • Template: 
    Hi! I'm [Name] from [Company/Project]
- Role: [Your role]
- Building: [Brief project description]
- Excited about: [What excites you about USL]
- Background: [Relevant experience]

#showcase

  • Purpose: Show off what you're building
  • Use For:
  • Screenshots of your application
  • Demo videos
  • Cool features you've implemented
  • Milestones achieved

#random

  • Purpose: Off-topic chat
  • Use For:
  • Non-USL discussions
  • Memes (keep it professional!)
  • Weekend plans
  • General tech chat

🆘 Support Channels

#help

  • Purpose: Technical questions and support
  • Response Time: < 24 hours (business days)
  • Use For:
  • Compilation errors
  • Syntax questions
  • Deployment issues
  • Configuration problems

Format Your Questions: 

**Issue**: Brief description
**Error Message**: (if applicable)
**Code**: ```usl
// Your code here
Environment: USL v1.0, macOS, PostgreSQL 14 What I've Tried: ... 
#### #feedback
- **Purpose**: Share feedback and suggestions
- **Use For**:
  - Feature requests
  - Pain points
  - UX improvements
  - Documentation gaps
  - Weekly feedback submissions

#### #bugs
- **Purpose**: Report bugs
- **Auto-synced**: To GitHub Issues
- **Use For**:
  - Bug reports (with reproduction steps)
  - Unexpected behavior
  - Performance issues

**Bug Report Template**:
```markdown
**Bug**: Brief description
**Expected**: What should happen
**Actual**: What actually happens
**Steps to Reproduce**:
1. ...
2. ...
3. ...
**USL Version**: 1.0.5
**OS**: macOS 14.2

📚 Resources & Learning

#resources

  • Purpose: Curated learning materials
  • Read-only: Team posts resources
  • Content:
  • Tutorials
  • Best practices
  • Example code
  • External articles

#office-hours-questions

  • Purpose: Submit questions for office hours
  • Use Before: Tuesday/Thursday sessions
  • Format: One question per message
  • Upvote: Questions you want answered (👍 reaction)

#office-hours-recordings

  • Purpose: Access recorded sessions
  • Posted: Within 24 hours of session
  • Content: Zoom recordings + transcripts

🚨 Critical Channels

#emergency

  • Purpose: Production-critical issues only
  • Response Time: 2 hours (business hours)
  • Use Sparingly: For true emergencies
  • Tag: @emergency when posting

What Qualifies as Emergency: ✅ Production system down
✅ Data breach or security incident
✅ Critical bug affecting users
✅ Unable to deploy critical fix

Not Emergency: ❌ Development questions
❌ Non-critical bugs
❌ Feature requests
❌ Documentation questions

🎓 Learning Together

#study-group

  • Purpose: Collaborative learning
  • Use For:
  • Study sessions
  • Pair programming
  • Code reviews
  • Learning new features together

#success-stories

  • Purpose: Share wins and learnings
  • Use For:
  • Milestones achieved
  • Problems solved
  • Lessons learned
  • Performance improvements

👥 Team-Specific (If Applicable)

Private channels may be created for individual pilot teams: - #team-[company-name] - Private discussions with USL team - Confidential topics - 1-on-1 support

Discord Best Practices

Do's

✅ Search before asking - Use Discord search to see if your question was answered
✅ Use threads - Keep discussions organized
✅ Tag appropriately - @USL-Team for urgent matters
✅ Format code - Use code blocks for readability
✅ Be helpful - Answer others' questions if you can
✅ React to messages - Show appreciation with reactions
✅ Update your profile - Add your company/project name

Don'ts

❌ Don't spam - Wait for responses before reposting
❌ Don't DM team members - Use public channels (unless invited)
❌ Don't share credentials - Never post API keys, passwords, etc.
❌ Don't go off-topic - Use appropriate channels
❌ Don't ping @everyone - Reserved for team use
❌ Don't share confidential info - Use private channels or email

Notification Settings

Recommended setup:

Desktop Notifications

  • @mentions: On
  • #announcements: All messages
  • #pilot-updates: All messages
  • #emergency: All messages
  • Other channels: Mentions only

Mobile Notifications

  • @mentions: On
  • #emergency: All messages
  • Other channels: Off (to avoid notification overload)

Custom Settings

  1. Right-click channel name
  2. Notification Settings
  3. Choose level:
  4. All Messages
  5. @mentions only
  6. Nothing
  7. Use server default

Discord Roles

Roles help identify community members:

🏆 Early Adopter Roles

  • @Early-Adopter: All pilot participants
  • @Healthcare: Healthcare pilot
  • @FinTech: Financial services pilot
  • @SaaS: SaaS pilot
  • @E-commerce: E-commerce pilot
  • @Enterprise: Enterprise pilot

👨‍💻 USL Team Roles

  • @USL-Team: All USL team members
  • @Core-Dev: Core developers
  • @Support: Support team
  • @Founder: USL founders

🎖️ Achievement Roles

Earned through participation: - @First-Deployment: First successful deployment - @Bug-Hunter: Reported 5+ bugs - @Helpful: Helped others 10+ times - @Contributor: Contributed to USL codebase - @Completionist: Finished all pilot milestones

Voice Channels

🎙️ Office Hours

  • Tuesday Office Hours: 2-3 PM ET
  • Thursday Deep-Dive: 10-11 AM ET
  • Join for live sessions

🤝 Coworking

  • General Coworking: Drop-in anytime
  • Study Room 1-3: Scheduled sessions
  • Mute by default, use text chat

📞 1-on-1

  • USL Team 1-on-1: Private calls with team
  • By invitation only

Discord Commands

Useful bot commands:

Information

  • /help - Show bot commands
  • /docs [topic] - Search documentation
  • /examples [type] - Get code examples
  • /status - USL service status

Support

  • /ticket create - Create support ticket
  • /feedback - Submit feedback form
  • /office-hours - Show schedule

Fun

  • /progress - Show your pilot progress
  • /leaderboard - Early adopter leaderboard (opt-in)
  • /celebrate - Celebrate a win! 🎉

Finding Information

Search Discord

  1. Click search icon (top right)
  2. Use filters:
  3. from:USL-Team - Messages from team
  4. in:#help - Messages in specific channel
  5. has:link - Messages with links
  6. before:2026-02-01 - Messages before date

Search Documentation

  • Use /docs [topic] command
  • Or ask in #help

Browse Pinned Messages

  • Click pushpin icon (top right)
  • Important messages are pinned

Community Guidelines

Be Respectful

  • Treat everyone with respect
  • No harassment or discrimination
  • Professional tone
  • Constructive feedback only

Be Collaborative

  • Help others when you can
  • Share your learnings
  • Provide constructive feedback
  • Celebrate others' successes

Be Professional

  • This is a professional community
  • Keep conversations work-appropriate
  • No spam or self-promotion (unless relevant)
  • Respect confidentiality

Be Patient

  • Team responds within 24 hours (business days)
  • Other early adopters are volunteers
  • Complex questions take time
  • Check documentation first

Getting Help

  1. Search Discord - Question might be answered already
  2. Check Documentation - Use /docs command
  3. Ask in #help - Format question clearly
  4. Attend Office Hours - Live support
  5. Email Support - For sensitive issues
  6. Emergency Tag - Only for true emergencies

Integration with Other Tools

Discord is integrated with: - GitHub: Auto-post issues, PRs, releases - Status Page: Incident notifications - Calendar: Office hours reminders - Zoom: Office hours links

Mobile App

Download Discord mobile app: - iOS: App Store - Android: Google Play

Stay connected on the go!

Leaving Discord

If you need to leave after program: - Alumni have continued access (read-only) - Can return if needed - Transition to public Discord server

Questions?

Having trouble with Discord? - Discord Help: Ask in #help - Email: early-adopters@usl.dev - Discord Support: https://support.discord.com

Welcome to the community! See you in Discord! 💬

Last Updated: January 15, 2026