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

# Studio overview

> Studio is your organization's document library — upload, organize, generate, and chat with the documents your motions send and your customer portal serves.

Studio is the single home for every document your organization works with: files you upload, text you paste, imports from Google Drive, and the branded documents and decks you generate with AI. It's what the rest of Thread draws on — when a motion email play attaches a document, it comes from Studio; when a customer opens a document link in their portal, it resolves to a Studio asset; when an agent needs a reference document, it's picked from Studio.

Studio is available to **every member** of your org — it isn't gated to admins. Open it from **Studio** in the sidebar.

## What lives in Studio

The main view is **All Documents**: a searchable, filterable list of every asset in the library, with a category filter (Onboarding, Training, Compliance, Marketing, Sales, Security, Other) and a type filter (Deck / Document). Assets arrive four ways:

* **Uploads** — PDF, Word, Excel, PowerPoint, images, and plain text, up to 50 MB per file.
* **Pasted text** — paste Markdown, CSV, JSON, or plain text directly (up to 500 KB); these show a "Pasted text" badge and can be wired into agents like any file.
* **Google Drive imports** — when Google is connected, a **Google Drive** button opens a browser over My Drive, Shared with me, Starred, and Recent. Import up to 50 files at once; Google-native files are converted on import.
* **Generated assets** — documents and decks created with the **Create** button. See [Documents and decks](/studio/documents-and-decks).

Each asset supports **Preview** (with an AI Summary panel you can generate on demand), **Edit details** (rename, description, category), **Add to Packet**, and **Archive**. Generated assets also get **Edit in Studio**, which reopens them in the generator.

<Note>
  Archiving is a soft remove — there is no hard delete from the Studio UI. Archived assets drop out
  of the library and out of pickers.
</Note>

## Packets: folders built for sharing

A **packet** is a named, ordered collection of documents — an "Enterprise Security Pack," a kickoff bundle, a training set. Create one from the **Packets** section in the Studio sidebar, then drag documents onto it or use **Add to Packet** from a document's menu.

Two things make packets more useful than plain folders:

* **Documents are added, not moved.** The same document can live in as many packets as you like, and stays in All Documents.
* **Packets are a sharing unit.** From an account page, **Apply Packet** shares every document in the packet with that account — they appear in the customer's portal immediately. A packet's documents can also be pinned to a motion stage as portal resources.

## Chat with your documents

The **Chat** button in the Studio header opens a side panel where you can ask questions across your library — "What does the SOW say about deliverables?", "Summarize the onboarding timeline." Answers stream in with citations; clicking a citation opens the document preview at the cited page.

<Note>
  Chat always searches your whole library, even while you're viewing a single packet.
</Note>

## SOW templates

Under **Templates → SOW Templates**, org admins can upload your organization's standard Statement of Work (PDF, Word, or text) and mark one as the default. Thread uses the default standard SOW for automatic comparison against the SOWs on your customer accounts. Non-admins can view the templates and chat over them but can't upload or change the default.

## Where Studio assets go

Studio is the supply side for every customer-facing document surface:

<CardGroup cols={2}>
  <Card title="Motion email plays" icon="envelope" href="/motions/email-plays">
    The email editor's Attach picker searches Studio directly, and files uploaded there are saved
    back into Studio for reuse. Each attachment can ride as a portal link or as a file.
  </Card>

  <Card title="Customer portal" icon="window" href="/customer-portal/documents">
    Portal document links, applied packets, and stage-pinned resources all resolve to Studio
    assets — customers see them under your brand.
  </Card>

  <Card title="Agents and guides" icon="user-astronaut" href="/motions/agents">
    Agent reference documents, guide knowledge, and Voice Studio knowledge are all picked from the
    same library, so there's one source of truth.
  </Card>

  <Card title="Documents and decks" icon="wand-magic-sparkles" href="/studio/documents-and-decks">
    Generate branded, co-branded documents and 16:9 decks and save them straight into the library.
  </Card>
</CardGroup>