Make Penny University able to live outside of just one slack community.

[JnBrymn]

This will become an entire epic, but it's just for brainstorming right now and I've stuck it in this milestone so that we'll plan ahead.

How do we attack this?

• We need to set up issues for every product feature to make sure we have coverage. We might need issues for shared chunks of code too, like our models.
• We need to solidify the requirements. Like, what are the invariants that must be met so that every slack team that uses Penny is completely isolated from the other slack teams. (We'll eventually introduce new features that combine slack teams, but let's focus on strict isolation first.)
• We need a set of questions to ask as we address each feature so that we can find the places to change. Example:
  • When does the feature contact the user?
  • When does the feature read or write data to a User or Profile?
  • other questions?

[mrshwah]

Just adding a thought I had:

We need a better way of adding topic channels. Right now the only tool to do so is with a Slack command. We either need some sort of user flow to kick off in Slack when the app is added or direct them to the web app to do so.

[ghost]

Major things I can think of so far that could cause us issues:

• Separating visible chats to public chats / their privates only in the communities they're in.
• In turn with that, we'll need to keep track of:
  • The workspace originating the chat request
  • All workspaces along with the user
• Should we eventually allow multiple workspaces to "connect" for chats? Public chats to everyone for public communities?
• What do we have right this second that only functions inside Penny U? Any specific IDs that the bot works around?
• Potentially add an intro message to admins letting them know the basics to help their members. How to set topic channels, starting chats, using the web app, etc.