Manage Slack workspaces

Manage Slack workspaces to control how notifications are routed across teams, regions, departments, or environments.

Each workspace represents a separate Slack integration with its own configuration, authentication, and notification settings. You can configure one or more Slack workspaces in a single P4 Code Review instance.

Configure workspaces

Configure a workspace either:

Important behaviour

The workspace identifier is used internally to track notifications and thread data. Changing an identifier creates a new workspace configuration, not a rename.

For example:

  • Changing na to north-america:

    • Creates a new workspace configuration.

    • Existing Slack threads are not reused.

    • New messages are posted as new threads.

To preserve existing behaviour, avoid changing workspace identifiers after they are configured.

Workspace independence

Each workspace operates independently.

This means:

  • A problem in one workspace does not affect other workspaces.

  • Each workspace uses its own Slack bot token.

  • Each workspace maintains its own channel mappings.

  • Each workspace applies its own notification settings.

Adding or removing workspaces

Add a workspace

When you add a workspace:

  • Notifications begin after the workspace is configured.

  • Existing reviews generate notifications in the new workspace when their next update occurs.

  • Existing workspaces continue to operate normally.

Remove a workspace

When you remove a workspace:

  • Notifications to that workspace stop immediately.

  • Existing Slack threads are no longer updated.

  • Other workspaces continue to operate normally.

Multi-workspace use cases

Common multi-workspace deployment scenarios include:

  • Routing notifications to separate regional Slack workspaces.

  • Supporting multiple business units.

  • Separating production and test environments.

  • Delivering notifications to different teams that do not share a Slack workspace.