Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Next »

  1. What assets do we want to share in the future when creating a connection?

    1. Teams

    2. Channels

    3. Emojis

    4. Playbooks

    5. Plugins

  2. What happens when one server is outdated or has features the other server does not? i.e. calls, or plugins.

    1. Do we generate the posts? Like if a person initials a call, or a zoom call in a channel, do we show it for members of the other org, even if they don’t have access to them?

  3. For the MVP, do we want to allow public team sharing?

  4. For the MVP, do we want to allow DMs?

  5. Do we allow people users to control what the other server is sharing with them?

    1. Server A shared 2 teams.

    2. Can server B decide to only accept 1 team?

  6. If server A initiated a connection by sharing their DMs, can server B reject the request to share DMs? And keep DMs closed?

  7. How does MS teams integration play into this? Can we incorporate that flow here as well?

  8. This is a very specific case for P1, most other platforms allow you to share a channel, rather than opening up a whole team. Should we consider developer a more general usecase for this feature so it’s applicable to general users of our platform. This would mean having the following features:

    1. Allowing you to share specific channels

    2. Allowing you to have control

  • No labels