> ## Documentation Index
> Fetch the complete documentation index at: https://docs.royaltyport.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Views
> Create and manage custom views for your contracts
## Overview
Views control how contracts are displayed in the Drive. Use built-in views for quick access, or create custom views with specific columns and fields tailored to your workflow.
## Built-in Views
Two built-in views are always available:
| View | Description |
| -------------- | --------------------------------------- |
| **Card View** | Visual cards showing contract summaries |
| **Table View** | Basic spreadsheet-style table |
Built-in views cannot be customized or deleted.
### Table View Columns
The Table View includes the following fixed columns:
| Column | Description |
| -------------- | ----------------------------------------------------------------------------------------- |
| **Contract** | File name and contract type |
| **Assets** | Linked recordings, compositions, or products |
| **Duplicates** | Number of detected duplicate contracts (click to see which ones) |
| **Missing** | Number of expected content items not found in the contract (click to see what is missing) |
| **Created** | Upload date |
| **Actions** | Per-contract actions menu |
### Card View
Each card displays the contract name, type, status, linked assets, and any **Duplicates** or **Missing** indicators alongside action buttons.
## Custom Views
Custom views let you create table layouts with the exact columns and fields you need.
### Creating a Custom View
1. Click the **View** dropdown in the toolbar
2. Click **Add view\...** at the bottom
3. Enter a name for your view
4. Configure columns in the Editor tab (or start from a Template)
5. Click **Save**
### Accessing Custom Views
Your saved custom views appear in the View dropdown below the built-in views. Click any view to apply it.
***
## View Editor
When editing a custom view, you'll see two tabs:
### Editor Tab
The main workspace for building your view. Here you:
* Add, remove, and reorder columns
* Configure fields within each column
* Adjust column design settings
### Templates Tab
Pre-configured column layouts for common use cases. Select a template to quickly populate your view with relevant columns.
***
## Working with Columns
Columns are the building blocks of custom views. Each column can contain one or more fields.
### Adding a Column
Click the **+ Add Column** button at the bottom of the Editor tab. A new column named "New Column" is created.
### Column Controls
Each column has controls in its header:
| Control | Function |
| ----------------- | ------------------------------------- |
| **Toggle switch** | Enable/disable the column in the view |
| **Up arrow** | Move column left (reorder) |
| **Down arrow** | Move column right (reorder) |
| **X button** | Remove the column |
### Reordering Columns
Use the **up** and **down arrow buttons** on each column to change the display order. Columns at the top of the list appear on the left side of the table.
### Renaming a Column
Click the **edit icon** next to the column name to rename it. Press Enter to save or Escape to cancel.
***
## Column Configuration
Expand a column to access its configuration. Each column has two tabs:
### Column Fields Tab
Configure which data fields appear in the column.
**Adding a field:**
1. Use the **Select field** dropdown at the bottom
2. Choose a field from File Fields, System Fields, or Custom Fields
3. Click **+ Field** to add it
**Field options:**
Each field can be expanded to configure its display settings. Options vary by field type but may include:
* Display type (text, count, badges)
* Which properties to show
* Filtering options
**Removing a field:**
Click the X button on any field to remove it from the column.
### Column Design Tab
Control the visual appearance of the column.
**Column Size:**
| Size | Description |
| ---------- | ------------------------ |
| **Auto** | Width adjusts to content |
| **Small** | Fixed narrow width |
| **Medium** | Fixed medium width |
| **Large** | Fixed wide width |
**Column Layout:**
| Layout | Description |
| -------------- | --------------------------- |
| **Vertical** | Fields stack vertically |
| **Horizontal** | Fields display side by side |
The Design tab includes a preview showing how your column will appear.
***
## Available Fields
Fields are organized into categories:
### File Fields
Basic information about the uploaded file:
| Field | Description |
| ------------------ | ------------------------- |
| **File Name** | Name of the uploaded PDF |
| **File Extension** | File type (typically pdf) |
| **File Date** | Upload date |
### System Fields
Extracted contract data:
| Field | Description |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Language** | Contract language |
| **Type** | Contract classification |
| **Entities** | Related parties |
| **Compensation** | Advances and payment terms |
| **Accounting Period** | Accounting and payment cycles |
| **Relations** | Related contracts |
| **Compositions** | Linked compositions |
| **Recordings** | Linked recordings |
| **Royalties** | Royalty rules |
| **Costs** | Cost deductions |
| **Splits** | Revenue splits |
| **Signatures** | Signatories |
| **Control Areas** | Rights and territories |
| **Dates** | Key dates and terms |
| **Tags** | Applied tags |
| **Commitments** | Contractual obligations |
| **Duplicates** | Contracts detected as duplicates of this one |
| **Missing Content** | Referenced content (appendices, amendments, exhibits, etc.) not found in the contract |
| **Entity Artists** | Artists linked to the contract's parties, showing artist name and the entity they belong to |
| **Entity Writers** | Writers linked to the contract's parties, showing writer name and the entity they belong to |
| **Recording Artists** | Artists credited on recordings referenced in the contract, showing artist name and associated recording titles |
| **Composition Writers** | Writers credited on compositions referenced in the contract, showing writer name and associated composition titles |
**Duplicates field options:**
* **Field Layout** — display as a **count** (number badge) or **text** (list of duplicate file names)
When you click a duplicate indicator to inspect the list, each duplicate card shows when it was auto-merged. If AI reasoning is available for why the contracts were identified as duplicates, it appears below the merge date — click **Read more** to expand the full explanation.
**Missing Content field options:**
* **Field Layout** — display as a **count** (number badge) or **text** (list of missing items with their type and identifier)
* **Filter by Type** — restrict which content types are shown: External Document, Appendix, Schedule, Exhibit, Amendment, Addendum, or Missing Pages
**Entity Artists field options:**
* **Field Layout** — display as a **count** (number badge) or **text** (artist names with their entity in parentheses)
* **Filter by Entity Role** — restrict to Assignee or Assignor entities only
**Entity Writers field options:**
* **Field Layout** — display as a **count** (number badge) or **text** (writer names with their entity in parentheses)
* **Filter by Entity Role** — restrict to Assignee or Assignor entities only
**Recording Artists field options:**
* **Field Layout** — display as a **count** (number badge) or **text** (artist names with associated recording titles)
* **Filter by Creator Role** — restrict to specific roles: Main Artist, Featured Artist, Producer, Remixer, Writer, Composer, Lyricist, Vocalist, or Other
**Composition Writers field options:**
* **Field Layout** — display as a **count** (number badge) or **text** (writer names with associated composition titles)
* **Filter by Creator Role** — restrict to specific roles: Main Artist, Featured Artist, Producer, Remixer, Writer, Composer, Lyricist, Vocalist, or Other
**Royalties field options:**
* **Field Layout** — display as a **count** (number badge) or **text** (formatted royalty rules)
* **Rate Source** — filter which rates are included. Select **Main Rates**, **Third Party Rates**, or both. Leave blank to show all.
* **Rule Type** — filter by rule type. Select any combination of **Base Rate**, **Modifier**, or **Exception**. Leave blank to show all.
**Costs field options:**
* **Field Layout** — display as a **count** (number badge) or **text** (formatted cost deductions)
* **Cost Source** — filter which costs are included. Select **Main Costs**, **Third Party Costs**, or both. Leave blank to show all.
### Categorized Fields
Flattened versions of complex extractions, displaying data in a more detailed format:
| Field | Description |
| ------------------------------- | --------------------------------------------- |
| **Royalties (categorised)** | Royalty rules by rights type and revenue type |
| **Costs (categorised)** | Cost deductions by category |
| **Recordings (categorised)** | Recording details with metadata |
| **Dates (categorised)** | All dates with their types |
| **Control Areas (categorised)** | Rights breakdown by type |
Categorized fields are useful when you need to see detailed breakdowns in your view rather than just counts or summaries.
### Quality Fields
Fields that surface contract quality signals detected during processing:
| Field | Description | Display Options |
| ------------------- | ------------------------------------------------------- | ----------------------------------------------------------------------- |
| **Duplicates** | Contracts identified as duplicates of this one | **Count** — shows a number badge; **Text** — lists duplicate file names |
| **Missing Content** | Expected attachments or pages not found in the contract | **Count** — shows a number badge; **Text** — lists what is missing |
**Duplicates field options:**
* **Field Layout** — choose **Count** (a number badge) or **Text** (a list of duplicate contract names)
Clicking a duplicate indicator opens a panel listing each duplicate. Each entry shows the merge date and, when available, the AI reasoning behind the match — click **Read more** to see the full explanation.
**Missing Content field options:**
* **Field Layout** — choose **Count** or **Text**
* **Filter by Type** — narrow which missing content types are shown. Available types:
| Type | Description |
| ----------------- | ------------------------------------------ |
| External Document | Referenced external documents not uploaded |
| Appendix | Missing appendices |
| Schedule | Missing schedules |
| Exhibit | Missing exhibits |
| Amendment | Missing amendments |
| Addendum | Missing addenda |
| Missing Pages | Detected page gaps within the contract |
Use the **Missing Content** field with **Filter by Type** set to "Amendment" or "Addendum" to quickly flag contracts that reference changes not yet uploaded to the Drive.
### Custom Extractor Fields
If you've created [custom extractors](/projects/contracts/drive/custom-extractors), they appear as available fields. Only active extractors are shown.
***
## Templates
Templates provide pre-configured column layouts for common use cases.
### Using a Template
1. Open the view editor
2. Click the **Templates** tab
3. Browse available templates
4. Click a template to apply it
Applying a template replaces all current columns. You'll be prompted to confirm if you have existing columns.
### Available Templates
Templates are designed for specific workflows like:
* Recording deal overview
* Publishing deal overview
* Financial terms focus
* Expiration tracking
***
## Managing Views
### Renaming a View
1. Open the view in the editor
2. Click the **edit icon** next to the view name in the header
3. Enter the new name
4. Click **Save**
### Deleting a View
1. Open the view in the editor
2. Click the **Delete** button at the bottom left
3. Confirm the deletion
Deleting a view cannot be undone. Built-in views (Card View, Table View) cannot be deleted.
***
## View Sharing
Custom views are **shared at the project level**. This means:
| Aspect | Behavior |
| -------------- | --------------------------------------------- |
| **Visibility** | All project members see the same custom views |
| **Creation** | Any project member can create new views |
| **Editing** | Any project member can edit existing views |
| **Deletion** | Any project member can delete views |
Views are not personal or private. When you create or modify a view, all team members with access to the project will see those changes.
### Implications for Teams
* **Coordinate with your team** before deleting or significantly changing shared views
* **Use clear naming conventions** so team members understand each view's purpose
* **Consider creating role-specific views** (e.g., "Finance Review", "Legal Compliance") that different team members can use
***
## Best Practices
Build views that match how you work - one for reviewing new contracts, one for tracking expirations, one for financial analysis.
Name views clearly so you can quickly find them: "Expiring Q1 2025" or "Sony Recording Deals".
Templates provide a good starting point - customize from there rather than building from scratch.
Too many fields in one column can be hard to read. Split related data across multiple columns.
When you need to see the full breakdown of royalties, costs, or dates, use the categorized versions instead of the summary fields.
Since all project members share the same views, communicate before making significant changes or deleting views others might rely on.
***
## Related Documentation
Filter contracts within any view.
Export view data to CSV or Excel.