Send confirmed messages
chat:write lets the app post the test message or report summary you confirm in a saved channel where the app is a member.
Leera for SlackLimited pilot
Share a QA report. Choose who sees it.
Leera brings project planning, documents and QA work together. Its Slack pilot lets a workspace administrator share an existing issued QA report summary in a chosen channel. The pilot is not generally available or listed in the Slack Marketplace. Your instance must have the pilot enabled before you can connect.
The overview
What does the Slack pilot do?
An administrator confirms each test message or QA report summary before it is sent. A report message includes its verdict, counts, commit, environment, issue date, sender attribution and a link back to Leera. Opening the source still requires project access. Automatic notifications, issue intake, thread synchronization and MCP-triggered Slack messages are not part of this pilot.
Set up
Connect once. Choose a channel for each project.
You need a Leera workspace administrator account, access to the project and QA reports, and permission to approve the app in Slack. A Slack administrator may need to approve the installation under your workspace policy.
- 01
Open the Slack pilot in Leera
In your Leera project, open Settings → Integrations → Slack pilot. Select Enable Slack, review the requested permissions in Slack, and approve the intended Slack workspace. Cancelling returns you without enabling sharing. Each Slack workspace connects to one Leera workspace.
- 02
Invite the app and save a destination
Invite the Leera app to the intended Slack channel. Back in Leera, load channels, choose that channel, and save it. Public and private channels are supported where the app is a member. Saving a channel does not send a message. Check whether Slack Connect gives external organizations access to the channel.
- 03
Confirm a test, then share a report
Choose Send test message and confirm the destination. Refresh the delivery status and check Slack. Share latest QA report sends the latest issued report only after confirmation; it does not run a fresh test. All channel readers can see the summary and your Leera display name, even if they cannot open the source report.
Permissions
Only the access this pilot uses.
Slack grants these permissions to the app’s bot. The pilot does not request Slack message history, files, email addresses or permission to act as an individual Slack user. It does not automatically join channels.
Choose public channels
channels:read lets Leera show public channel names and IDs and verify that the chosen destination is available and the app has joined it.
Choose joined private channels
groups:read lets Leera show and verify private channels the app has been invited to. It does not grant permission to read their messages.
Data and control
Know what leaves your workspace.
Direct message delivery
For managed connections, Leera’s connection service handles encrypted credentials and connection metadata. Your Leera instance sends report content directly to Slack. On self-hosted installations, customers do not need an AWS account, queue service or their own Slack app to use the managed connection.
Bounded, on-demand sharing
The pilot allows 20 send requests per Leera workspace per UTC day, including tests. No Slack history is polled, no AI provider is called, and detailed test steps and attachments are not copied. Slack data is not used to train models by this integration.
Disconnect from settings
Disconnect Slack removes the instance’s credentials and project destinations, and cancels pending sends for every project in the Leera workspace. If remote removal cannot be confirmed, the screen asks a Slack administrator to remove the app in Slack. A message already being delivered may still arrive. Posted messages remain under Slack’s retention and deletion controls.
Good to know
Setup and delivery questions
Why can’t I enable Slack?
This is a limited pilot. Your instance must have it enabled, and you must be a Leera workspace administrator. The setup screen explains missing configuration. Ask your instance administrator or contact support. Slack’s own app approval policy may require a separate approval by a Slack administrator.
Why is my channel missing?
Invite the app to the channel, then reload channels in Leera. Use Load more channels if another page is available. Archived channels cannot be used. A private channel is visible only if the app has been invited. Choose a destination appropriate for the report, including any external people in a Slack Connect channel.
Why am I asked to remove an older Slack installation?
Slack can retain permissions granted to an older installation even after an app’s requested permissions change. This pilot accepts only the permissions listed above. Ask a Slack administrator to remove the Leera app in Slack’s Manage apps settings, then return to Leera and connect again. Changing the permission list alone does not remove previously granted access. Existing messages remain in Slack.
Why is my Slack workspace already connected elsewhere?
A Slack workspace can be connected to only one Leera workspace. Ask the administrator of the current Leera workspace to disconnect it before reconnecting, or contact support to verify ownership. Do not share another workspace’s credentials.
What should I do if delivery is unconfirmed?
Check the selected Slack channel before sending again: the message may already exist. Refresh status in Leera. Queued means accepted for delivery, not delivered. Temporary Slack rate limits are retried automatically; an ambiguous response is not blindly resent because that could duplicate a message.
How long is integration data retained?
Pending message payloads expire after one day and are cleared on completion, failure, cancellation or uncertain delivery. Delivery metadata and daily send counters are scheduled for cleanup after seven days. Connection metadata is kept while needed to operate the connection or verify ownership after disconnection. See the linked privacy policy for the connection service, deletion requests and self-hosted responsibilities.
Can I ask for access, export or deletion of my data?
Yes. Email contact@leera.io with your request and the relevant workspace details. We verify the requester’s authority before providing or removing data. For customer-operated instances, contact your instance administrator for the locally stored data; Leera can help with data held by the managed connection service. Do not send tokens or report contents with the request.
Help without a login
Get support or review your data controls.
Email Slack integration support
Contact support@leera.io. Include the workspace URL, the action you tried, approximate time and the displayed error. Never include access tokens, signing secrets or sensitive report content.
Explore Email Slack integration supportRead the Slack privacy disclosure
Review collected data, purposes, retention, disconnection and how to request access, export or deletion. No Leera account is required to read this policy or email a request.
Explore Read the Slack privacy disclosure