> 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-connector/ko/configuration/change-a-non-verkada-channel-orientation.md).

# Verkada가 아닌 채널 방향 변경하기

Verkada가 아닌 채널 카메라 뷰 회전하기

때때로 Verkada가 아닌 카메라 피드는 잘못된 방향으로 표시될 수 있습니다. Command Connector를 사용하면 Command에서 직접 이러한 피드를 쉽게 회전시켜 올바른 정렬을 유지하고 가시성을 높일 수 있습니다.

***

## 구성

{% stepper %}
{% step %}
**Verkada Command에서 모든 제품 > 카메라로 이동합니다.**
{% endstep %}

{% step %}
**구성하려는 Verkada가 아닌 채널을 선택합니다.**
{% endstep %}

{% step %}
**오른쪽 아래에서 설정을 클릭합니다.**
{% endstep %}

{% step %}
**장치 > 방향에서 변경을 클릭합니다.**

a. 방향 모드를 선택합니다.\
b. 클릭 **저장** 하여 변경 사항을 확인합니다.

<div align="left" data-with-frame="true"><img src="https://1565113462-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNje42M0OzzbT2nhzkB3K%2Fuploads%2Fgit-blob-b2d990dab20fe6188d65e50ae8bb34c1c853abe8%2F88cacdfd55ddccaea797014e2b1ea2c357d8d713.png?alt=media" alt="" width="356"></div>
{% endstep %}
{% endstepper %}

{% hint style="danger" %}
Command Connector는 최대 4개의 Verkada가 아닌 카메라 피드를 회전할 수 있습니다. H.264 메인 및 하이 프로필만 카메라 회전을 지원합니다.
{% 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-connector/ko/configuration/change-a-non-verkada-channel-orientation.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.