> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://docs2.emma.legal/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Info tab

The **Info** tab is the default tab when you open the document viewer. It shows everything Emma knows about the file beyond risks and key terms — metadata, AI-generated summary, categorization, signature status, bundle membership, and duplicate warnings.

For the overall viewer layout, see **Document viewer overview**.

# Document name and source

At the top of the Info tab you see the document's **display name** with a file-type icon.

* **Hover** the name to see a tooltip with:

* **Source** — the integration or "Manual Upload" where the file came from
* **Folder path** — the full path in the data room
* **Uploaded** — date and time the file was added to Emma
* **Edit** — click to rename the display name (up to 180 characters). The original filename is preserved; the display name is what appears in lists, the Matrix, and reports. Other team members see a presence indicator if someone else is editing the name at the same time.

# Document types

The **Document types** section shows every IRL document type the file is assigned to. Each entry displays the area number and name, document type number and name, and a status badge when the AI was unsure.

**To change categorization:**

1. Click the document type field to open the type selector
2. Search for and select the correct type
3. Save — Emma re-runs relevant extraction for the new type

You can assign multiple document types to one file when it genuinely belongs in more than one category. See also [Categorize a single document](https://docs.emma.legal/en/articles/11706586-categorize-a-single-document).

If the AI flagged **unsure categorization**, a warning appears here and in the file list. Use the **Review duplicates** flow (below) to open a consolidated warning dialog.

# Summary

The **Summary** section contains an AI-generated overview of the document's content and purpose.

* Click the summary text to edit it inline with a rich markdown editor
* Changes save automatically and appear in the Matrix Info tab and exports
* A presence badge shows if another reviewer is editing the summary simultaneously

Summaries are especially useful in the Matrix, where a short version appears under the file name in the Info tab.

# Possible duplicates

When Emma detects files that may be duplicates of the current document, a **Possible duplicates** section lists them with upload timestamps.

* Click a duplicate name to open that file in the viewer
* Click **Review duplicates** to open a warning dialog that summarises all issues: unsure categorization, processing errors, and duplicate files

Exact content duplicates and same-filename matches are both surfaced. Resolving duplicates early prevents double-counting in risk analysis and reports.

# Jurisdiction

The **Jurisdiction** field shows the governing law or jurisdiction Emma extracted from the document.

* Click the combobox to search and select a jurisdiction from your organisation's list
* Changes apply immediately and update the Matrix, filters, and exports
* If Emma did not extract a jurisdiction, the field is empty until you set one manually

# Legal entities

The **Legal entities** section lists companies or parties identified in the document.

* Use the multi-select combobox to add or remove entities
* Entities are shared across the data room — type to search existing ones or create new entries
* Legal entity tags power filtering on the Documents page and grouping in the Matrix

# Signature review

The **Signature review** section now always appears, even if no signature pages or expected signatures are detected.

* If Emma detects signature pages or estimates an expected signature count, this information is shown in the section.
* If no signature pages are found, a message states "No signature pages detected."
* The action to mark the document as fully signed or unsigned is available whenever signature information is present—including when there are signature bounding boxes, expected signature count, or a previous confirmation of signing.

| Element | Description |
| --- | --- |
| Expected signatures | AI-estimated number of required signatories. If none are expected, you will see 'No expected signatures'. |
| Page navigation | Previous / next buttons jump between pages containing detected signature areas. If none are found, a message 'No signature pages detected' is shown. |
| Mark as fully signed | Toggle to record that all required signatures are present, or to mark as unsigned. This appears if signature pages or expected signatures exist, or if a fully signed timestamp has been set. |

* If there are no pages with detected signature areas, a message 'No signature pages detected' will be shown instead of navigation buttons.
* If the expected signature count is zero, it displays 'No expected signatures'.
* If either signature pages exist, or there is a non-zero expected signature count, or the document is already marked fully signed, the **Mark as fully signed** button appears. Otherwise, it is hidden.

Clicking a signature navigation button scrolls the PDF to that page and clears any other selection highlights so you can inspect the signature area clearly.

When marked fully signed, the toggle shows who confirmed it and when. Click again to mark as unsigned if needed.

Signature bounding boxes appear as detections on the PDF — use them alongside the page navigation to verify execution status during due diligence.

# Bundle

The **Bundle** section manages groups of a main document and its annexes reviewed as one package.

## Suggested bundles and missing documents

When Emma identifies a likely relationship between a main agreement and an annex or addendum, the Bundle section shows a **Suggested bundle** row. Click **Review** to check the proposed relationship before creating the bundle, or **Dismiss** to remove the suggestion.

Emma can also flag a **Missing** related document when:

* a document explicitly references an annex that cannot be found in the data room; or
* a likely annex or addendum has no viable main agreement.

When Emma can locate the reference in the PDF, use **View** to jump directly to the highlighted text. Dismiss the finding if the related document is contained within the same file, is intentionally absent, or the reference is not relevant.

Emma never creates a bundle automatically. Creating or editing a bundle remains a user decision because it changes how files are reviewed and analyzed.

**When the file is not in a bundle:**

* Click **New bundle** to create a bundle with this file as the main document, or **Attach** to add it as an annex to an existing bundle

**When the file is the main document:**

* See all annexes listed with drag-to-reorder support
* Add or remove annexes
* Swap which file is the main document
* Delete the entire bundle

**When the file is an annex:**

* See which main document it belongs to
* Remove it from the bundle

When all files in a bundle are PDFs, opening the main document merges them into a single scrollable view in the file panel. See **PDF viewer — Disclosure bundles**.

# Processing status

If the document has not finished processing, sections that depend on AI output (risks, key terms) show loading states or warnings in their respective tabs. The Info tab remains usable for manual metadata edits throughout processing.

A blue progress banner below the sidebar header shows the current pipeline step (for example "Extracting text", "Running checks") while processing is active.

# Actions available from the sidebar header

While on any tab, the sidebar header provides:

* **Approve** — mark the document reviewed; see **Document viewer overview**
* **Actions menu** — add to or remove from the disclosure schedule (when enabled for your organisation)
* **Close** — exit the viewer

# Typical Info tab workflow

1. Confirm the **document type** is correct — fix it immediately if the AI miscategorised
2. Read the **summary** and edit if the AI missed nuance
3. Set **jurisdiction** and **legal entities** if missing or wrong
4. Check **duplicates** and resolve any unintended copies
5. For contracts, use **Signature review** to verify execution
6. Group related files in a **Bundle** before reviewing annexes together
7. Click **Approve** when metadata review is complete, then move to the Risks tab

If you need additional help with the Info tab or encounter any other problem, don't hesitate to reach out through the chat bubble in the bottom right or contact [[email protected]](/cdn-cgi/l/email-protection#c5b6b0b5b5aab7b185a0a8a8a4eba9a0a2a4a9).