How to configure the system so that only administrators can restart the gateway, while others cannot | Friends of the Crustacean 🦞🤝 | Page 1

chilly rampart Apr 24, 2026, 1:50 AM

#

How to configure the system so that only administrators can restart the gateway, while others cannot?

golden spindleBOT Apr 24, 2026, 1:50 AM

#

plucky falconBOT Apr 24, 2026, 1:50 AM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

golden spindleBOT Apr 24, 2026, 1:50 AM

#

fast vaporBOT Apr 24, 2026, 1:53 AM

#

Let me verify the exact auth/permission model in the docs/code so I don't hand-wave this.

#

There isn’t a separate per-command “admins can /restart, others can’t” RBAC layer right now.

What is supported:

Disable chat restarts entirely

{
  commands: {
    restart: false
  }
}

Restrict command access to admin IDs only

#

  commands: {
    restart: true,
    allowFrom: {
      discord: [
        "user:123456789012345678",
        "user:234567890123456789"
      ]
    }
  }
}

Or set explicit owners:

#

  commands: {
    ownerAllowFrom: [
      "discord:123456789012345678"
    ]
  }
}

Important caveat: commands.allowFrom is broader than just /restart, it controls command/directive authorization generally. So if you need fine-grained per-command roles, OpenClaw does not currently expose that as a separate config.

Also, treat gateway.auth.token / password as full admin credentials. Anyone with those is effectively an operator.

Docs:

#How to configure the system so that only administrators can restart the gateway, while others cannot