> 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/clm/management/counterparty.md).

# 계약 상대방

계약을 자주 진행하는 상대방을 등록하고 관리할 수 있습니다.

### 계약 상대방 추가 <a href="#add" id="add"></a>

<figure><img src="https://851683292-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlYb8RCswvOdlgmdfACCT%2Fuploads%2F6fqOh1adENvxclc2UUIH%2FCLM-%EA%B3%84%EC%95%BD%20%EC%83%81%EB%8C%80%EB%B0%A9%20%EC%B6%94%EA%B0%80.png?alt=media&amp;token=b2366f74-7237-499c-a6e7-a0a6bc6eea1c" alt=""><figcaption></figcaption></figure>

* 계약 > 계약 상대방 정보 메뉴에서 \[+ 계약 상대방 추가] 버튼을 클릭합니다.
* 팝업이 실행되면 사업자 유형을 선택한 뒤  \[추가하기] 버튼을 클릭합니다.
* 계약 상대방에 대한 추가 정보를 기입한 뒤 \[추가하기] 버튼을 클릭합니다.

{% hint style="info" %}
계약 상대방 등록이 완료되면 계약 정보 입력 시, 상대방을 바로 불러올 수 있습니다.
{% endhint %}

***

## 계약 상대방 관리 <a href="#manage" id="manage"></a>

<figure><img src="https://851683292-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlYb8RCswvOdlgmdfACCT%2Fuploads%2FSQxbmN9aJt2LWDQj9472%2F%EA%B4%80%EB%A6%AC%EC%9E%90-%EA%B3%84%EC%95%BD%20%EC%83%81%EB%8C%80%EB%B0%A9%20%EA%B4%80%EB%A6%AC.png?alt=media&amp;token=fc034ca5-7416-47da-8719-f4668af83759" alt=""><figcaption></figcaption></figure>

* 등록된 계약 상대방의 정보를 수정하거나 삭제할 수 있습니다.
* 삭제된 내용은 복구할 수 없습니다.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guide.allibee.ai/clm/management/counterparty.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.