command-access-control

Restrict Hermes commands by configuring tiered access control that separates admins, limited users, and everyone else. This enforces different command permissions and blocks risky file or shell operations outside approved per-user directories.

Yes, you can grant model switching permissions to a user while keeping terminal execution, config changes, and dangerous filesystem actions blocked. This is achieved through tiered command permissions and safe configuration handling.

Secure API keys by migrating them into .env files. The access control setup includes operational guardrails for safe configuration handling, preventing configuration abuse while allowing secure model and provider management.

Enforce workspace jails by applying pre-command hook validation and session directory injection. This blocks risky file and shell operations outside approved per-user directories, ensuring safe multi-user deployments.

Yes, pre-command hook validation is required. It restricts Hermes commands by user identity, workspace, and command class to prevent unauthorized administration and dangerous shell actions across multi-user deployments.

Avoid YAML editing pitfalls and ensure proper restart and validation steps. The setup includes operational guardrails for multi-user deployments, requiring safe configuration handling for models, providers, and API keys to prevent abuse.