The Slack integration is a workflow app inside the integrations page at https://lengrowth.com/integrations.

Use Slack when you want LenGrowth activity to show up in a team channel and when you want the workflow to stay visible in the place your team already uses.

The integration card describes it as a Workflow App.

The setup copy says to install the LenGrowth app in your Slack workspace to enable:

The page makes one more thing clear: the Slack connection belongs to the active company in the header. It is not a global account-level switch.

Use Slack when:

Before connecting Slack, choose the company in the header.

If no company is selected, the integrations page tells you to choose or create one first.

In the Workflow Apps tab, open the Slack card.

The card may show a status like Not connected, Connected, or Active Workspace depending on the current state.

The setup form uses the Add to Slack button image inside the modal.

When you click Connect, LenGrowth opens the Slack authorization URL for the selected company. That is the step where Slack handles the connection itself.

It is normal for the browser to leave LenGrowth briefly during that step. The Slack authorization flow is external, so the connection is finalized in Slack before you come back to the integrations page.

Complete the Slack authorization steps in Slack, then return to LenGrowth.

If the authorization succeeds, the card should move into a connected state.

Once connected, the card can show Connected and may identify the workspace as active.

If the workspace has not been fully configured yet, the card may say Workspace selected, awaiting bot credentials.

That is a useful reminder that a company has been selected, but the Slack side is not fully ready yet.

If the connection is fully healthy, the card should also swap from the plain Connect action to Manage connection.

The Slack card stays intentionally compact after setup. It does not try to list every channel or every alert inside the card.

Instead, it helps you answer three simple questions:

That keeps the integrations page easy to scan even when multiple sources are connected.

After Slack is connected, LenGrowth can keep the workflow connected to the Slack workspace instead of leaving the activity only inside the app.

The integrations page does not promise a specific message format in the help text, so keep the guidance focused on the visible behavior:

Slack is part of the workflow-app side of LenGrowth, so it is most useful when a team wants alerts and collaboration to stay in the same place as day-to-day conversations.

If the connection is removed, the card returns to the disconnected state and the Slack workspace is no longer active for that company.

That usually means the auth flow did not finish. Return to LenGrowth after the Slack step and check the card status.

That means the company has been selected, but the Slack connection is not fully configured yet.

Use the same card in Integrations and choose the disconnect option. The card should return to a disconnected state after the change is saved.

The card description uses #growth as the example channel for alerts. If your setup uses a different workspace pattern, the channel choice should follow the Slack-side configuration.

Reopen the Slack card and confirm the connection state. If it still says Not connected, the auth flow likely did not finish cleanly.

That is how the integration is designed. Pick the company in the header first, then connect Slack for that workspace only.

Use Manage connection on the Slack card. That keeps the connection management in the same place as the setup.

Select a company first. Slack connections are attached to a company workspace, not to the account in general.