Back to changelog
platformteams

Team Members, Multi-Org Support, and Per-Member Telegram Access

EcomClaw is no longer a single-player tool. Brands have teams, and agencies manage multiple brands. This update brings proper multi-user and multi-org support so everyone on your team can work with your agent directly.

Team Members

You can now invite team members from Settings > Team. Enter their email, pick a role, and they get an invitation link.

Three roles control what each person can do:

  • Owner — Full control. Manage billing, destroy instances, invite and remove members.
  • Admin — Same as owner, minus ownership transfer. Good for ops leads and senior team members.
  • Member — Can view the dashboard, settings, and interact with the agent. Cannot make destructive changes.

Pending invitations expire after 7 days. Owners and admins can cancel them or resend.

Multi-Organization Support

If you manage multiple brands, you no longer need separate accounts. One login, multiple organizations. Each org gets its own:

  • Dedicated OpenClaw instance on Fly.io
  • Separate subscription and billing
  • Independent onboarding and integrations
  • Isolated agent memory and workspace

Switch between orgs from the sidebar. Create a new org anytime from Settings > New Organization.

Per-Member Telegram Access

Previously, only the account owner could message the agent on Telegram. Now every team member can connect their own Telegram account and chat with the bot directly.

When a member saves their Telegram ID, we automatically sync the full team's allowlist to your bot. The bot restarts with the updated list — only your team members can message it. When someone is removed from the team, their access is revoked on the next sync.

How to Set Up Telegram Access

Each team member follows these steps:

  1. Find your Telegram user ID. Open Telegram and message @userinfobot. It will reply with your numeric user ID (e.g. 123456789).
  2. Go to Settings. In EcomClaw, navigate to Settings > General. Scroll down to the Telegram Access card (visible when your instance is running).
  3. Paste your user ID. Enter the numeric ID in the input field and click Save.
  4. Wait for the bot to restart. Your bot will automatically restart to apply the updated allowlist. This takes about 30 seconds.
  5. Message the bot. Open your Telegram chat with the bot and send a message. You should get a response.

That's it. Each team member repeats this independently — no owner intervention needed. To revoke your own access, clear the field and save.

Improvements

  • Allowlist sync is idempotent — rapid saves won't trigger duplicate restarts
  • Legacy owner Telegram ID from onboarding is preserved and merged into the team allowlist
  • Member removal automatically triggers an allowlist sync as a safety net