Hello,
On a Free JSM site, connecting a service space to Slack never completes. In Space settings > Channels & self service > Chat, Add to Slack opens Slack’s permission screen. After Allow, I land back on the Chat page with ?expectedSlackTeamId=<our team ID>&error=generic-error. The page still shows Add to Slack, and no agent-channel step appears.
What I’ve confirmed:
- The team ID in the error URL matches the Slack workspace I’m authorizing.
- The same person is used on both sides, with the same email in Jira and Slack. An earlier attempt with different accounts returned
error=email-mismatch, so the check is working. Since matching the accounts, it’s always generic-error. - That person is a Jira admin and a Slack Workspace Admin.
- Slack’s activity log shows Atlassian Assist — Installed by that same user, so the Slack half succeeds.
- Atlassian Assist (
halp.com) is listed under Connected apps as a System app (installed automatically). - The global permission Browse users and groups includes
atlassian-addons-admin. - Slack private-channel creation is open to everyone except single-channel guests.
- No other service space on the site uses chat.
- Retried several times over two days, including removing Assist from Slack and installing it fresh, and from a separate browser with only that user signed in. The result is always the same.
Is chat (Assist) actually supported on the Free plan today? Atlassian’s pricing page lists Slack and Teams on Free, but a third-party article says it isn’t. Or is there a site-side state that gets stuck after a failed first attempt (the first one was the email mismatch)? Happy to share the site URL with Atlassian staff privately.
Any help would be appreciated, been stuck on this for two days now :(