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

# Overview

> Bring a customer’s AI Acceptable Use Policy to life inside Longwave: four simple decisions that turn a written policy into rules the browser enforces.

A customer’s AI Acceptable Use Policy is usually a Word doc no one rereads.
Longwave makes it real. The **Policy** page inside any tenant has four tabs;
each is a single conversation you have with the customer.

<CardGroup cols={2}>
  <Card title="1. Access Control" icon="shield-check" href="/how-tos/create-an-ai-policy/access-control">
    Which AI app are people meant to use, which are off-limits, and what
    happens with everything else.
  </Card>

  <Card title="2. Data Protection" icon="lock" href="/how-tos/create-an-ai-policy/data-protection">
    Stop sensitive data and risky file uploads from leaving the browser.
  </Card>

  <Card title="3. Prompt Collection" icon="clipboard-list" href="/how-tos/create-an-ai-policy/prompt-collection">
    Keep the right evidence so you can prove the policy is doing its job.
  </Card>

  <Card title="4. Dialog Templates" icon="message-lines" href="/how-tos/create-an-ai-policy/dialog-templates">
    The in-browser experience users see, in the customer’s voice.
  </Card>
</CardGroup>

## How to use this with the customer

Walk the four pages above in order. Each one is short and decision-led, so it
maps cleanly to a working session:

1. Agree the **approved AI app** they’ve licensed (or pick one to license).
2. Agree the **hard blocks** and what happens for everything else.
3. Agree what counts as **sensitive data** and what to do about it.
4. Agree what gets **retained for audit**.
5. Brand the **end-user dialogs** so they read as the customer’s policy, not a
   vendor message.

When you’re done, the customer’s policy isn’t just written down. It’s running.

<Info>
  Set this up on the pilot group first, confirm the experience matches what
  you agreed, then roll out tenant-wide.
</Info>

## What the customer gets back

Once the policy is enforcing, the value shows up in two places:

* **In-browser:** users see the customer’s AUP at the moment it’s relevant,
  with a clear path to the approved tool.
* **In review:** the **Audit Log** and **Reports → Overview** become the
  artifact you walk through together. See [Client
  reporting](/how-tos/client-reporting/overview).