One governed assistant, wherever work begins.
Use Linkence from a channel, browser, desktop, website, or compatible AI client. Each surface is a separate doorway into the same approved company context.
Choose the doorway that fits the work.
These are independent ways to reach Linkence. They are not a workflow and they do not need to be used together.
Slack botAsk from Slack channels and threads using the knowledge scope approved for the workspace.
BotDiscord botA proposed conversational access point for approved Discord servers and channels.
BotChrome extensionA proposed browser-side route to Linkence for teams working across web applications.
ExtensionDesktop appA proposed desktop route into the governed Linkence workspace.
NativeWebsite widgetA proposed embedded assistant for an approved website and deliberately scoped audience.
EmbedLinkence MCP serverA proposed server interface for compatible AI clients that need approved Linkence context.
Server
The interface changes. The workspace does not.
Slack botAsk from Slack channels and threads using the knowledge scope approved for the workspace.
Bot02Discord botA proposed conversational access point for approved Discord servers and channels.
Bot03Chrome extensionA proposed browser-side route to Linkence for teams working across web applications.
Extension04Desktop appA proposed desktop route into the governed Linkence workspace.
Native05Website widgetA proposed embedded assistant for an approved website and deliberately scoped audience.
Embed06Linkence MCP serverA proposed server interface for compatible AI clients that need approved Linkence context.
ServerNew access points without six new knowledge stacks.
Shared identityEach surface starts from an approved workspace and deployment boundary.
Shared governanceKnowledge scope and source permissions remain defined in Linkence.
Distinct routesBots, apps, embeds, and MCP remain separate access patterns with their own setup.
Choose access without confusing it with integration.
A surface is where people ask. An integration is where approved knowledge and actions connect.
Are these separate Linkence products?+
No. They are access surfaces for the same governed Linkence workspace. The interface changes, while the approved knowledge and organization boundary remain in Linkence.
Does using a bot make every channel part of the knowledge base?+
No. A bot is a place to ask Linkence. A connector is what imports or retrieves source content. Those are separate boundaries.
Can every workspace use every surface?+
Availability and deployment requirements vary by workspace, client, and environment. We confirm the supported surface and access boundary during implementation.
Does the MCP server replace source integrations?+
No. The MCP server gives compatible AI clients a route into approved Linkence context. Source integrations still determine what knowledge Linkence can access.
Meet teams where the question already appears.
We will map the audience, knowledge boundary, and deployment requirements before recommending a surface.