> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/developer-guide/pt-br/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-publish-a-capsule.md).
# Como publicar uma Cápsula
Saiba quais critérios você precisa atender para publicar uma Cápsula na Digibee Integration Platform.
Publicar uma Cápsula significa disponibilizá-la para uso em *pipelines*.
## Pré-requisitos
Para publicar uma Cápsula, você deve atender a estes critérios:
* Adicionar um JSON Schema na aba **Contrato** do [formulário de configuração](/documentation/developer-guide/pt-br/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-configure-a-capsule.md).
* Preencher o [formulário para salvar a Cápsula](/documentation/developer-guide/pt-br/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-save-a-capsule.md).
* Ter a permissão CAPSULE:UPDATE:PUBLISH. Leia mais na [documentação sobre Papéis](/documentation/developer-guide/pt-br/platform-administration/administration/new-access-control/access-control-roles.md).
## Publicando uma Cápsula
Com todos os critérios atendidos, há duas formas de publicar uma Cápsula:
### Aba Cápsulas
Na página **Build**, acesse a aba **Cápsulas** e localize a Cápsula desejada dentro do seu grupo. Clique no menu de três pontos e selecione **Publicar.**
### Canvas
No Canvas, clique em **Publicar** no canto superior direito. O botão ficará inativo se alguns dos critérios não forem atendidos.
Uma vez publicada a Cápsula, ela recebe a *tag* **Publicado** e é adicionada à lista de Cápsulas disponíveis que podem ser usadas nos *pipelines*. As Cápsulas públicas com o selo são certificadas pela Digibee.
---
# 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.digibee.com/documentation/developer-guide/pt-br/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-publish-a-capsule.md?ask=&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.
