/
Future scope - Server Federation

Future scope - Server Federation

Creating a connection

We can create and accept a connection from the Connected Organisations page under the environment section.

On the add a connection button, you have two options:

  1. Create a connection

  2. Accept an invitation

Creating a connection

Only instances with an Enterprise license can create a connection with another server. Once the user clicks on Create a connection, they’re taken to the Connection Inner page:

Here they can enter/decide:

  1. Organisation name

    1. This would also be the connection name

  2. Enable DMs

    1. This would allow users to expose their DMs between connections

  3. Teams they want to share

    1. This would allow people to decide which teams to expose to the other organisation.

Team Sharing

  • The system admin can decide to share all public teams

  • Or decide to share individual teams

Once a team is shared, it automatically appears as a public team for people to join (even if it is private on the originating organisation).

Channel Sharing per team

Once a user has added a team, all channels are shared by default, but they can change that by

  1. Clicking the channels shared item on their row.

  2. Going to Edit > Channels shared

 

Once they do that, a modal pops up, allowing them to decide which channels to share.

  1. They can share all channels

  2. Channels except the selected channels

  3. Specific channels

For both 2 and 3, the input box will be a search autocomplete, allowing users to search and select channels.

The limit of channels that can be selected is unlimited.

Once done, the user can click on Save to create a connection. They get a share popup to share the code needed to accept the connection.

Accepting a connection

Only instances with an Enterprise license can accept a connection with another server. On the other end, once the user receives the invitation code, they can go to the same page and click on Accept a connection in the Add connection dropdown.

Here the user can enter the encrypted invitation code and the organisation name.

  • This would also show the things shared by the external organisation.

Connection Inner Page

This inner page is similar to the one above.

However here the user can’t either enable or disable DMs, as that would depend on the system admin that initiated the connection.

They can however decide which teams to share.

Once the user accepts/saves, the connection is made, and is displayed in the list.

Connection list page

  • Here we display the connections that the user has created/accepted.

  • Status of the connection.

  • DMs shared, and teams shared.

  • Options to See the invitation code, edit, and delete the connection.

DMs with External Connection

Once DMs are shared, the user can open the DM modal to see all members from the external organisation, with an icon that indicates that they’re from the outside.

This icon appears on the DM page as well.

Accessing Public Teams

If any teams are shared, they will appear on the public teams page, along with the icon to indicate it’s from an external organisation.

The team has an icon on the sidebar indicating that its from an external organisation.

Adding external users to a team

Users can add external users from the other organisation to a team.

  • They can be added individually.

  • Or all members can be added to the team.

  • They can be added to both public, or private teams. Even to teams that haven’t been explicitly shared in the shared connection page.

Once the user is added, the team will automatically appear on the sidebar for them.

Adding user to a channel

If the user in a team, they can now be added to a channel as well.

If the user is not in the team, and you try to add them, we will show an error message, like we show it today.

 

Related content