Guide

PRC Slack admin guide

Configure the Slack connection at Settings → PRC Slack.

Requires manage_options.

Connection

FieldPurpose
Enable Slack chat (PRC Nexus)Inbound DMs and @mentions. Not environment-gated.
Enable publish noticesProduction always sends #publish and #decoded notices. Local never sends. On hosted staging (alpha, beta, canary), turn this on to send notices from this site.
Bot token overrideOptional xoxb- token for local/staging. Production always uses PRC_PLATFORM_SLACK_TOKEN.
Signing secret overrideOptional Events API secret for local/staging. Production uses PRC_PLATFORM_SLACK_SIGNING_SECRET.
Workspace ID overrideOptional team id (T…). Production uses PRC_PLATFORM_SLACK_WORKSPACE_ID.

Staff connect Slack from their WordPress profile. Connect Slack looks up the profile user's WordPress email (users:read.email). After this scope lands, reinstall or re-auth the Slack app on VIP.

Platform Factory Notifications

Platform Factory notifications turn Cursor Origin pull request events into Slack notices.

FieldPurpose
Enable Platform Factory notificationsAccept verified Origin events and queue Slack notices. Disabled webhooks return HTTP 200 without sending.
Engineering channel IDPrivate channel ID (C…) for pull requests merged to the trunk branch.
Trunk branchBranch treated as trunk. The default is trunk; refs/heads/trunk is also accepted.
Bot loginsOne login per line. These accounts never receive direct messages.
Slack roster fallbackOne login = email or login = U… mapping per line.

The section shows the Origin webhook URL and whether WordPress has the Origin API credentials. Copy that URL when you register the Cursor Origin app. Subscribe to these events:

  • pull_request.created
  • pull_request.reviewer.added
  • pull_request.reviewer.rerequested
  • pull_request.review.submitted
  • pull_request.merged

Ops create the Origin app, install it, and store the VIP constants before you enable this section. See Architecture → Register the Origin app.

WordPress first looks up an Origin email in Slack. If an event has no email, WordPress uses the roster entry for that login. WordPress skips a direct message when both values are missing.

Authors receive direct messages when a pull request opens, gets approval, or merges to trunk. Requested reviewers receive review-request messages. Trunk merges also go to the engineering channel. The original backport author receives a merge button for the release branch when the pull request is not a draft.

The Origin API credentials come from VIP constants. Do not put the app private key in the roster or another settings field.

Chat

Editors DM PRC Nexus or @mention it in a channel where it is invited. Map a WordPress user to Slack with the prc_slack_user_id profile field so Nexus can offer that editor's systems. Trending News and Social Builder copy both require edit_posts. Social copy needs a WordPress post ID (Nexus will ask if you omit one).

Point Slack Event Subscriptions and Interactivity at the routes in the REST API.

Was this helpful?