# Connected Apps

> Combine an app definition with connected channels so participants work on the same tickets from their own platforms.

Canonical HTML page: https://conclude.io/doc/connect/connected-apps/
Last updated: 2026-11-02

---

Connected Apps combines an app's ticketing workflow with a channel connection. A ticket created on one side is visible on the other, and participants can follow replies, updates, and conclusions from their own Slack or Microsoft Teams environment.

![A Support app installed in a Slack channel and synced to a Teams channel through one connection, with the same ticket on both sides](https://conclude.io/images/doc/figures/f13-connected-apps.svg)

*Figure: Apps defines the work; Connect carries it between the participating channels. Both sides work on the same tickets, while each organization retains its own platform administration.*

This works for internal collaboration and cross-company connections. An internal helpdesk can serve employees on both Slack and Microsoft Teams, and customer support can run over an [external connection](https://conclude.io/doc/connect/external/). A shared request process, an approval workflow, or an incident response process uses the same platform concepts. Building the app in the [visual editor](https://conclude.io/doc/apps/tutorial/) requires no software development skills.

## Set up a connected app

1. Enable **Apps** and the relevant **Internal**, **External**, or **Bridge** solution under [**Admin console > Solutions**](https://conclude.io/admin/solutions).
2. Connect the two channels under [**Connect > Channels**](https://conclude.io/app/connect/channel), [**Connect > External**](https://conclude.io/app/connect/external) or [**Bridge**](https://conclude.io/app/bridge). See [Internal connections](https://conclude.io/doc/connect/internal/), [External connections](https://conclude.io/doc/connect/external/) or [Bridge](https://conclude.io/doc/connect/bridge/).
3. Open [**Apps**](https://conclude.io/app/apps) in the Dashboard and click **Install app**. Choose a template, then the workspace, team and channel on your side of the connection.
4. The next step shows the connected channel and says that the app will be enabled on both sides. Click **Install**.
5. Conclude adds the app to the channel at the other end. Tickets, replies and status changes then sync between the two channels.

You can also install the app first and connect the channel afterwards. Conclude then enables the app on the other side when the connection is created. Install the app on the side that should own its configuration, because its settings apply to both channels. The [Connected Apps quickstart](https://conclude.io/quickstart/connected-apps/) walks through both orders with screenshots.

For thread-based tickets created from Teams messages, use the Teams channel's **Posts** layout as described in the quickstart. If messages or updates are missing, check the connection and [Teams integration account](https://conclude.io/doc/admin/organization/integration-account/) before changing the app definition.

## Configure the app and connection

The [app editor](https://conclude.io/doc/apps/editor/) controls the work: fields, responsibility, labels, and integrations. [Connect settings](https://conclude.io/doc/connect/message-syncing/) control the conversation, including existing-thread history and identity presentation. [Attachment policies](https://conclude.io/doc/connect/file-sharing/) control file and image sharing.

Connecting channels does not grant the other company's users administrative access to your account. Review [Manage apps](https://conclude.io/doc/admin/users-and-access/roles-and-permissions/#apps) and the app's own [roles](https://conclude.io/doc/apps/editor/roles/) before delegating changes to a shared workflow.

An external system is optional. For example, [Zendesk integration](https://conclude.io/doc/apps/integrations/zendesk/) can synchronize the same work with a support system; it is an extension of the app rather than a prerequisite for Connected Apps.