# Document Classes, Metadata & Policies — Overview

## In this section

- [Document Classes](/products/namirialsignenterprise/namirialsignenterprise-knowledge-center/02-products-and-modules/01-nse/02-nse-settings/organization-document-classes)
- [Policies](/products/namirialsignenterprise/namirialsignenterprise-knowledge-center/02-products-and-modules/01-nse/02-nse-settings/organization-policies)


## Configuration (Organization Settings)

Before using document classification in the Designer, administrators must set up two building blocks in Organization Settings.

A **Document Class** is a named category for documents. Each class can carry any number of **Metadata fields** — structured attributes (e.g., a contract value or a department name) that describe the document's content. These fields can be marked as required, meaning they must be filled before any policy can be evaluated.

A **Policy** is then linked to a Document Class and defines what should happen when a document of that class carries specific metadata values. It is made up of **Conditions** — rules that compare metadata values against a defined threshold — and **Actions**, which list the recipients to add to the envelope when all conditions are met.

```
┌─────────────────────────────────────────────────────────────┐
│  DOCUMENT CLASS                                             │
│  ─────────────                                              │
│  Name          e.g. "Contract"                              │
│  Description   e.g. "All signed contracts"                  │
│                                                             │
│   ├── METADATA FIELD                                        │
│   │   ──────────────                                        │
│   │   Name        e.g. "contract_value"                     │
│   │   Data Type   String | Number                           │
│   │   Required    yes / no                                  │
│   │                                                         │
│   ├── METADATA FIELD                                        │
│   │   Name        e.g. "department"                         │
│   │   Data Type   String                                    │
│   │   Required    no                                        │
│   │                                                         │
│   └── ...                                                   │
└─────────────────────────────────────────────────────────────┘
                         │
                         │  linked to
                         ▼
┌─────────────────────────────────────────────────────────────┐
│  POLICY                                                     │
│  ──────                                                     │
│  Name            e.g. "High-value contract approval"        │
│  Document Class  → Contract                                 │
│  Enabled         yes / no                                   │
│                                                             │
│   ├── CONDITIONS  (AND logic — all must match)              │
│   │   ──────────                                            │
│   │   Metadata     contract_value                           │
│   │   Operator     greater than                             │
│   │   Value        1000                                     │
│   │                                                         │
│   │   Metadata     department                               │
│   │   Operator     equals                                   │
│   │   Value        "Finance"                                │
│   │                                                         │
│   └── ACTIONS  (recipients added when conditions match)     │
│       ───────                                               │
│       Add recipient      → individual (email, name, phone)  │
│       Add group          → predefined recipient group       │
│       Add from User Group→ from org user group              │
└─────────────────────────────────────────────────────────────┘
```

## In the Designer (Envelope)

Once the configuration is in place, the flow moves into the Designer where documents are uploaded, classified, and enriched with metadata. The sender assigns a Document Class to each uploaded file and fills in the associated metadata fields. When ready, **Apply Policies** evaluates all matching policies and automatically populates the envelope with the required recipients.

```
  [ Upload Document ]
          │
          ▼
  ┌───────────────────────────────────────────┐
  │  Apply Document Class dialog              │
  │  ─────────────────────────────────────    │
  │  Select class for each uploaded file      │
  └───────────────────────────────────────────┘
          │
          ▼
  ┌───────────────────────────────────────────┐
  │  Right panel — per document               │
  │  ─────────────────────────────────────    │
  │  Document Class    Contract               │
  │                                           │
  │  contract_value *  [ 2500         ]       │
  │  department        [ Finance      ]       │
  │                                           │
  │  * = required field                       │
  └───────────────────────────────────────────┘
          │
          ▼
  [ Other Actions → Apply Policies ]
          │
          ▼
  ┌───────────────────────────────────────────┐
  │  Policy evaluation                        │
  │  ─────────────────────────────────────    │
  │  For each document → find linked policies │
  │  Evaluate all conditions (AND)            │
  │                                           │
  │  ✔ All conditions match                   │
  │    → Recipients from Actions are added    │
  │                                           │
  │  ✘ One or more conditions not met         │
  │    → No recipients added for this policy  │
  └───────────────────────────────────────────┘
          │
          ▼
  [ Envelope with auto-populated recipients ]
```

## Operators by data type

```
  String  ──→  equals
  Number  ──→  equals | greater than | less than
```

## Key constraints

```
  Document Class ──── associated with a Policy?
    YES  →  cannot be deleted (remove policy link first)
    NO   →  can be deleted freely

  Apply Policies
    →  can be run multiple times (no duplicate recipients)
    →  requires all required metadata fields to be filled
```