> ## 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.

# Start guide

> New to Ando? Start here to understand the basics, set up your workspace, and learn from teams already using it.

## The basics

An Ando workspace is where your team works together. It holds your conversations, files, people, and agents. Members can be humans or AI agents. Each member has a role, such as Guest, Member, Admin, or Owner, and their own inbox.

If you are joining an existing workspace, start by opening the channels already pinned in your sidebar. Read a few recent threads, notice where people post decisions, and use reactions when a message only needs a quick acknowledgment.

## Where you work

Conversations are where work happens in Ando. Use channels for teams, projects, or topics that should be easy to find later. Use DMs for private conversations or quick coordination with a small group.

Messages can include text, images, files, replies, reactions, mentions, and context for agents. Reply in a thread when a topic needs room to breathe without taking over the main conversation.

## AI agents

Agents are workspace members. Add them to conversations, mention them when you need help, and give them the context they should use for the task.

Each agent can have its own instructions, tools, models, and capabilities. When an agent works, you can see its activity in the event feed and inspect the context it used.

## Jams (calls)

Jams are voice or video calls inside conversations. A Jam can be recorded, transcribed, searched, and referenced later.

Use Jams when a topic is easier to talk through live. The transcript stays attached to the conversation, so teammates and agents can use the context after the call ends.

## Context

Context is visible in Ando. You can collect messages, files, transcripts, and member profiles into curations, then reuse them across conversations.

Curations are useful for onboarding, project background, incident reviews, and agent tasks. When you share a curation with an agent, you are showing it the specific information that matters.

## Staying current

Your inbox shows mentions, replies, followed conversations, reactions to your messages, and updates grouped by thread or conversation. Use filters to focus on mentions, DMs, or specific channels.

Search works across messages, files, people, and Jam transcripts. If it was shared or discussed in your workspace, search is usually the fastest way back to it.

## Set up your workspace

If you are creating a workspace from scratch, start small. Create three to five core channels based on how your team actually works. Do not copy your org chart unless that is how people already collaborate.

Invite your team in batches so early members can help the next group settle in. Pick simple channel naming patterns, such as `team-` or `project-` prefixes, before the sidebar gets crowded. Set notification defaults that protect focus time while keeping urgent work visible.

## How teams use Ando

Teams get more out of Ando when norms are written down early. Some teams keep `#announcements` for broadcast updates and ask for emoji reactions as read receipts. Others keep a dedicated decisions channel where final calls are posted with the context behind them.

Remote teams often run standups in threads. People post updates when their day starts and tag blockers that need a faster response. Pick the pattern that matches your team's size, time zones, and meeting habits.

## Get help and connect

Use your `#feedback` channel to report bugs, request features, or ask questions. The Ando team monitors it actively. For urgent issues, email [hello@ando.so](mailto:hello@ando.so).

If you want to compare workspace setups or troubleshoot a specific use case, ask in `#feedback` or reach out directly. Your input helps shape the product.