Skip to main content

Ask SABLE in Slack

SABLE can answer questions from a direct message or an app mention in an approved Slack channel. It uses the same scoped project data and document evidence as Ask SABLE, and it never posts a substantive answer into a channel. Answered channel mentions may receive a neutral acknowledgment; setup and answers arrive in a direct message.

Slack access is tied to your verified SABLE identity. An administrator must first enable Slack access for your SABLE account.

  1. Send SABLE a direct message. If you are joining through Slack Connect, mention SABLE in the approved shared channel instead.
  2. Open the private sign-in link SABLE sends you. The link expires after 10 minutes and can be used once.
  3. Sign in to SABLE in the browser and complete the link.
  4. Return to Slack and resend your question. The question that started the linking flow is not retained for an answer.

SABLE never links accounts by matching an email address or display name. If the link expires, start again from Slack to receive a new one.

Ask a question​

  • In a direct message, send the question to SABLE.
  • In an approved channel, mention @SABLE and include the question.
  • In an approved Slack Connect channel, follow the same mention flow. An operator must approve that exact channel and external workspace first.

For example:

  • “What is the current status of the Acme account?”
  • “What is blocked on the website launch?”
  • “What needs my attention today?”

Answers are private. SABLE can read authorized business records and summarize your personal priorities, but it cannot change projects or external systems from Slack. Slash commands and file attachments are not supported.

Your Slack scope defaults to projects where you are a member. An admin or lead can explicitly opt in to their own All projects scope through an operator. This setting does not permit impersonating another person, and it stops applying if the person is no longer an admin or lead. SABLE may report that an account is missing when it falls outside your current Slack scope.

Troubleshooting​

  • No link arrives: Ask an operator to confirm your SABLE account is active and Slack access is enabled. Slack Connect users must begin in the approved shared channel.
  • The link worked, but there is no answer: Resend the original question after linking.
  • A channel mention is ignored: The channel may not be approved, SABLE may no longer be a member, or a Slack Connect workspace or participant may no longer be allowed.
  • Slack desktop looks stale: Reload Slack, reopen the SABLE conversation, and resend. A cached desktop view may lag behind a link completed in the browser.
  • An account or project is missing: Confirm the project is in your membership scope. Admins and leads who need their own All projects view must request the explicit Slack scope setting.
  • The response is delayed: Scheduled dispatch normally begins within about one minute, then answer generation and any retries add time.

For installation and policy checks, see Slack setup and operations.