> For the complete documentation index, see [llms.txt](https://docs.acestudio.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acestudio.ai/docs/product-wiki-ko/voice-cloning/cloning-a-voice-for-vocal-synth/private-share.md).

# 비공개 공유

ACE Studio에서 클로닝한 음성을 다른 사용자와 비공개로 공유하세요.

## 음성 비공개 공유란

계정의 모든 제어 권한을 유지한 채, 협업 좌석을 등록하여 복제한 음성을 다른 사용자와 비공개로 공유할 수 있습니다.

## 협업 좌석 등록

복제한 음성 중 어떤 항목이든 협업 좌석을 등록할 수 있습니다. [음성 복제 홈 페이지](https://acestudio.ai/app/custom-voice/vocal-synth).

좌석을 등록하려면, 다음을 클릭하기만 하면 됩니다. <kbd>공유</kbd> 복제한 음성 카드의 버튼을 클릭한 다음 공동 작업자의 사용자 ID를 입력하세요.

## 모든 협업 좌석 관리

등록된 사용자 ID를 변경하거나 삭제하여 언제든지 각 좌석을 관리할 수 있습니다.

모든 좌석은 슬롯 관리 페이지에 표시됩니다.


---

# 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://docs.acestudio.ai/docs/product-wiki-ko/voice-cloning/cloning-a-voice-for-vocal-synth/private-share.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.
