> For the complete documentation index, see [llms.txt](https://guide.allibee.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.allibee.ai/en/clm/contract-copy/repository.md).

# Executed Contract Repository

### Viewing and Managing Executed Contracts

You can view all executed contracts and check detailed information for each one.

{% @arcade/embed flowId="k2j8k4Hp7THo1kVwKDzy" url="<https://app.arcade.software/share/k2j8k4Hp7THo1kVwKDzy>" %}

In the executed contract list, you can configure which fields to display using \[row/column].

* Turn columns on or off as needed to view only the information you want.
* Rearrange the column order by dragging and dropping.
* A total of 26 fields are available:\
  Contract Name / Contract Type / Contract Execution Date / Current Owning Department / Current Person in Charge / Language / Contract Status / Counterparty / Registration Date / Last Modified Date / Our Position / Contract Start Date / Contract Title / Contract End Date / Contract Amount / Currency / Note for Management / Created By / Initial Owning Department / Observer / Reference Department / Tag(label) / Governing Court / Method of Dispute Resolution / Governing Law / Main Clauses

From the executed contract list, you can select a contract to check details, edit information, or manage it.

* Click a contract to view its information.
* In the summary panel, you can edit the contract name or replace the executed file.
* Click \[Executed Contract Details] at the bottom to check the full text and key information.
* You can set notifications on executed contracts to send reminder emails for key dates, such as contract schedules.
* Select contracts from the list to download. If attachments are included, the executed contract and attachments are downloaded together in a ZIP file.

However, the available actions differ depending on how the contract was executed.

* Contracts executed with e-signature
  * Only download is available.
  * Editing contract information, replacing the executed file, or deleting is not allowed.
* Contracts uploaded manually
  * Editing contract information, replacing the executed file, downloading, and deleting are all available.

Executed contract data fields are displayed separately for registration and history management.

* Contract Manager / Owning Department and Created By / Initial Owning Department are distinguished, making them useful for operations and history tracking.
* You can also attach related documents for storage, and add tags (labels) to use them as search and filter conditions.
*

***

### Using Filter and Search

You can use filter and search functions to quickly find contracts that match specific conditions.

{% @arcade/embed flowId="73KSUgYghpM8jSTVQjeP" url="<https://app.arcade.software/share/73KSUgYghpM8jSTVQjeP>" %}

* When you set conditions with the filter, the list is filtered accordingly.
* A total of 16 filter fields are available:\
  Contract Status, Language, Contract Type, Our Position, Contract Execution Date, Contract Start Date, Contract End Date, Contract Amount, Currency, Current Person in Charge, Current Owning Department, Observer, Reference Department, Tag(label), Registration Date, Last Modified Date
* You can also search contracts by entering a keyword.&#x20;
* Filter and search functions can be used together.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guide.allibee.ai/en/clm/contract-copy/repository.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.