Back to Leni

Leni in Slack

Install the official Leni agent. It uses each member’s authenticated Leni account, organization permissions, memory, and usage limits.

Loading Slack connection…

Getting started with Leni in Slack

Ask questions and request supported tasks using your Leni information, directly in Slack. An eligible paid Leni account is required; your organization permissions and usage limits still apply. Slack workspace administrators may also need to approve app installation.

The controls above show what is currently available to your account. If installation is unavailable, contact Leni support. These instructions do not mean the app is approved or listed in Slack Marketplace.

Leni uses AI and may generate inaccurate answers, summaries or other outputs. Review important results against their sources before relying on them or taking action.

Install the official Leni app
  1. Sign in to the correct production Leni account and organization. If sign-in opens a new tab, return here and select “I’ve signed in”.
  2. Select “Add Leni to Slack” above. Choose the intended Slack workspace, review permissions and approve, or ask your Slack administrator for approval.
  3. Select “Open Leni in Slack” and send a direct message, such as “Hello”. If a colleague already installed Leni, open its DM instead of reinstalling.
  4. Follow the fresh “Connect Leni” link in the DM. Sign in to your own Leni account, verify the displayed Slack workspace and user, and complete “Sign in with Slack” if requested.
  5. Return to Slack and send your question again. Try: “Using only this message, what is 14 plus 9?” Each colleague connects their own account separately.

Never forward account-link URLs or share the installer’s credentials. Ask Leni for a fresh link if yours expires. Installing the app does not give colleagues access to your private Leni memory.

Create your own branded Slack app

A paid organization owner/admin, or eligible self-serve account, can register a customer-owned Slack app with a different name and icon. Leni still runs the backend and verifies each user’s Leni access. No separate bot server is needed. Only trust app owners authorized to handle your conversations.

  1. When branded setup is available above, select “Create a branded Slack app”. Enter the front-facing name and select “Generate Slack manifest”.
  2. Select “Copy manifest”, then “Create app in Slack”. Choose “From a manifest”, select a workspace you administer and paste the generated JSON.
  3. In Slack’s Basic Information, add your icon. Enter the App ID, Client ID, Client Secret and Signing Secret in Leni’s setup form, then select “Save app securely”. Never send secrets in chat, screenshots or support messages.
  4. Use the configuration displayed by Leni. In Slack, verify the OAuth redirect URL and requested scopes. Enable Event Subscriptions, paste your app-specific Events Request URL, wait for verification, add the displayed supported bot events and save.
  5. Enable Interactivity & Shortcuts with the generated Interactivity Request URL. In App Home, enable the Messages tab and allow users to send messages. Keep Socket Mode and Enterprise-wide deployment off for this flow.
  6. Return here and select “Install [your app name]”. Choose the intended workspace and approve. Start installation from Leni, not a copied raw OAuth link.
  7. Open the branded app’s DM, send “Hello” and connect your own Leni account. A central Leni identity-verification page may appear even though the bot has your company’s name. Each colleague connects separately.

Follow the token-rotation setting shown in Leni’s generated configuration. Existing apps can keep rotation disabled only when Leni marks it optional. Once enabled in Slack, rotation cannot be turned off. Never change the shared official app’s settings to configure your separate branded app.

Test with synthetic data in a separate workspace: one workspace can have only one active Leni-powered app and is bound to one Leni organization. Do not replace a working installation just to test branding. A customer-owned app is not automatically Marketplace-approved; distributing it beyond its development workspace requires Slack’s distribution setup and any applicable approval.

Channels, privacy and notifications

An organization owner/admin can enable “Allow replies in internal Slack channels” for an installed workspace above. Invite the app to the intended channel and mention it to start a request. Use “Reply in thread” for follow-ups without repeating the mention. A new top-level request needs a mention.

Channel answers are visible to channel members, including Leni information you ask the agent to share. Use DMs for private work. Slack Connect channels with external organizations are blocked for Leni data retrieval. Group DMs and Enterprise-wide installation are not supported by this flow.

Accepted requests receive an eyes reaction and a progress message. On completion the progress text becomes “Worked on it”, and the answer is posted as a new message. Notifications still depend on Slack settings, Do Not Disturb, thread subscriptions and browser/OS permissions; an alert is not guaranteed.

Some connection and confirmation steps open Leni’s website. Memory-changing requests require confirmation before execution.

Troubleshooting and disconnecting
  • No channel reply? Check app membership, the internal-channel setting and that you replied in an activated thread. Use a DM for externally shared channels.
  • Wrong account or organization? Cancel the connection and request a fresh link from your own DM. Signing out of Leni does not revoke an existing Slack identity link; contact support to resolve a binding.
  • To disconnect a workspace, an organization manager selects “Disconnect from Leni” and confirms “Disconnect workspace”. This disconnects all linked members, not just one person. Uninstall the Slack app separately if desired.
  • Removing a branded app from Leni deletes its stored credentials and disconnects its workspaces. It does not delete the app registration in Slack.