← Back to library

飞书 Bitable 多账号接入:按账号隔离 token 与数据表权限

问题:单账号配置难以覆盖多团队/多租户场景。做法:为每个飞书账号配置独立凭据与表访问范围,再做逐账号回归。

GITHUBDiscovered 2026-02-18Author @chuhxen
Prerequisites
  • Feishu channel/tools are enabled and you own credentials for each target account/app.
  • You can edit OpenClaw config and limit each credential to least-privilege Bitable scopes.
Steps
  1. Inventory all target Bitable tenants and map each to a dedicated credential set.
  2. Configure multi-account entries in Feishu Bitable tool settings; keep account identifiers explicit.
  3. Run create/read/update tests per account against its own table to verify no cross-tenant access.
  4. Add account-level routing rule in automation so each workflow picks the intended credential.
Commands
openclaw gateway status
openclaw gateway restart
openclaw help
Verify

Each account can only access its mapped Bitable resources and cross-account reads/writes are rejected.

Caveats
  • Exact config field names for multi-account Feishu setup may evolve before release notes are finalized(需验证).
  • Credential sprawl increases operational risk; rotate and audit keys periodically.
Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗
Visit original post