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

# Contract Workspace

> Table, board, due-date, and task views over your contracts, with saved views and filters.

The contract workspace is the operational center of Deals — not just a ledger. It supports four
ways of looking at the same underlying contract set:

| Mode         | Use it for                                                                                                     |
| ------------ | -------------------------------------------------------------------------------------------------------------- |
| **Table**    | Scanning, sorting, and bulk actions across many contracts                                                      |
| **Board**    | Moving contracts across workflow stages, grouped by stage, owner, payment status, contract type, or due bucket |
| **Due-date** | Prioritizing what's coming due                                                                                 |
| **Task**     | Working through fulfillment tasks attached to contracts                                                        |

## Filtering and saved views

Every list is backed by `GET /contracts`, which accepts filters for type, status, payment state
(`unpaid` / `partial` / `paid`), owner, subject company, workflow stage, `overdue`, and
`dueSoon` — see [Contracts](/api-reference/contracts) for the full parameter list.

Filter and sort combinations can be saved as **saved views**, which are either team views
(governed by admins) or personal views (owned by the user who created them). See
[Saved Views](/api-reference/saved-views).

## Workflow stages

Each contract has a workflow stage, a lock state, allowed roles for advancing it, and a full
event trail. Board moves and explicit transitions write workflow events — approval, return,
signing, execution, completion, and archival are all explicit states, not just a free-text
status field. A locked contract blocks core-field edits until a role with sufficient
**workflow control** unlocks it — see [Roles & Permissions](/concepts/roles-and-permissions) and
the [Workflow API](/api-reference/workflow).

## Custom fields

Beyond the system fields required for reporting, tenant admins can define custom fields (text,
number, money, date, select, member, attachment, boolean, or formula), each with its own visible
and editable roles. Custom fields participate in forms, the contract detail view, table columns,
filters, import, export, and audit once defined. See
[Dynamic Fields](/api-reference/dynamic-fields).