Start Free Trial
Start Free Trial
Platform documentation

Slack (@{{aiName}}) - Access & permissions

Last updated 5 November 2026

Slack (@{{aiName}}) - Access & permissions

Elevale uses Slack OAuth to read metrics from Slack (@{{aiName}}). Elevale does not modify data in the external system. Tokens and keys are encrypted server-side after validation.

Who can connect

  • Workspace admins and users with permission to manage Workspace Settings integrations.

  • Connections are managed from Workspace Settings → Integrations.

  • Requires professional on your workspace plan.

What Elevale accesses

  • Read-only metrics exposed as KPI data points (see the Data points article).

  • Connection metadata (account IDs, property IDs, organisation tenants) needed for sync.

  • No write access to campaigns, repositories, accounting records, or CRM objects unless the provider API requires it for authentication only.

Slack bot permissions

  • app_mentions:read see messages that mention the app.

  • chat:write post replies in Slack.

  • channels:history and groups:history - read recent messages in public and private channels the app is in, so the reply has context.

  • im:history read direct messages with the app.

  • users:read and users:read.email - match the Slack user to an Elevale member.

Sync direction

  • Mentions in Slack are sent to {{aiName}}. The reply is posted back in Slack.

  • If the reply would change Elevale data, it follows the same confirmation rule as chat in Elevale. With confirmation cards on, nothing is saved until someone confirms.

  • Channel history is not imported into Elevale Chat.

Branding

Slack's consent screen uses Elevale's app. It does not show a white-label app name, and branding settings cannot change it.

Disconnect and data retention