# Working with other capabilities

Most of what makes Publishing worth having in the suite comes from what sits next to it. This page is the summary; each connection has its own page with the detail.

Where a connection does not exist, it is listed as such rather than left out, so you can stop looking.

---

## Every connection

| **Connects to**                        | **What you get** |
| -------------------------------------- | ---------------- |
| Approval                               | \-               |
| Capable Search                         | \-               |
| Confluence search index (CQL)          | \-               |
| Confluence page restrictions           | \-               |
| Capable capability visibility controls | \-               |
| Licensing                              | \-               |

---

## The pages

[ApprovalOne connection.](https://help.gocapable.com/publishing/approval.html)

[Capable SearchOne connection.](https://help.gocapable.com/publishing/capable-search.html)

[Confluence search index (CQL)One connection.](https://help.gocapable.com/publishing/confluence-search-index-cql.html)

[Confluence page restrictionsOne connection.](https://help.gocapable.com/publishing/confluence-page-restrictions.html)

[Capable capability visibility controlsOne connection.](https://help.gocapable.com/publishing/capable-capability-visibility-controls.html)

[LicensingOne connection.](https://help.gocapable.com/publishing/licensing.html)

---

## A few things worth knowing

* A connection needs both halves installed. In a standalone app most of these do not exist.
* Anything that depends on search only reflects pages that have been indexed.
* Published sites render Capable macros properly, which is where several of these pay off.

---

## Related

[IntegrationsThe section.](https://help.gocapable.com/publishing/integrations.html)

[Capable for ConfluenceThe whole suite.](https://staging.dev.capable-sites.com/wiki/pages/1412890864)

---

_Better with company._