# Domain Verification

https://docs.wisecp.com/es/domain-verification

Review the information and documents a customer sent for a domain and record an approve or reject decision with a reason the customer can read, so no registration waits on a document nobody looked at.

## Opening the Screen

Open a domain service from **Orders › Services** and select the **Verification** tab: `{admin}/services/detail?id={service}&content=verification`

The tab is built only for domain services. Hosting, server, software and other types get a **Management** tab in that position, so there it does not exist.

A red counter beside the **Verification** label counts submissions awaiting a decision. It is drawn while the page is built, so it reflects your decisions the next time the service detail is loaded rather than the moment you save. The list itself loads when you first open the tab.

## What Is on the Screen

The tab is one form with three stacked sections and a single **Save Changes** button at the bottom right that saves all three in one request.

- **Client's Submitted Information/Documents**: One row per document, with what was sent and the decision controls.
- **Operator Document Fields**: Extra field definitions recorded on this one service, alongside what the extension already asks for.
- **Operator Note**: A note stored on the service and shown on the customer's verification window.

### Submitted Information and Documents

Three columns, no paging. With nothing requested and nothing sent, the empty state **No data available yet.** takes its place.

| Column | What it shows | With no submission |
| --- | --- | --- |
| Info/Document Name | The requested name in the panel language, shortened when long, full text on hover. | Still listed, so you see what is missing. |
| Data | Text answers in a light box. Files as a card: preview or icon, the file name, extension and size, plus **View** and **Download**. | A dash. |
| Status | The **Approve** and **Reject** pair, current decision highlighted. | A plain **Not sent** badge, no buttons. |

**View** opens the file in a new tab and **Download** saves it; both go through the panel and check your privilege first. A rejected document that is sent again adds a second record, so one name can appear twice; the customer reads the newest, so the decision that counts is the one on the newest row.

### Where the Rows Come From

Three origins feed the list, merged so a required document is visible before anything arrives. **Service provider fields** come from the provider module for that extension and cannot be edited here. **Extension documents** are the ones you defined yourself, in your sort order; only active entries are requested. **Submissions with no definition** match nothing current but stay listed so an existing decision is never hidden. That extension list lives under **Products › Domains** and applies to every domain of the extension.

### Review Controls

**Reject** opens a panel under the row: a picker of saved rejection texts, a floppy disk button with the tooltip **Save as template**, a bin button with the tooltip **Delete template**, and the reason box with the placeholder **Additional rejection reason (Optional)**.

Choosing an entry from **Select saved reason...** copies its text into the box and enables the bin button, otherwise disabled. Selecting **Approve** afterwards closes the panel and clears the box.

### Operator Document Fields

**Add Field** appends a row with **Field Name**, **Type** and a red cross that removes it. **Type** offers **Text** and **File**; **File** reveals **Allowed Extensions** and **Max File Size (MB)** in the same row.

The definitions are stored on the service record, so they belong to this one domain rather than to the extension. Removing every row clears them.

Read them as a note to yourself about what is still missing, not as a request the customer will see. The customer's verification form is assembled from the extension's own document list and the provider module's fields; a row added here is saved and read back on this tab, but it does not appear on that form, so ask for the document through a ticket or by rejecting the related row with a reason.

### Operator Note

The note carries the same three controls, here labelled **Select saved note...**, plus the box with the placeholder **Add a note about this verification...**. A red strip above it repeats the rule: **If you reject a document, you must provide a reason. This reason will be visible to the client.**

The customer's verification window reads it, so it suits a sentence about the whole submission; clearing the box and saving removes it.

## Fields

- **Operator Note**: Optional, no default. Shown to the customer; saving an empty box removes it.
- **Select saved note...**: Optional picker. Copies the chosen text into the note box; a shortcut, not a value.
- **Approve / Reject**: One decision per submitted row, no default. An untouched row keeps its status.
- **Additional rejection reason (Optional)**: Free text of the row, stored with the document and shown to the customer.
- **Field Name**: Required, or the row is silently dropped on save. It labels the definition on this tab only.
- **Type**: Text by default. File turns the row into an upload; anything else falls back to Text.
- **Allowed Extensions**: File type only, no default. A comma separated list, as the placeholder shows.
- **Max File Size (MB)**: File type only, no default. Stored as a whole number of megabytes.

## Tasks

### Approving a Document

1. Open the tab, read the row's **Data** column and, for a file, use **View** or **Download**.
2. In that row's **Status** column press **Approve**; it becomes the highlighted button.
3. Press **Save Changes** at the bottom. The customer sees the document as verified; the tab counter only drops the next time the service detail page is loaded.

### Rejecting a Document

1. In the row's **Status** column press **Reject**; the reason panel opens under the buttons.
2. Pick a text from **Select saved reason...** or write your own in **Additional rejection reason (Optional)**; the customer reads it.
3. Press **Save Changes**. The row is stored as rejected with your reason and the customer can send that one document again.

### Managing Saved Texts

1. Write the text you want to keep, in a row's reason box or in the **Operator Note** box.
2. Press the floppy disk button beside it, tooltip **Save as template**; the text joins every picker on the tab.
3. To remove one, select it in a picker and press the bin button, tooltip **Delete template**. Texts already saved on a document are untouched.

### Defining an Extra Field

1. Go to **Operator Document Fields** and press **Add Field**; an empty row appears.
2. Fill in **Field Name** and choose **Type**. For **File**, also fill in **Allowed Extensions** and **Max File Size (MB)**.
3. Press **Save Changes**. The definitions are stored on this service record and read back the next time the tab opens; they are not added to the customer's verification form.

### Writing an Operator Note

1. In the **Operator Note** section pick a text from **Select saved note...** or type into the box.
2. Press **Save Changes**. The note appears on the customer's verification window and a line goes to the activity log.
3. To withdraw it later, clear the box and save again.

## Things to Watch

> **A rejection reason is written for the customer**
> 
> It appears beside the rejected item in the client area, so it is a message, not an internal note. Rejecting is also the only way to reopen a document: approved and pending submissions are locked.

> **Approving sends nothing to the service provider**
> 
> The decision is recorded in this installation only. Nothing leaves for the registry or the service provider from this tab, and the domain's own state is not advanced by it.

> **Saved texts are shared by the whole installation**
> 
> Rejection reasons and operator notes go into one list. A text saved on one domain appears in every operator's pickers on every domain, and deleting one removes it everywhere, so keep entries free of customer details.

## Required Privileges

Reading this tab and opening or downloading a document needs `SERVICES_LOOK`. Saving the form and adding or removing a saved text need `SERVICES_OPERATION`.

## Related Articles

- [Service Detail Overview](https://docs.wisecp.com/en/service-detail-overview)
- [Service Details](https://docs.wisecp.com/en/service-details)
- [Domain Documentation Management](https://docs.wisecp.com/en/domain-documentation-management)
- [Domain Extensions and Pricing](https://docs.wisecp.com/en/domain-extensions-and-pricing)
- [Activity Logs](https://docs.wisecp.com/en/action-logs)
