Secure Partner Communication

Communicate securely with partners, suppliers and customers – with Matrix federation, controlled meetings and direct VoIP calls. E2EE, clear tenant boundaries and shared project channels across organisational boundaries.

Security in collaboration

  • Clear boundaries

    Tenant isolation and clear access rules. Partners only see what is released for collaboration.

  • E2EE and compliance

    Encryption for chat and optional meetings. Support for compliance in sensitive industries.

  • Federation optional

    Matrix federation for direct exchange with partners who also use Matrix – without data via third-party servers.

Federation via Matrix: chat, channels and shared content

Matrix federation connects your Sparks instance directly with your partner’s. In shared project channels, both sides work in the same interface – with chat, shared widget content and clear access control.

Federation: shared channels across organisations with chat, files and whiteboard.

  • Federated channels across organisational boundaries

    Shared Matrix channels with partners: only invited users (yours and the partner’s) have access. No detour via public cloud services – communication runs directly between the participating Matrix servers (Synapse/tuwunel).

  • Shared widget content in the channel

    In shared project channels you use tabs and widgets as in your internal channels: shared files (e.g. via WebDAV/Nextcloud), whiteboards (Excalidraw), tasks (e.g. Planner) and embedded web content. All participants see the same content in real time – without email copies or separate tools.

  • E2EE and access control

    Matrix chat in these channels can be used with end-to-end encryption. Access control lies with the room admins: who joins the room is explicitly added. You keep control over the circle of participants.

Information exchange in meetings with participant whitelisting

Meetings with external partners remain under your control: you start meetings from chats or channels and decide who may join. The waiting room (lobby) acts as a whitelist – only participants you admit enter the meeting.

Meetings with whitelisting: from chat/channel to lobby, only admitted participants into the meeting.

  • Start a meeting from chat or channel

    Start a video meeting directly from a 1:1 chat or from a channel. Invited participants (from your organisation or the partner’s) get access – everyone else does not.

  • Lobby as whitelist

    Participants first arrive in the lobby (waiting room). As host you see who is waiting and admit only those intended for the meeting. Unwanted or unknown access is blocked.

  • Secure information exchange

    Screen sharing, whiteboard and in-meeting chat only for admitted participants. So you share confidential content specifically with partners, without third parties having access.

Direct VoIP calls with partners

Call partners directly from Sparks – by voice or video, 1:1 or in a group. No separate telephony tool, no sharing of phone numbers over insecure channels.

Direct VoIP calls: 1:1 or group, from the same chat or channel.

  • Call from chat or channel

    With one click from the chat or channel you start a voice or video call with one or more participants. Participants come from the same context (project channel, partner chat) – no random contacts.

  • WebRTC-based, no PSTN required

    VoIP over WebRTC: calls run over the internet, encrypted and without mandatory connection to the traditional phone network. Ideal for partners who also use Sparks or a compatible client.

  • One context for everything

    Chat history, shared files and calls stay together in one channel or chat. After the call you can continue writing or schedule the next meeting from the same room.

Further aspects of partner communication

From our product and architecture documentation: additional points that secure partner communication with Sparks.

  • Tenant isolation

    Your users and the partner’s can be managed in separate tenants. This keeps each organisation’s internal structure protected; only the released rooms and channels are visible to both.

  • Waiting room (lobby) and moderation

    The waiting room is a core part of Sparks meetings – not only for partner meetings but also internally. Moderators can admit participants or assign them to breakout rooms.

  • Open base: BwMessenger, Tchap, gematik

    Matrix and WebRTC are the same technical base as BwMessenger, Tchap and gematik TI-Messenger. If partners already use Matrix-based solutions, federation with Sparks is in principle possible.

  • Transparency and self-hosting

    With self-hosting or your own tenant you control server location and access. No forwarding of metadata to third parties; compliance and audit requirements are easier to meet.

Request partner solution