Important: Slack and publishing connections are project-scoped. Check the active project before editing credentials or channels.
Questions this page should answer
- Why did the old organization integrations route move?
- Where are Slack and publishing connections managed now?
- Which project settings page should I open next?
Before you continue
- Confirm you are in the correct project.
- Check whether the integration you need is project-specific.
- Use project-level settings for Slack channel, WordPress, and Webflow connections.
What this page gives you
- A pointer from the old integrations location to the current project integrations page.
- A reminder that publishing connections are project-scoped.
- A safe path to the page that actually controls connection state.
- Slack bot connection and channel selection for the current project.
- Reconnect flows when the project Slack app is missing the
app_mentions:readscope. - Publishing connections such as WordPress and Webflow.
How to use this redirect page
Open Project Integrations, then confirm the project name before connecting or editing anything.Quick setup checklist
- Open the current project.
- Go to Project Integrations.
- Confirm Slack and publishing connections belong to this project.
- Verify each connection after editing credentials.
What to fix first
Team routine
- When sharing setup docs: link to Project Integrations directly.
- After project changes: verify Slack and publishing destinations again.
- During onboarding: explain that publishing setup is project-scoped.
Keep in mind
- Organization members and billing remain organization-level settings.
- Slack and publishing connections are managed per project.
- Old route names may still appear in older internal notes or screenshots.