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

# Architect for Slack

> Install the Architect Slack app to get briefs, prospect alerts, and answers about your pages without leaving Slack

The Architect Slack app brings your Architect workspace into Slack: scheduled briefs, real-time prospect activity, and an assistant you can ask about your pages, audiences, and people.

## What you can do in Slack

### 📬 Organization briefs

Architect posts a recurring brief to a channel you choose — a daily morning roundup of yesterday's activity, a Monday roundup of the past week, or both. Briefs cover page and audience analytics plus the questions your visitors asked.

### 👤 Personal briefs

Each teammate can receive their own brief, independent of the organization brief. Personal briefs are delivered by email today; Slack DM delivery is listed as **Coming soon** in the Notifications UI.

### 🔔 Prospect activity alerts

When a prospect is active on one of your pages, Architect posts to your notification channel and keeps the message updated as the session progresses, so a live visit reads as a single thread instead of a stream of pings.

### 💬 Ask Architect in Slack

Mention `@Architect` in a channel the app is in, or send it a direct message, and it replies in the thread. The assistant can look up your pages, audiences, and people to answer questions such as *"which audiences did we publish this week?"* or *"what do we know about [jane@acme.com](mailto:jane@acme.com)?"*.

<Note>
  In Slack, the assistant is **read-only**. It can look up information scoped to your Architect organization, but it cannot create, edit, or delete anything. Use the Architect app or [MCP integration](/docs/overview/integrations/mcp-overview) for changes.
</Note>

## Before you start

* An Architect account at [app.tryarchitect.com](https://app.tryarchitect.com)
* A Slack workspace, and permission to install apps in it (some workspaces require an admin to approve the request)

## Install the Architect Slack app

<Steps>
  <Step title="Open Notifications → Channels in Architect">
    Sign in to [app.tryarchitect.com](https://app.tryarchitect.com) and go to **Notifications**, then the **Channels** tab.
  </Step>

  <Step title="Connect Slack">
    On the **Slack** card, select **Connect**. You are redirected to Slack to review the permissions Architect requests.
  </Step>

  <Step title="Approve the app in Slack">
    Choose the workspace to install into and confirm. Slack returns you to Architect, and the Slack card shows the connected workspace and who connected it.

    <Check>
      The Slack card reads **Connected**, with your workspace name in the subtitle.
    </Check>
  </Step>

  <Step title="Pick a notification channel">
    Still on the **Slack** card, choose the channel Architect should post organization briefs and prospect alerts to. Both public and private channels are listed once the app can read them.

    For a private channel, invite the app first by typing `/invite @Architect` in that channel.
  </Step>

  <Step title="Choose what gets sent">
    Open the **Briefs** tab to turn organization and personal briefs on or off and set their cadence. Briefs are sent at 08:00 in the time zone of the person who configured them. Organization briefs go to your Slack channel; personal briefs go to your email.
  </Step>
</Steps>

## Permissions the app uses

Slack shows you the exact list at install time. Architect uses these scopes:

| Scope                          | Why Architect needs it                                                                |
| ------------------------------ | ------------------------------------------------------------------------------------- |
| `chat:write`                   | Post briefs, prospect alerts, and assistant replies.                                  |
| `chat:write.public`            | Post to a public channel the app has not been invited to.                             |
| `channels:read`, `groups:read` | List your public and private channels so you can pick a notification channel by name. |
| `channels:join`                | Join the public channel you select as your notification channel.                      |
| `app_mentions:read`            | See messages that mention `@Architect` so the assistant can reply.                    |
| `im:read`, `im:history`        | Receive and reply to direct messages sent to the app.                                 |
| `users.profile:read`           | Address the person the assistant is replying to by name.                              |
| `reactions:write`              | Acknowledge a message with a reaction while the assistant works on a reply.           |

Architect never requests admin, search, or message-export scopes, and does not read channels it has not been added to.

## How your data is handled

* **Sent to Slack**: the content of your briefs, prospect activity alerts, and assistant replies.
* **Read from Slack**: the list of channels in your workspace, the profile of the person the assistant is replying to, and the messages in a thread where `@Architect` was mentioned or in a direct message with the app. Thread messages are used only to generate that reply.
* **Stored by Architect**: your workspace and channel identifiers, your notification preferences, the link between a Slack user and their Architect account, and the delivery state of messages Architect has posted.

Full details are in the [Architect privacy policy](https://legal.tryarchitect.com/privacy-policy), which also explains how to request access to, transfer of, or deletion of your data.

## Turn it off

<Steps>
  <Step title="Disconnect in Architect">
    Go to **Notifications → Channels**, open the **Slack** card, and select **Disconnect**. Architect stops posting immediately.
  </Step>

  <Step title="Remove the app in Slack">
    In Slack, go to **Settings & administration → Manage apps**, find **Architect**, and remove it to revoke the workspace token.
  </Step>

  <Step title="Request deletion of stored data">
    Email [support@tryarchitect.com](mailto:support@tryarchitect.com) to have the Slack data Architect stored for your organization deleted.
  </Step>
</Steps>

## Troubleshooting

<AccordionGroup>
  <Accordion title="The channel list is empty or won't load">
    Architect needs the `channels:read` and `groups:read` scopes to list channels. Reconnect Slack from the **Slack** card to grant them, or enter a channel ID manually.
  </Accordion>

  <Accordion title="Nothing is being posted to my channel">
    Check that the Slack card still reads **Connected** — a revoked or expired installation shows **Reconnect to resume notifications**. If the destination is a private channel, invite the app with `/invite @Architect`.
  </Accordion>

  <Accordion title="The assistant doesn't reply when I mention it">
    The app only sees mentions in channels it belongs to. Invite it with `/invite @Architect`, then mention it again. Direct messages work without an invite.
  </Accordion>

  <Accordion title="Architect says the connection is missing scopes">
    Slack grants scopes at install time, so newly added capabilities need a fresh authorization. Select **Connect** on the Slack card to re-authorize; the error message names the missing scopes.
  </Accordion>
</AccordionGroup>

## Get help

Email [support@tryarchitect.com](mailto:support@tryarchitect.com) with your workspace name and a description of what you were doing. You do not need an Architect account to contact support, and we aim to respond within two business days.


## Related topics

- [What is Architect?](/docs/index.md)
- [Changelog](/docs/changelog.md)
- [How does Architect Cookie Consent Banner work?](/docs/overview/faq/how-does-architect-cookie-consent-banner-work.md)
- [Connect MCP with Cursor](/docs/overview/integrations/mcp-cursor.md)
- [MCP Integration](/docs/overview/integrations/mcp-overview.md)