Slack

Install Slack from workspace settings, approve the requested OAuth scopes, and select a default alert channel.

Use /embrasure for help or a governed data question:

/embrasure help
/embrasure What changed in analytics.orders?

Answers remain scoped to the linked Embrasure user and include available source evidence.

Each Scout alert thread is a scoped control surface for the exact report and check that created it. A linked user can ask for an explanation or issue a clear command to edit, run, mute, disable, delete, acknowledge, resolve, or relearn that check. Embrasure validates the complete command first, applies no partial change after a validation failure, records the Slack event and before/after state, and posts a deterministic receipt in the same thread.

Linked members can inspect. Editors can change checks and report state. Existing admin and security-admin rules still protect ownership, routing, and sensitive settings. Deletion requires explicit “delete” or “remove” wording and an exact target. Ambiguous or speculative replies ask a question without changing anything. Enter destination credentials and secrets only in protected web settings.

Explicit table watchers receive Scout alerts first, followed by confirmed owners and then evidence-based impact recipients. Change-rule channel alerts mention linked confirmed or downstream owners. Every table alert links directly to ownership correction. Channel delivery resolves data-product routes first, then the alert-family route, then the workspace default. Email remains the fallback for targeted recipients who cannot be reached in Slack.

Slack actions change Embrasure workflow state only after the request is validated. They do not write connected warehouse data.