> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tekma.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Share a capture report in Slack

> Connect Slack, choose a channel or permitted recipient, and send a private link-backed report.

Slack delivery posts a plain-text capture report and a private Tekma link. A workspace owner connects one Slack bot identity and default channel. Members use that configured channel; only the owner who completed the OAuth connection can discover and choose alternate channels or individual recipients.

## Requirements and connection

Setup requires a workspace owner. Use **Continue to Slack** when OAuth is enabled, or **Use a token instead** with a bot token. For a token connection, invite the app to the intended channel and enter **Channel ID** (for example `C0123456789`). The bot must be able to post there. OAuth additionally binds the connecting Slack user and team identity; another Tekma owner cannot use that OAuth identity to discover alternate destinations.

1. Open **Settings → Integrations** and choose **Connect** beside Slack.
2. Choose **Continue to Slack** and authorize, or choose **Use a token instead** and enter the bot token.
3. Enter **Channel ID** for the default channel. Both the bot and connecting OAuth user must belong to a channel selected for OAuth discovery.
4. Choose **Connect Slack**. Confirm **Connected**, then use **Manage** to change the default channel without replacing credentials.

## Send to a channel or person

1. Open a saved capture and choose **Send to app → Slack**.
2. Wait for **Loading preview…**. Review the report text, destination, and private **Open capture** link.
3. Members choose the configured channel. The connecting OAuth owner can choose another channel or an individual recipient after Tekma verifies current membership. User choices exclude bots, deactivated users, and users from another Slack team. Group DMs are not supported.
4. Choose **Send to Slack** once. A direct-message send is posted by the Tekma bot to the selected person; it is not sent as the connecting human.
5. Open Slack and confirm the message. If delivery is unconfirmed, inspect the channel or DM before trying again.

| Destination          | Who can choose it                | Conditions                                                              |
| -------------------- | -------------------------------- | ----------------------------------------------------------------------- |
| Configured channel   | Members with capture edit access | Bot can post; token connections stay here                               |
| Alternate channel    | OAuth connecting owner           | Connecting user and bot belong to the channel                           |
| Individual recipient | OAuth connecting owner           | User is active and in the same Slack team; Tekma opens/resumes a bot DM |
| Group DM             | Not supported                    | —                                                                       |

Slack receives plain text, saved summary, sanitized source URL, capture kind and an Open capture button. Tekma does not upload recordings, screenshots, comments, diagnostics, or raw logs. Automatic URL/media unfurling is disabled on this outgoing path. The private link still requires Tekma access. Revoking the link cannot retract text already copied into Slack.

## Troubleshooting

If the default channel fails, invite the bot and confirm the token has the scopes shown by the connection form, including `chat:write` and channel-read access. If alternate channels or people do not appear, the current user is not the OAuth connecting owner; reconnect Slack with that owner's Slack identity. Discovery does not send a message. Large workspaces may need another channel if membership verification is bounded. A permalink lookup failure can still leave a successfully posted message; check Slack before retrying.

Slack link previews are a separate incoming feature. They require an eligible exact-origin public share and a configured Slack events setup; an ordinary **Send to Slack** message does not make a private capture public.