openclaw-multi-user-workspaces

Configures OpenClaw multi-user access with session isolation and sandboxing.

2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/TheophilusChinomona/claude-openclaw-plugin --skill openclaw-multi-user-workspaces
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-multi-user-workspaces
Source: https://github.com/TheophilusChinomona/claude-openclaw-plugin/tree/main/plugins/openclaw/skills/openclaw-multi-user-workspaces
Command: npx skills add https://github.com/TheophilusChinomona/claude-openclaw-plugin --skill openclaw-multi-user-workspaces

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables you to safely configure your OpenClaw gateway for shared use by multiple individuals, ensuring data privacy and controlled access.

Core Features & Use Cases

  • Session Isolation: Prevent users from seeing each other's conversations.
  • User Access Control: Manage who can access the gateway via pairing or allowlisting.
  • Per-User Agent Routing & Sandboxing: Assign different agents and permission levels to different users.
  • Device Pairing: Securely connect additional devices to your gateway.
  • Use Case: You want to allow your family members to use your OpenClaw gateway for specific tasks without compromising privacy or security. This Skill guides you through setting up isolated sessions and restricted access for each family member.

Quick Start

Use the openclaw-multi-user-workspaces skill to configure session isolation by setting session.dmScope to per-channel-peer.

Frequently Asked Questions about openclaw-multi-user-workspaces

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I isolate user sessions on a shared gateway?

You isolate user sessions on a shared gateway by setting `session.dmScope` to `per-channel-peer`, preventing users from seeing each other's conversations.

What is the best way to manage multi-user access control for an OpenClaw gateway?

The best way to manage multi-user access control for an OpenClaw gateway is by using device pairing and allowlisting to restrict and authenticate user connections securely.

Can I assign different agents and permissions to different users on the same gateway?

Yes, you can assign different agents and permissions to different users on the same gateway through per-user agent routing with sandboxing to control access levels.

How do I securely share my gateway with multiple users without compromising privacy?

You securely share your gateway with multiple users by configuring session isolation, user access control via allowlisting, and per-user agent routing to protect data privacy.

Does this multi-user configuration address security threats for shared deployments?

Yes, this multi-user configuration addresses security threats for shared deployments by detailing trust models, threat matrices, and OS-level hardening to protect the gateway.

When do I need OS-level hardening for my gateway deployment?

You need OS-level hardening for your gateway deployment when establishing a shared multi-user environment to properly mitigate security threats and enforce per-user sandboxing.