TSUMIRA CONNECT
Work with another Tsumira company through an explicit connection.
Establish an accepted company relationship, choose partner conversations and share supported work through deliberate agreements instead of opening the whole workspace.
Connect companies before sharing selected work
An accepted relationship is distinct from granting access to a whole workspace.
Working together should not require opening every internal record
A service business and its partner may need a common conversation and selected working material, while their internal operations remain separate. Tsumira Connect establishes a relationship between active Tsumira companies and supports explicitly selected partner channels and sharing. Connection, participation and resource sharing are distinct decisions. An accepted company relationship is the beginning of controlled collaboration, not universal access to the other organization.
Establish the relationship with the other company
An authorized human manager can invite another active Tsumira company by its workspace identity. The other side decides whether to accept or decline. The relationship has states and actions for disconnecting or blocking where appropriate. Check the actual company before accepting. A familiar display name is not a reason to skip the relationship decision, and a company connection is not an arbitrary external email address or a general connection to every software service.
- Company invitation and acceptance
- Authorized human management
- Explicit connection lifecycle
Choose the people and supported work deliberately
Accepted connections can support direct or group partner conversations with selected people. Supported resources may be shared through explicit agreements and applicable module authority. The sharing model can describe records, documents, lists, spaces and files, but eligibility and access depend on the actual resource and enabled module. Review the selected material and intended rights rather than assuming a customer reference, chat invitation or connected company has shared the full underlying graph automatically.
- Selected partner conversation audience
- Explicit supported-resource agreements
- Module-specific sharing eligibility
Review the actual sharing agreement
Partner collaboration is selective; it is not universal cross-company synchronisation.
- Participants
- Chosen partner members
- Scope
- Explicit sharing agreement
Partner collaboration is selective; it is not universal cross-company synchronisation.
Keep ongoing access and local history understandable
Current relationship and participant authority are checked for partner conversation operations. Sharing has its own state and conflict or synchronization context; it should not be marketed as unlimited universal cross-company synchronization. Leaving a channel removes the live participation while local history can remain retained. Disconnecting is not a claim that every piece of material already received elsewhere has been erased. Review the actual relationship and resource state when work ends.
- Current connection and participant checks
- Resource-specific sharing state
- Live access separate from retained history
A concrete workflow
Verify the partner company
Identify the intended active Tsumira workspace and send the relationship invitation through authorized management.
Accept deliberately
The other company reviews the invitation before accepting the connection.
Choose the collaboration scope
Select the partner people, channel and supported material that the joint work needs.
Maintain or end the relationship
Review access and sharing state as the work changes and use the appropriate leave, disconnect or block action.
An illustrative working example
Illustrative workflow: a service business and its delivery partner
Two Tsumira companies agree to collaborate on delivery. Their authorized managers establish the connection. A selected group channel includes the people doing the work, and the teams review which supported working material should be shared. Internal records outside that scope stay within their own authority. At the end, the companies review the relationship and resource states rather than assuming that ending participation destroys all previously retained conversation history.
Questions about this topic
Can I connect any external email address this way?
This function concerns accepted relationships between active Tsumira companies. It is not a universal external-email invitation or a connection to every third-party service.
Does acceptance share the entire workspace?
No. Connection, channel participation and supported resource sharing are separate, explicit decisions with their own authority.
Can an AI identity send partner messages as a person?
The implemented partner-message path checks an active human author. Do not infer unrestricted AI sending across company boundaries.
Does leaving erase everything the partner already received?
No such claim is made. Leaving and disconnection affect current participation or relationship; local history and previously received material require their own handling.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Slack
Workflow concept: Plan a partner communication boundary without granting access to every internal record.
Microsoft Teams
Workflow concept: Review shared-project context before opening a cross-company discussion.
SharePoint Online (v2)
Workflow concept: Identify the exact partner material that needs an explicit sharing agreement.