Channels
Route Slack and Microsoft Teams conversations into Lleverage projects and keep organisation installation separate from project-specific Agent context.
Channels connect conversation surfaces such as Slack and Microsoft Teams to the Lleverage Agent.
They are not the same thing as Connections. Connections authorise external-system tools. Channels decide how a conversation reaches the Agent and which Lleverage context the conversation runs in.
Organisation installation and project routing are different
There are two administrative layers:
organisation/workspace installation connects the Slack workspace or Microsoft Teams tenant to the Lleverage organisation;
conversation/project routing determines which Project context a conversation uses.
If the app is installed but a tool behaves differently from the web Agent, check routing before reconnecting the external provider.
Pin conversations that depend on project-specific capability
An unpinned conversation can be dispatched through organisation-level channel resolution rather than the same Project context as a web Agent session. That matters when a Connection, Skill or other capability exists only in a particular Project.
Pin the conversation to that Project when the operational work depends on Project-specific authority or context. This gives the channel run a clear working boundary instead of relying on cross-Project capability resolution.
For how Project boundaries affect available capability more generally, see Projects and solutions.
Identity and access still apply
Installing the Slack or Teams app does not grant Lleverage access by itself. The person using the Agent still needs to resolve to a Lleverage identity and to the Project access required for the work.
Use Members and Roles and Permissions for the Lleverage-side access model.
Supported conversation surfaces
The current channel service handles direct conversations and supported multi-person/channel contexts across Slack and Microsoft Teams. The exact interaction and attachment behaviour depends on the provider.
For operator guidance, see Agent in Slack and Agent in Microsoft Teams.
Set up a channel
If what you need is a Workflow trigger or external-system action rather than conversational Agent access, go back to Connections.
Last updated
Was this helpful?