Skip to main content

​
Work surfaces and Slack

A work surface is where Hermes sends assignments, reminders, and chase messages. Self-install does not require Slack. The pack can use a safe Hermes messaging target that already exists, or it can keep local/manual mode active.

​
Supported self-install behavior

The pack can detect existing Hermes targets such as:
  • Slack,
  • Telegram,
  • Discord,
  • WhatsApp,
  • Signal,
  • Matrix,
  • Mattermost.
If exactly one safe target exists, Hermes can configure it automatically. If multiple targets exist, Hermes asks which one to use. If none exists, the pack keeps local safe mode on.

​
Why Slack is optional

Slack is powerful, but it should not block the product. For self-install, the pack reuses whatever Hermes already has connected. For many customers that may be Telegram or local mode at first. That is enough to start projects, use the board, run approvals, scan risk, and produce briefs.

​
Does the bot see every Slack chat?

No. A Slack bot does not magically see every workspace conversation. What it can see depends on the Slack app scopes, events, and the channels it has access to or is invited into. That is why the self-install pack does not force every buyer through custom Slack app setup.

​
Managed Slack path

White-glove/BossMode can add a managed Slack path later:
  • customer clicks an authorization link,
  • Slack OAuth grants the app permission,
  • BossMode handles event delivery and reply ingestion,
  • Hermes uses thread-bound replies as evidence.
This is the right path for teams that need real Slack chasing and inbound reply automation.

​
Safety rules

  • No external send happens without an enabled configured target.
  • Auto setup only picks a target when there is exactly one safe candidate.
  • Stable target IDs are stored for sends.
  • Ambiguous destinations require clarification.
  • Client-visible or risky sends remain approval-gated.