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

# Set up Orchestra for your lab

> A research workspace for an academic lab: papers written together in LaTeX, findings and failed experiments cited to the work behind them, and the AI use statement drawn from the record. How to get one, hosted or on your own computers, and what each shares.

A research workspace is an Orchestra workspace with the research features on:
papers written and compiled together, the lab's findings and failed
experiments each cited to the session, commit or run behind them, uploads and
their PDFs as sources, a citation check, and an AI use statement drafted from
the record for the authors to confirm. Everything else in Orchestra works as
usual.

## Get a research workspace

Research is turned on per workspace by Orchestra. Write to
[contact@orchestrahq.ai](mailto:contact@orchestrahq.ai) with your lab's name
and its Orchestra workspace (create one first at
[app.orchestrahq.ai](https://app.orchestrahq.ai) if you have none). Once it is on, **Settings** has a **Research** section that
lists what the workspace turns on, and **Papers** and **Findings** appear in
the sidebar.

## Hosted or Local

A lab can work in a hosted workspace, on Orchestra Local, or both. What
decides it is whether co-authors write papers together.

| | Hosted | Orchestra Local |
| - | - | - |
| Papers | Written together, live, by everyone with access. Compiled in Orchestra's cloud. | Stay on the computer they were written on. Co-authors on other computers cannot open them. Compiled on that computer. |
| Findings, decisions, failed experiments | Shared with the lab | Shared with the lab through your repository's git |
| Session transcripts | Private to each person until they share one | Stay on each person's computer until they share one |
| Uploads (PDFs, figures, data) | In the workspace's file store, as private as their project | On each person's computer |
| What to install | Nothing (the desktop app is optional) | The desktop app or the CLI on each computer |

**To write a paper together, use a hosted research workspace.** On Orchestra
Local, the Paper tab says that papers stay on that computer. Local suits work
that should never leave the lab's machines: each person's sessions,
experiments and drafts. A lab can do both: share findings through Local and
write its papers in the hosted workspace.

## Your first steps as the lab's lead

Setup asks only for the lab's name. Inviting your lab and bringing in
Overleaf are optional, and a research workspace has no GitHub, Linear or
repository step. **Getting started**, at the bottom left of the app, lists
what is left:

1. **Start a paper.** On **Papers**, a new lab names its first project (a
   paper lives in a project, and is as private as it), then starts the
   paper in it.
2. **Invite your lab** (below).
3. **Bring in Overleaf** (optional). A project on Overleaf comes in as a
   paper: keep it in sync with your own Overleaf Git token (Overleaf plans
   with Git), or import its source zip once (any plan). Each person connects
   their own Overleaf account.

Ask AI and the claims check run on Orchestra's keys, free for now, unless an
admin chooses the workspace's own in **Settings**, **Integrations**
([Model keys](https://docs.orchestrahq.ai/model-keys.md#orchestras-keys-or-your-own)). The paper agent always
runs on an Anthropic key of your own or the workspace's. Anyone can add their
own key, under **Your own keys**.

## Invite your lab

In **Settings**, **People**, enter each person's email address and choose
**Invite**. Each person signs up from the link in their email
([If you were invited](https://docs.orchestrahq.ai/getting-started.md#if-you-were-invited)). For Local, see
[Local teams](https://docs.orchestrahq.ai/local-teams.md).

To skip typing addresses, make an invite link under **Invite link** on the same
page and post it in your lab's chat. Whoever opens it signs in or creates an
account and joins as a member, until the link expires or you turn it off. See
[Invite links](https://docs.orchestrahq.ai/workspace-setup.md#invite-links).

## If you joined a lab

When you sign in for the first time, on the web or in the desktop app,
Orchestra welcomes you to your lab's workspace. There is nothing to configure:
whoever runs it already set it up. The welcome shows:

* **Your lab's papers and findings.** **Papers** lists every paper you can
  see. A paper is as private as its project, so if one you expect is
  missing, ask a co-author to add you to its project, or ask for access from
  the paper's link.
* **Whether AI will work for you.** Ask AI and the claims check run on
  Orchestra's keys, or on the workspace's own. The paper agent needs your own
  Anthropic key or the workspace's. You can save your own Anthropic key right there to have it
  billed to you; where the workspace runs on its own keys and has none, that
  is a step.
* **Your Overleaf papers** (optional). Keep a project in sync with your own
  Overleaf Git token, or import its source zip. To cite from your Zotero
  library, connect it in **Settings**, **Integrations**.

**Go to Papers** opens your lab's papers. The welcome shows once; this
section is always here.

When someone turns Orchestra on in a repository of a research workspace
(`orchestra enable`, or the desktop app's setup), they choose how much to
share, starting from the lab's defaults:

1. What they learn is shared with the lab: findings, decisions and failed
   experiments, each pointing to the session behind it. Their session
   transcripts stay on their computer until they share one.
2. Share session transcripts with the lab as well.
3. Share nothing from this repository.

Nobody can watch or steer someone's live session unless they allow it.

## Papers

Each project has a **Paper** tab, and **Papers** lists every paper you can
see. [Projects and teams](https://docs.orchestrahq.ai/projects-teams.md#papers-research-workspaces) covers
writing, versions, roles (can edit, can review, can view), comments and
suggestions, the References panel, Import from Overleaf, and compiling.

* **Bring your Overleaf papers in.** On **Papers**, choose **Import from
  Overleaf** in the header. Keep one project in sync with your Overleaf Git
  token, or import zips: one project's source zip, or every project at once
  from Overleaf's project list (tick them, then choose Download). Each
  becomes a paper, in one project or in a new project of its own. Steps and
  the file types that come in: [Import from Overleaf](https://docs.orchestrahq.ai/projects-teams.md#import-from-overleaf).

* On Orchestra Local, papers compile on your computer, inside a sandbox, with
  TeX Live 2025 that Orchestra installs: [Compile papers on your
  computer](https://docs.orchestrahq.ai/compile-papers-locally.md) says what macOS, Linux and Windows need.

* Your own Claude Code can read a paper, propose edits as suggestions and
  compile it: [Edit your paper with Claude Code](https://docs.orchestrahq.ai/edit-paper-with-claude-code.md).

* Ask AI, the paper agent and the claims check run on your own Anthropic key
  or the workspace's: [Model keys](https://docs.orchestrahq.ai/model-keys.md).

* The claims check also finds passages by meaning, so a claim worded
  differently from the cited paper is still matched. To do that, the citing
  sentence and the cited paper's passages are also sent to Orchestra's
  embedding provider, as well as to the model on your key. If that is not
  acceptable for a paper, do not run the claims check on it.

## A paper in a private project

A paper is as private as its project. In a private project, only the
project's people can open, edit or compile it, or read its PDF. Someone
outside it can ask for access from the paper's link. Its owners see the
request in their inbox and give access with the role they choose, and nobody
else is told the paper exists.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.