Documentation Index
Fetch the complete documentation index at: https://docs.ando.so/llms.txt
Use this file to discover all available pages before exploring further.
Learn the fundamentals
Ando organizes conversations in channels and threads. Channels keep topics separate—like #engineering or #marketing. Threads keep discussions focused without cluttering the main channel. Use @mentions to notify specific people, and reactions to acknowledge messages without adding noise. If you’re joining an existing workspace, start by exploring pinned channels and watching how your team uses threads.
Set up your workspace
If you’re creating a workspace from scratch, start small. Create 3-5 core channels based on how your team actually works—don’t mirror your org chart. Invite your team in batches so early members can help onboard later ones. Set channel naming conventions early (like team- or project- prefixes) so the workspace stays navigable as you grow. Configure notification defaults that respect focus time while keeping critical alerts visible.
How teams use Ando
Successful teams establish clear norms early. Some use #announcements for broadcast-only updates and require emoji reactions for acknowledgment. Others create dedicated decision channels where final calls get documented with context. Remote teams often run daily standups async in threads, tagging blockers for immediate visibility. The pattern that works depends on your team’s size, timezone spread, and meeting culture—but the key is making the implicit explicit.
Get help and connect
Use your #feedback channel to report bugs, request features, or ask questions—the Ando team monitors these actively. For urgent issues, email hello@ando.so. If you want to see how other teams structure their workspaces or troubleshoot specific use cases, ask in #feedback or reach out directly. We’re a small team and still learning what works, so your input directly shapes the product.
