Skip to content
NanoFlags
Start free

Tooling

Slack

Post release events to Slack channels and let owners and admins approve or reject a change right from the message. Each decision is made as the linked NanoFlags member, with exactly the rules of the dashboard. Publishing always stays a separate step in NanoFlags.

Two ways to connect

NanoFlags Slack appIncoming Webhook
SetupAn admin installs the app in the workspace once, then picks channels by channel ID.An admin pastes a channel's webhook URL. Nothing to install.
MessagesEvery event, in English or Arabic.Every event, in English or Arabic.
Approval requestsInteractive: Approve and Reject buttons, updated in place as decisions arrive.A Review change button that opens the dashboard.
PlanTeam and above.Team and above.

Both can be used side by side; a destination uses one or the other. Settings → Integrations → Slack.

Install the Slack app

  1. As an owner or admin, open Settings → Integrations → Slack and choose Connect Slack.
  2. Slack shows what the app may do in your workspace. Choose Allow (a workspace admin may need to approve apps first).
  3. Slack returns you to NanoFlags. Confirm Connect workspace: the workspace now belongs to your NanoFlags organization.
  4. Add a destination with Delivery: NanoFlags app and the channel ID (in Slack: the channel name → About → Channel ID). The app can post to public channels without joining; for a private channel, first run /invite @NanoFlags there.
Why connecting is protected
The confirmation only works for the admin who started it, in the same browser, within one hour. A Slack workspace can be connected to one NanoFlags organization only, and an organization to one workspace.

Destinations and events

A destination receives the events you tick, from one project or every project, optionally only for some environments, in the language you choose: approval requests and decisions, publishes with a diff summary, scheduled publish results, failed scenario checks, kill switches, promotions, failing webhooks and a daily stale-flags digest. Send test message checks a destination; the delivery log shows every attempt with Slack's answer (for example not_in_channel when the app must be invited to a private channel).

Approve and reject in Slack

  • When someone requests approval, app destinations receive the change with its environment and flags, the number of valid approvals needed, and the buttons Approve, Reject and Review change.
  • Approve asks for a confirmation, then records your approval of the draft the message shows.
  • Reject opens a dialog for the comment the author will see (required, as in the dashboard). The change goes back to draft.
  • The message is updated in place: who approved or rejected, whether the draft changed since, and once published, the revision. Decisions made in the dashboard update it too.
  • If a decision is refused, only you see why, in a reply below the message. The message itself is unchanged.

Who is clicking

NanoFlags must know which member pressed the button. It uses, in order:

  1. A linked account. The first time, the reply offers Link my NanoFlags account: a one-time link, valid 30 minutes, that you confirm while signed in to NanoFlags. The link is bound to the e-mail address Slack has confirmed for your Slack account, and only the NanoFlags account whose confirmed e-mail is the same address can confirm it, so a forwarded link is useless to anyone else. Slack accounts without a confirmed e-mail (and guests, apps and people from other workspaces) are not offered a link: ask a workspace admin to confirm your e-mail in Slack, or decide in NanoFlags. Links are listed on the Slack settings page; you can remove yours, and admins can remove any.
  2. Your verified e-mail, if your organization allows it (on by default; admins can turn it off to require linked accounts). It applies only to full members of the connected workspace whose e-mail Slack has confirmed, and only when it equals the confirmed e-mail of a member of your NanoFlags organization. Guests, apps and people in channels shared with other workspaces never match by e-mail.

Rules each decision follows

A button press runs the same database check as the dashboard's Approve and Reject, as you:

  • Your role and access: approving needs the approve permission for that environment (owners and admins by default; project and environment overrides apply).
  • Independent approval: the author cannot approve their own change, and neither can anyone who edited the environment's draft since the change's base revision.
  • The environment's policy: the number of approvals required, and approvals bound to the exact draft. If the draft changed after the message was posted, Approve is refused: review the current draft in NanoFlags.
  • The change must still be waiting for approval, and the same decision on the same draft is not recorded twice.
  • Two-step verification: Slack is not a second factor. In organizations that require two-step verification for owners and admins, decide in the dashboard; Slack explains this when you press a button.

Every decision is in the activity log as yours, marked as made from Slack.

Permissions and why

ScopeUsed for
chat:writePosting messages and updating the approval message in place.
chat:write.publicPosting to public channels without having to join them.
users:readTelling full members from guests and apps when identifying who pressed a button.
users:read.emailReading the verified e-mail of the person who pressed a button, only when they have no linked account: for e-mail matching (when on) and to bind the one-time link to that address.

The app reads no messages and no channel history. Every request from Slack is checked against Slack's signature and refused when older than five minutes.

What NanoFlags stores

  • The workspace: its ID and name, the app's bot user, the granted scopes and who connected it.
  • The bot token, encrypted with a key the database does not hold. It is never shown in the dashboard, returned by any API or sent to a browser.
  • Linked accounts: Slack user ID and display name, and the member they act as.
  • For approval messages: channel ID and message timestamp, so the message can be updated (kept 90 days).
  • E-mail addresses read from Slack are only compared, except for a pending one-time link, which keeps the Slack-verified address for at most 30 minutes (the expired link is deleted within two days).

See the privacy notice.

Disconnect

  • Disconnect (Slack settings page, admin): deletes the stored token, every linked account and every app destination. Remove the app in Slack too (Apps → NanoFlags → Remove app).
  • Removing the app in Slack first: Slack tells NanoFlags, which deletes the token at once and stops app destinations. Reconnecting restores them.
  • Incoming-webhook destinations are not affected.