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

# Legal

> Set up a Legal desk in Ravenna: contract review with real intake and triage, and policy questions answered from your own positions instead of one at a time.

Legal teams are small, and every request arrives as a DM that starts "quick question". The point of a Legal desk is not process for its own sake. It is that a two-person team cannot triage what it cannot see.

## What Legal owns in Ravenna

<CardGroup cols={2}>
  <Card title="Contract review" icon="file-signature" href="/guides/playbooks/legal/contract-review" horizontal>
    Intake that captures the deal, triage by risk, and signature as a tracked step.
  </Card>

  <Card title="Policy and compliance questions" icon="book-open-check" href="/guides/playbooks/legal/policy-and-compliance" horizontal>
    The recurring questions answered from your documented positions.
  </Card>
</CardGroup>

## Suggested shape

One workspace called **Legal**, with **Private workspace** on. Legal requests routinely name counterparties, deal values, and disputes, and none of that should be browsable by the company.

Keep the entry points deliberately narrow: a Slack channel for the internal teams that raise most requests, and the Portal for anyone else. Do not put a Legal inbound email address in front of external counsel until you have decided what happens to privileged material.

<Callout icon="link" color="#6B7280">Read [Portal and privacy](/guides/best-practices/portal-and-privacy) first. A private workspace still gates ticket visibility rather than hiding the workspace, and the difference matters here.</Callout>

## The two things that make a Legal desk work

**Intake that asks the questions you would have asked anyway.** Counterparty, contract type, value, deadline, and whether the counterparty's template or yours is on the table. A request with those five answers can be triaged in thirty seconds. Without them it takes two rounds of email.

**A real triage rule.** Most Legal requests are not review requests, they are questions. Separating those two lets the agent take the questions and leaves the review queue small enough to be credible.

## Categories worth having

Contract review, NDA, Policy question, Privacy and DPA, Dispute, Vendor terms, Employment. That list also becomes your reporting axis, which is how you make the case for a third lawyer.

## Signature

Ravenna has no native e-signature integration, but the [DocuSign OAuth walkthrough](/guides/how-to/foundry/setup-oauth/docusign) exists as a Foundry guide, which means sending an envelope can be a workflow action on the ticket rather than a separate manual step.

Build it after the intake and triage are working. A signature integration on a desk with no intake is automation pointed at the wrong problem.

## Where Legal desks stall

<AccordionGroup>
  <Accordion title="No intake form, so the desk is just a channel">
    The form is the entire value. Without it you have moved DMs to a different surface.
  </Accordion>

  <Accordion title="The agent answering legal questions freely">
    It should quote your documented positions and nothing else. Say so explicitly in the custom prompt.
  </Accordion>

  <Accordion title="A review request with no deadline">
    Legal work is prioritized by deadline more than by anything else. Make the date required.
  </Accordion>
</AccordionGroup>

## Next

<CardGroup cols={2}>
  <Card title="Contract review" icon="file-signature" href="/guides/playbooks/legal/contract-review" horizontal>
    Intake, triage, and signature.
  </Card>

  <Card title="Policy and compliance questions" icon="book-open-check" href="/guides/playbooks/legal/policy-and-compliance" horizontal>
    Stop answering the same question weekly.
  </Card>
</CardGroup>


## Related topics

- [Policy and compliance questions](/guides/playbooks/legal/policy-and-compliance.md)
- [Contract review](/guides/playbooks/legal/contract-review.md)
- [AI trust & privacy](/documentation/automate/agents/trust-privacy.md)
- [Playbooks](/guides/playbooks/overview.md)
- [RevOps and Sales Ops](/guides/playbooks/revops/overview.md)