> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command/ko/licensing.md).

# 라이선스

- [라이선스 관리](https://help.verkada.com/command/ko/licensing/manage-your-licenses.md): Verkada Command에서 라이선스를 관리하는 방법 알아보기
- [라이선스 그룹](https://help.verkada.com/command/ko/licensing/manage-your-licenses/license-groups.md): Verkada Command에서 라이선스 그룹을 설정하고 관리하는 방법 알아보기
- [라이선스 키 찾기 및 추가](https://help.verkada.com/command/ko/licensing/manage-your-licenses/find-and-add-license-keys-to-command.md): 조직의 규정 준수를 유지하기 위해 Command에 라이선스 키 추가
- [라이선스 만료 계산](https://help.verkada.com/command/ko/licensing/manage-your-licenses/calculate-license-expiration-date.md): Verkada 공동 만료 라이선스가 계산되는 방식 알아보기
- [미사용 장치 삭제](https://help.verkada.com/command/ko/licensing/manage-your-licenses/delete-unused-devices-and-products.md): 라이선스 규정을 준수하려면 미사용 장치를 제거해야 합니다
- [제품 보증](https://help.verkada.com/command/ko/licensing/verkada-product-warranty.md): 모든 Verkada 제품의 제품 보증에 대해 알아보기


---

# 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://help.verkada.com/command/ko/licensing.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.
