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

# Add and publish a document

> Upload a PDF or Word document, import from Google Drive or OneDrive, or write in ClearPolicy. Choose whether people need to sign.

Add a document before you send requests or make it available to read. A published revision is required for both.

**Who can do this:** owners and administrators.

## Upload a PDF or Word document

1. Open **Documents** and click **Add Document**.
2. Drop a file or choose one from your computer. PDF, `.doc`, and `.docx` files are supported, up to **25 MB**.
3. Check the document name.
4. Leave **Requires a signature** on if people need to sign. Turn it off if they only need to read.
5. Submit the form.

ClearPolicy converts Word files to PDF and publishes the first revision. Open **Revisions** to review the published file before sending it.

## Import from Google Drive or OneDrive

In **Add Document**, click **More options**, then choose **Pick from Google Drive** or **Pick from OneDrive**. Connect the service if prompted, select a supported file, check the name and signature setting, then submit.

Like a local upload, a new cloud import is published when added. Imports are copies: later changes in Drive or OneDrive do not automatically update ClearPolicy.

See [Google Drive import](/integrations/google) or [OneDrive import](/integrations/microsoft) for supported types and connection help.

## Write in ClearPolicy

1. In **Add Document → More options**, choose **Write in ClearPolicy**.
2. Enter a name and choose whether the document requires a signature.
3. Submit to open the draft editor.
4. Write and format your document, then use **Save Draft** while it is in progress.
5. Click **Publish** when it is ready.

Drafts are not visible to people and cannot be sent for signature.

## Choose what happens next

| Your goal | Next step |
| - | - |
| Ask people to sign | [Send a document request](/guides/send-requests). Publishing alone does not send it. |
| Let people read without signing | [Add the published document to a group](/guides/read-documents) with **Requires a signature** off. |
| Change published content | [Add a new revision](/guides/update-document). |
| Ask people to sign again periodically | [Set up renewal](/guides/renewals). |

## Find document settings and history

Use **Settings** for the document name, signature requirement, groups, renewal, and archive actions. Use **Revisions** for content, published versions, and downloads.

Documents requiring a signature open on **Compliance**. Documents available to read open on **Revisions** when there is no signature history. See [documents and revisions](/concepts/documents).


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