Decision | Reason | Status | Next steps |
|---|---|---|---|
Having channels shared on a one by one basis | Hard to share between teams consisting of thousands of channels and hundereds of teams | REJECTED | |
Having teams shared one by one | Hard to share between teams consisting of thousands of channels and hundereds of teams | REJECTED | |
Allowing users to share bulk teams | Easy to share a group of channels/teams directly with the shared connection | APPROVED | |
Allow users to choose which channels to share | Even when sharing bulk teams, there still may be cases for smaller organisations to just share a single team, or 1-2 channels | EXPLORATION | Explore in V2 |
Allow all members to decide who to invite to teams/channels | This would enable seamless communication between two trusted connections, as the end users don’t want system admin bottlenecks (which is the intended experience for the customer) | APPROVED | |
Allow shared DMs | This allows people in both orgs to talk to each other, like they would if the organisations were connected (which is the intended experience for the customer) | APPROVED | |
💎 Source files
Type /link to add links to design files.