> ## Documentation Index
> Fetch the complete documentation index at: https://studio.assembly.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack community

The Assembly Studio Slack is the cohort space for everyone in the private beta. It's where you'll see what other firms are building, get answers from the Assembly Studio team, and share what's working for you.

It's small on purpose. Beta participants only.

## How to join

You should have received an invite when you joined the beta. If you didn't, or you lost it, email [studio@assembly.com](mailto:studio@assembly.com) and we'll send a new one.

## Channels

<AccordionGroup>
  <Accordion title="#start-here">
    Introductions. New cohort members post a quick hello — what your firm does, what you're hoping to build. Worth reading the recent posts as you onboard.
  </Accordion>

  <Accordion title="#announcements">
    Assembly Studio team updates. New features, known issues, scheduled maintenance, beta program updates. Read-only for cohort members.
  </Accordion>

  <Accordion title="#help">
    Questions of any size. A stuck build, a confusing error, a "is this supposed to work this way" — all welcome. The Assembly Studio team monitors, and other cohort members often chime in.
  </Accordion>

  <Accordion title="#feedback">
    Where to send product feedback that's bigger than a one-off issue. Feature requests, friction reports, things that worked surprisingly well. We read it all and it shapes what gets built next.
  </Accordion>

  <Accordion title="#built-with-assembly-studio">
    Show-and-tell. Post a screenshot or screen recording of something you've built. Inspire other cohort members and give us a window into the range of what people are making.
  </Accordion>

  <Accordion title="#general">
    Everything else. Industry conversation, off-topic chat, the things that don't fit anywhere else.
  </Accordion>
</AccordionGroup>

## Community norms

A short list of what makes this space useful:

<Check>
  Share what you're building. Even if it's rough.
</Check>

<Check>
  Ask questions early. Don't burn an hour on something a 30-second answer would unblock.
</Check>

<Check>
  Be specific. "Assembly Studio isn't working" is harder to help with than "the build froze on task 3 for my onboarding app."
</Check>

<Check>
  Help other cohort members where you can. You probably know something that would help someone else.
</Check>

## What to expect from the team

During the beta, the Assembly Studio team is actively in the Slack. Expect responses during business hours and a slower rhythm on evenings and weekends. For urgent issues outside Slack hours, email [studio@assembly.com](mailto:studio@assembly.com).
