Separate Manual and Rule-Based Cross-Workspace Moves

Currently, the "Allow conversations to be moved to all inboxes" setting controls both:

• Manual moves performed by users

• Automated moves performed by Rules

This creates an unnecessary trade-off.

Use case: Many organisations use separate Workspaces to segregate teams, permissions, and sensitive communications. To prevent staff from accidentally moving conversations into the wrong Workspace, the global move setting is disabled.

However, disabling this setting also prevents legitimate automation Rules from routing conversations between Workspaces.

Example:

• A conversation arrives in a general support inbox.

• A Rule identifies it as belonging to a specialist or restricted team.

• The Rule should automatically move it to the appropriate inbox in another Workspace.

• The Rule fails because cross-workspace moves are disabled globally.

Proposed enhancement: Separate manual and automated move permissions, for example:

• ✅ Allow Rule-based cross-workspace moves

• ❌ Allow manual cross-workspace moves

Benefits:

• Prevents accidental user moves between Workspaces

• Preserves Workspace boundaries and governance

• Enables automated routing to the correct teams

• Removes the need for workaround solutions such as forwarding rules

This would give administrators much finer control over Workspace management while still allowing automation to do its job.