> 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/getting-started/quick-reference-guide-for-verkada-command.md).

# Verkada Command 빠른 참조 가이드

Verkada Command 탐색에 도움이 되는 참조 링크

## 계정 설정

* [Verkada Command 시작하기](/command/ko/getting-started/get-started-with-verkada-command.md)
* [필수 네트워크 설정](/command/ko/need-help/required-network-settings.md)
* [Verkada Command 시스템 요구 사항](/command/ko/need-help/required-network-settings/verkada-command-system-requirements.md)
* [Verkada Command 계정 확인](/command/ko/security/authentication-overview/verify-your-verkada-command-account.md)
* [Command에서 조직 전환](/command/ko/security/authentication-overview/switch-organizations-in-command.md)

## 사용자 및 권한

* [Command의 역할 및 권한](/command/ko/users-and-permissions/roles-and-permissions-for-command.md)
* [역할 및 권한 사용자 지정](/command/ko/users-and-permissions/roles-and-permissions-for-command/customize-roles-and-permissions.md)
* [조직의 사용자 관리](/command/ko/users-and-permissions/manage-users-in-your-organization.md)
* [임시 사용자 관리](/command/ko/users-and-permissions/manage-users-in-your-organization/manage-temporary-users.md)
* [로그인 링크](/command/ko/security/authentication-overview/login-links.md)

## 조직 설정

* [관리자 페이지 설정 관리](/command/ko/organization-settings/manage-your-admin-page-settings.md)
* [감사 로그 관리 및 보기](/command/ko/organization-settings/manage-your-admin-page-settings/manage-and-view-audit-logs.md)
* [Feature Manager](/command/ko/organization-settings/manage-your-admin-page-settings/feature-manager.md)
* [파트너 설치 가이드](/command/ko/need-help/site-planner-homepage-overview/verkada-best-practice-partner-installation-guide.md)

## 인증

* [인증 개요](/command/ko/security/authentication-overview.md)
* [2단계 인증](/command/ko/security/authentication-overview/two-factor-authentication.md)
* [ID 공급자 개요](/command/ko/security/identity-providers.md)
* [Microsoft Entra ID](/command/ko/security/identity-providers/microsoft-entra-id.md)
* [Okta](/command/ko/security/identity-providers/okta.md)
* [SCIM 토큰 관리](/command/ko/security/identity-providers/scim-token-management.md)

## **데이터 보호 및 보안**

* [이미지 및 비디오 데이터의 기본 위치 또는 카메라별 위치 설정](/command/ko/security/privacy-and-security-disclosure/set-a-default-or-camera-specific-location-for-image-and-video-data-storage-and-processing.md)
* [개인정보 보호 및 보안 체크리스트](/command/ko/security/privacy-and-security-disclosure/privacy-and-security-checklist.md)
* [Verkada와의 데이터 공유 활성화](/command/ko/security/privacy-and-security-disclosure/enable-data-sharing-with-verkada.md)

## 문제 해결

* [Verkada 지원팀에 문의](/command/ko/need-help/contact-verkada-support.md)
* [지원 액세스 활성화](/command/ko/need-help/contact-verkada-support/enable-support-access.md)
* [브라우저 캐시 지우기](/command/ko/need-help/required-network-settings/clear-your-browser-cache.md)

{% hint style="info" %}
팔로우 [우리 블로그](https://www.verkada.com/blog/) 최신 기능과 공지 사항을 모두 확인하세요!
{% endhint %}


---

# 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://help.verkada.com/command/ko/getting-started/quick-reference-guide-for-verkada-command.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.