Skip to content

docs(messaging): clarify Slack token validation and slack policy preset (#4979)#4986

Open
abhi-0906 wants to merge 1 commit into
NVIDIA:mainfrom
abhi-0906:docs/issue-4979-slack-onboard-validation
Open

docs(messaging): clarify Slack token validation and slack policy preset (#4979)#4986
abhi-0906 wants to merge 1 commit into
NVIDIA:mainfrom
abhi-0906:docs/issue-4979-slack-onboard-validation

Conversation

@abhi-0906

Copy link
Copy Markdown

Summary

Documents the intended Slack onboarding behavior that #4979 ran into: NemoClaw validates Slack tokens against the live Slack API during onboard, so invalid/placeholder tokens (invalid_auth) cause the Slack channel to be skipped — and because the slack network policy preset is only applied for channels that are actually enabled, the preset is not applied either (not shown as in policy-list). Also points to the existing NEMOCLAW_SKIP_SLACK_AUTH_VALIDATION=1 escape hatch for exercising Slack setup and the slack preset with placeholder tokens in restricted/hermetic environments.

Related Issue

Fixes #4979

Context

The current behavior is intentional and secure: live token validation prevents onboarding from enabling a channel with credentials Slack cannot use. The "fake-token test mode" the issue asks for already exists as NEMOCLAW_SKIP_SLACK_AUTH_VALIDATION (documented in the commands reference). The gap was purely documentation — the consequence chain (invalid tokens → channel skipped → slack preset not applied) and the skip-flag's role in policy-preset testing were not stated where Slack onboarding is documented. This is the reporter's "at minimum, document the mismatch" resolution; no behavior change.

Changes

  • docs/manage-sandboxes/messaging-channels.mdx — in the Slack section, document that validation calls the live Slack API, that rejected tokens skip the channel and therefore do not apply the slack preset, and that NEMOCLAW_SKIP_SLACK_AUTH_VALIDATION=1 skips the live probes for testing (format checks still apply).

Type of Change

  • Doc only (prose changes, no code sample modifications)

Verification

  • No secrets or credentials committed
  • Uses the existing <name> sandbox placeholder and backtick-wrapped conventions; new env/command references match the commands reference
  • Note: npm run docs / the docs link-check were not run on my Windows dev box (the link-check harness shells out in a way that fails locally); the change adds no links and is plain prose with inline code spans. Deferred to CI on Linux.

…et (NVIDIA#4979)

Signed-off-by: Abhimanyu Kumar <abhimanyukumar7290@gmail.com>
@copy-pr-bot

copy-pr-bot Bot commented Jun 8, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore Build, CI, dependency, or tooling maintenance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[All Platforms][Policy&Network] Slack resume policy test fails: fake SLACK_* env vars now cause invalid_auth and Slack policy preset is not applied

2 participants