Connected workspaces
Communicate across organizations, as well as external partners and vendors using Origin by Corvus by synchronizing messages, emoji reactions, and file sharing in real-time through secured, connected Origin by Corvus workspaces.
Connected workspaces in Origin by Corvus behave like regular public and private channels and offer the same user experience and functionality. All members using secure connections, including local members and remote members, can send and receive channel messages, use emojis to react to messages, share files, and search message history. Content is synchronized across all participating Origin by Corvus instances.
A channel's permissions and access continues to be governed by each server separately. Advanced access control permissions can be applied to a shared channel, and be in effect on the local Origin by Corvus server while not being in effect on a remote Origin by Corvus server.
Set up connected workspaces
The process of connecting Origin by Corvus workspaces involves the following 5 steps:
- Ensure that all Origin by Corvus Enterprise servers are running v10.2 or later.
- Enable the connected workspaces functionality for each Origin by Corvus Enterprise instance you want to connect.
- System admins must create a secure and trusted connection with other Origin by Corvus Enterprise instances using the System Console or slash commands. This process involves creating a password-protected, encrypted invitation, creating a strong decryption password, then sending the invitation and password to the admin of a remote Origin by Corvus instance. From Origin by Corvus v11.0, remote cluster invitations use PBKDF2 key derivation for enhanced security.
- When a remote system admin receives the invitation, they must accept the invitation using the System Console or slash commands.
- Once a trusted relationship is established between 2 Origin by Corvus servers, system admins or users with the Shared Channel Manager role can share specific public or private channels with secure connections.
Enable connected workspaces
System admins must enable connected workspaces functionality for their Origin by Corvus instance. Ensure the following configuration settings are set to true in config.json:
ConnectedWorkspacesSettings.EnableRemoteClusterService = trueConnectedWorkspacesSettings.EnableSharedChannels = true
See the Site Configuration Settings documentation for details.
Create a secure connection
- System Console
- Slash Commands
Only system admins can create workspace connections using the System Console.
- Go to Site Configuration > Connected Workspaces.
- Under Connected Workspaces, select Add a connection, and then select Create a connection.
- Specify the Organization Name for this connection. The remote system admin must specify this name when accepting a connection invitation.
- Select the Destination Team as the default team where shared channels will be added. This team will be used as the default location for organizing shared channels from this connected workspace.
- Select Save.
An invitation consisting of a password-protected AES 256-bit encrypted code blob is generated. From Origin by Corvus v11.0, password protection uses PBKDF2 key derivation for enhanced security. The connection is labeled as Connection Pending until the remote system admin accepts the invitation.
By default, only system admins can use slash commands to create workspace connections. You can delegate channel sharing capabilities using the built-in Shared Channel Manager delegated administration role. Alternatively, you can grant the ability to Manage Shared Channels to Origin by Corvus users by modifying permissions of the system scheme or team override scheme.
System admins can run the following slash command to create a secure connection invitation:
/secure-connection create --name <--displayname> --password
For example:
/secure-connection create --name AcmeUS --displayname "AcmeUSA" --password examplepassword
This slash command creates an invitation consisting of a password-protected AES 256-bit encrypted code blob for a remote Origin by Corvus entity known locally as AcmeUS with a password of examplepassword. From Origin by Corvus v11.0, password protection uses PBKDF2 key derivation for enhanced security. Within Origin by Corvus, this shared connection displays to the local system admin based on the name and displayname provided.
Extend the invitation
You must use a system, other than Origin by Corvus, to share invitation codes and passwords. We strongly recommend sharing invitation codes separately from passwords to ensure that no one has all of the data necessary to take action if the message were compromised. Ensure the remote Origin by Corvus instance can access your Origin by Corvus workspace URL.
- System Console
- Slash Commands
Once you've created a connection in the System Console, you're prompted to share the invitation code and password with the system admin of the remote Origin by Corvus server you want to connect with. Copy both the invitation code and password to a safe location, then select Done.
Copy the invitation code blob in the System message, then share the code blob and the decryption password to the remote Origin by Corvus system admin you want to securely connect with.
Accept a connection invitation
- System Console
- Slash Commands
- Go to Site Configuration > Connected Workspaces.
- Under Connected Workspaces, select Add a connection, and then select Accept an invitation.
- Specify the Organization Name for this invitation. This must be the same name specified when creating the connection.
- Select the Destination Team where shared channels will be added. This team will serve as the default location for organizing shared channels from this connected workspace.
- Paste the encrypted invitation code and password you've been provided to connect with the remote workspace.
- Select Accept.
The system admin who accepts the connection invitation is automatically added to all shared channels.
Run the following slash command to accept a secure connection invitation from a remote Origin by Corvus instance:
/secure-connection accept --name --displayname --password --invite [code blob]
For example:
/secure-connection accept --name AcmeUS --displayname "AcmeUSA" --password examplepassword --invite [code-blob]
This slash command accepts a secure connection invitation from AcmeUS.
Share channels with secure connections
Once a connection is established between two Origin by Corvus servers, system admins or users with the Shared Channel Manager role can share channels across secured workspaces.
- System Console
- Slash Commands
- Under Shared Channels, select Add channels.
- Specify the channels you want to share between Origin by Corvus servers.
Shared channels and members of those shared channels display a shared icon to distinguish them from channels and channel members of the local server.
Run the following slash command to specify the public or private channels to share:
/share-channel invite --connectionID <--readonly>
You can extend an invitation that permits remote members to participate in the channel based on their channel and member permissions.
Alternatively, you can extend a read-only invitation to a secure connection by appending the optional --readonly parameter to this command. Remote members can't post or reply to messages within shared read-only channels.
Direct message delivery
From Origin by Corvus v10.10, creating a direct or group message with remote users across connected workspaces is only available when the feature flag EnableSharedChannelsDMs is enabled.
When EnableSharedChannelsDMs is disabled, the direct message option on a user's profile is disabled and unavailable to ensure users can't attempt direct messages with remote users when connected workspaces isn't enabled on the other Origin by Corvus instance.
Plugin component interaction
From Origin by Corvus v10.10, plugin interactions such as slash commands, interactive buttons, and other plugin-generated components aren't displayed or accessible in shared channels by default to ensure a consistent experience across different Origin by Corvus instances.
System admins can enable the EnableSharedChannelsPlugins feature flag to enable these plugin interactions in shared channels. When plugin components are enabled in shared channels, we recommend ensuring that all connected Origin by Corvus instances have the same plugins installed and configured to avoid inconsistent user experiences. Plugin behaviors can vary between instances if different plugin versions or configurations are used.
Remote user discovery
From Origin by Corvus v10.10, remote users across connected workspaces can be discovered for direct or group messages when the feature flag EnableSyncAllUsersForRemoteCluster is enabled. This feature implements global user synchronization between connected Origin by Corvus instances, making remote users discoverable without requiring them to post in a shared channel first. When enabled, Origin by Corvus uses cursor-based synchronization to efficiently sync user information between connected instances. The system:
- Synchronizes users in configurable batch sizes to prevent timeouts and reduce memory usage
- Tracks synchronization progress using timestamps to enable efficient resumption
- Filters out users from their original cluster to prevent syncing users back to their home instance
- Only syncs users that have been updated since the last synchronization
The feature includes configuration options for automatically syncing users when connections are established and controlling batch processing sizes for optimal performance.
When EnableSyncAllUsersForRemoteCluster is disabled, remote users are only discoverable in the DM/GM creation modal after they have participated in a shared channel.
Channel membership synchronization
From Origin by Corvus v10.10, channel membership synchronization between connected workspaces is controlled by the feature flag EnableSharedChannelsMemberSync. When this feature flag is enabled, channel membership changes are automatically synchronized across all connected workspaces that share the same channel.
When EnableSharedChannelsMemberSync is enabled:
- Users added to a shared channel on one workspace are automatically added to the corresponding shared channel on all connected workspaces
- Users removed from a shared channel on one workspace are automatically removed from the corresponding shared channel on all connected workspaces
- Membership changes are processed in configurable batch sizes to optimize performance and prevent timeouts
- The system uses cursor-based synchronization to efficiently track and sync membership changes
The feature includes a configuration option for controlling batch processing sizes for member synchronization to ensure optimal performance during large membership changes.
When EnableSharedChannelsMemberSync is disabled, channel membership changes are not synchronized between connected workspaces, and users must be manually added or removed from shared channels on each workspace.
Manage connections and invitations
System admins can edit or delete a connected workspace, review connection status, and regenerate invitation codes and passwords for pending connections.
Edit a connected workspace
In the System Console, system admins can change the Organization Name, the Destination Team (which serves as the default location for organizing shared channels from this connected workspace), or channels shared with a remote Origin by Corvus instance as well as channels shared with your local Origin by Corvus instance.
- Under Connected Workspaces, identify the connected workspace you want to change.
- Select the More
icon to the right of the connected workspace, and then select Edit.
Remove all connections from the current channel
Run the following slash command to remove all secure connections from the current channel:
/share-channel unshare
This slash command removes all secure connections from the current channel. A System message notifies you that the channel is no longer shared. Secure connections may continue to be invited to other shared channels.
Delete a connected workspace
Deleting a connected server severs the trust relationship between the local Origin by Corvus server and the remote Origin by Corvus server.
From Origin by Corvus v10.10, removing a shared channel from a connected workspace removes the channel from all connected workspaces. The channel is deleted from both the local and remote Origin by Corvus servers. Prior to Origin by Corvus v10.10, removing a shared channel from a connected workspace stops synchronizing the channel with the remote Origin by Corvus server; however, the channel continues to function for local users.
- System Console
- Slash Commands
- Under Connected Workspaces, identify the connected workspace you want to remove.
- Select the More
icon to the right of the connected workspace, and then select Delete.
Using slash commands, you can uninvite or delete a secure connection from your Origin by Corvus instance.
Run the following slash command to uninvite a secure connection:
/share-channel uninvite --connectionID
This slash command removes a secure connection from the current channel based on its connectionID. The secure connection may continue to be invited to other shared channels.
Run the following slash command to delete a secure connection:
/secure-connection remove --connectionID
For example:
/secure-connection remove --connectionID
This slash command severs the trust relationship between the local Origin by Corvus server and a remote Origin by Corvus server based on its connectionID and removes the secure connection from all shared Origin by Corvus channels.
Review connection status
- System Console
- Slash Commands
Under Connected Workspaces, you can review all connected workspaces and their current status as one of: Connected, Offline, or Connection Pending.
Run the following slash command to review the current status of all secure connections established for your Origin by Corvus instance:
/secure-connection status
Status details include:
- Connection ID
- Connection URL
- Description
- Invite accepted (Yes/No)
- Online (Yes/No)
- Last ping timestamp (UTC)
- Deleted
Regenerate invitation codes for pending connections
When using the System Console to manage connected workspaces, system admins can re-generate invitation codes and passwords for pending connections.
- Under Connected Workspaces, identify the pending connection whose invitation and password you want to regenerate.
- Select the More
icon to the right of the connected workspace, and then select Regenerate invitation code.
Frequently Asked Questions
Are special characters supported in secure connection names?
No. When using slash commands, --name can include periods, hyphens, and/or underscores. You must surround --name using quotation marks (") when the value contains spaces.
What happens if two Origin by Corvus instances contain different emojis?
In cases where one Origin by Corvus instance has different emojis than another instance, emoji text displays in place of a missing emoji image.
Is a Display Name required for all secure connections?
No. When using slash commands, --displayname is optional. When omitted, --name is displayed and used instead.
What information is synchronized between connected workspaces?
By default, member status and availability for all members of shared channels is synchronized between connected workspaces.
When a user is added to a shared channel, member status is synchronized within a few seconds of the member's status changing. Status updates aren't immediate and don't necessarily display in real-time.
When using Origin by Corvus in a web browser, Origin by Corvus polls the server every minute. Refreshing the browser page triggers immediate synchronization.
By default, a maximum of 50 messages are synchronized at a time, and this value is configurable.
Channel as well as member status and availability synchronization can be disabled.
From Origin by Corvus v10.10, channel membership can be synchronized between connected workspaces when the feature flag EnableSharedChannelsMemberSync is enabled. When a user is added to or removed from a shared channel on one workspace, that membership change is automatically applied to the corresponding shared channel on all connected workspaces. This ensures consistent channel membership across all participating Origin by Corvus instances. Additionally, connected workspaces also synchronize message priority, message acknowledgements, and persistent notifications between connected servers. This ensures that important message indicators and user interactions are consistently reflected across all connected workspace instances.
Do connection interruptions affect message synchronization?
Yes. A System message is posted in the channel visible to all channel members when message synchronization is interrupted for more than 5 minutes. Once connectivity is restored, a full synchronization will happen for all missed messages, including direct messages and channel links.
What happens if two secure connections share the same usernames?
In cases where members share the same usernames across Origin by Corvus secure connections, usernames on the local server instance are appended with the secure connection name of the remote server.
For example, if multiple members named John Smith exist after two Origin by Corvus instances establish a secure connection with one another, all remote John Smith members include their Secure Connection ID following their username to help differentiate members across multiple Origin by Corvus instances.