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 |
| Having teams shared one by one | Hard to share between teams consisting of thousands of channels and hundereds of teams | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Status | |||||||||||||||
colour | Red | title | Rejected|||||||||||||
Allowing users to share bulk teams | Easy to share a group of channels/teams directly with the shared connection |
| |||||||||||||
Allow users to choose which teams or channels to share | Even when sharing bulk teams, there still may be cases a case for smaller organisations to just share a single team, or 1-2 limited set of teams or channels |
| 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) |
| |||||||||||||
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) |
| |||||||||||||
💎 Source files
Type /link to add links to design files.