Channel workspace access

Ordinary messaging and access to a saved workspace are separate permissions. An owner must review the exact sender, conversation and saved workspace in the native app, local Command Center or terminal TUI. Signing in to a hosted remote session alone does not grant workspace access.

Connector availability

Workspace access requires a supported, authenticated incoming connection with a stable sender and conversation identity. Availability depends on the connector, its configuration and the installed release. A connector that can exchange ordinary messages may still be unable to access a workspace.

Slack, Discord, LINE, Feishu/Lark, Google Chat, Nextcloud Talk and WeCom have restricted incoming modes. Check Channel Workspaces for the current status. An unsupported or ambiguous connection is refused; it does not inherit permission from a different app, account or configuration.

Review and bind

Use the owner's Grant and Bind review to save permission and select the exact workspace. A result of permission saved, awaiting fresh provider admission means the local permission was saved. It does not mean a remote action ran or a device displayed a change.

Changing the sender, conversation or target requires the appropriate current permission. Group and topic access need their own review.

Private replies

A supported incoming connection does not necessarily provide a safe private reply path. When that path is unavailable, the channel returns only general guidance; workspace names, results and confirmation details remain in the owner controls. Use Channel Workspaces for authoritative status.

If cleanup or account changes leave synchronization blocked, contact your operator for recovery. Do not delete local storage to bypass the blocked state. Quarantined data is not automatically restored or replayed.

See Connectivity and Collaboration and Commands for supported controls. These permissions apply across native 3D, Command Center and the terminal TUI.