Skip to content

docs(messaging): clarify admin/user split and signal future gating#27623

Merged
teknium1 merged 1 commit into
mainfrom
hermes/hermes-22adc932
May 17, 2026
Merged

docs(messaging): clarify admin/user split and signal future gating#27623
teknium1 merged 1 commit into
mainfrom
hermes/hermes-22adc932

Conversation

@teknium1

Copy link
Copy Markdown
Contributor

Summary

Restructures the messaging security section so the admin/user distinction reads as a first-class concept rather than buried under "Slash Command Access Control."

Changes

  • website/docs/user-guide/messaging/index.md: rename the section to Admins vs Regular Users, lead with what the tiers mean, then call out:
    • Slash commands are the first capability gated by the tier split today.
    • Future gating (tools, model switching, expensive ops) will hang off the same admin/user distinction — so configuring it now is forward-compatible.
    • Allowlists ("can they reach the bot?") vs admin/user split ("what can they do?") contrasted up front.
  • Anchor changes: #slash-command-access-control -> #admins-vs-regular-users on the index page. Platform pages (telegram.md, discord.md) keep their existing #slash-command-access-control headings since slash gating IS the only thing they currently gate, and the cross-link from the index page still points at those.

Test plan

  • Diff review of the markdown — no other docs files reference the renamed anchor.
  • Platform-page cross-links unchanged and still resolve to existing headings.

Restructures the security section so the admin/user distinction is a
first-class concept rather than buried under 'Slash Command Access
Control'. The new section makes explicit that:

- Slash commands are the first capability gated by the tier split today
- Future gating (tools, model switching, etc.) will hang off the same
  admin/user distinction, so configuring it now is forward-compatible
- Allowlists vs the admin/user split solve different problems and are
  contrasted up front

Heading renamed: 'Slash Command Access Control' -> 'Admins vs Regular
Users'. The platform-specific pages (telegram.md, discord.md) keep the
old heading since slash gating IS the only thing they currently gate.
@teknium1 teknium1 merged commit 4c46c35 into main May 17, 2026
8 checks passed
@teknium1 teknium1 deleted the hermes/hermes-22adc932 branch May 17, 2026 21:44
@alt-glitch alt-glitch added type/docs Documentation improvements P3 Low — cosmetic, nice to have comp/gateway Gateway runner, session dispatch, delivery labels May 17, 2026
gweeteve pushed a commit to gweeteve/hermes-agent that referenced this pull request Jun 2, 2026
…ousResearch#27623)

Restructures the security section so the admin/user distinction is a
first-class concept rather than buried under 'Slash Command Access
Control'. The new section makes explicit that:

- Slash commands are the first capability gated by the tier split today
- Future gating (tools, model switching, etc.) will hang off the same
  admin/user distinction, so configuring it now is forward-compatible
- Allowlists vs the admin/user split solve different problems and are
  contrasted up front

Heading renamed: 'Slash Command Access Control' -> 'Admins vs Regular
Users'. The platform-specific pages (telegram.md, discord.md) keep the
old heading since slash gating IS the only thing they currently gate.
Seven74AI pushed a commit to Seven74AI/hermes-agent that referenced this pull request Jun 13, 2026
…ousResearch#27623)

Restructures the security section so the admin/user distinction is a
first-class concept rather than buried under 'Slash Command Access
Control'. The new section makes explicit that:

- Slash commands are the first capability gated by the tier split today
- Future gating (tools, model switching, etc.) will hang off the same
  admin/user distinction, so configuring it now is forward-compatible
- Allowlists vs the admin/user split solve different problems and are
  contrasted up front

Heading renamed: 'Slash Command Access Control' -> 'Admins vs Regular
Users'. The platform-specific pages (telegram.md, discord.md) keep the
old heading since slash gating IS the only thing they currently gate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/gateway Gateway runner, session dispatch, delivery P3 Low — cosmetic, nice to have type/docs Documentation improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants