This could be our golden opportunity to introduce external clients to a network. "Flowy Labs - Support" could be a network and people can either "post" to the network publicly sort of like a forum, or directly to a Flowy Labs team member. They cannot see other external members.
Need to think Slack connect, and whether we want to not only add external guests by email but associate guests to other networks or organization name. This would provide a natural grouping for communication and artifacts between. However, would this require this client to create their own network? Or if they do have their own network, then it can be associated with it calculated?
We must break down this problem, and may have to implement something simple for now. without expanding scope and complexity in pricing, usage, etc.
For feedback, issues, and more.
This could be our golden opportunity to introduce `external clients` to a network. "Flowy Labs - Support" could be a network and people can either "post" to the network publicly sort of like a forum, or directly to a Flowy Labs team member. They cannot see other external members.
- Need to think Slack connect, and whether we want to not only add external guests by email but associate guests to other networks or organization name. This would provide a natural grouping for communication and artifacts between. However, would this require this client to create their own network? Or if they do have their own network, then it can be associated with it calculated?
We must break down this problem, and may have to implement something simple for now. without expanding scope and complexity in pricing, usage, etc.
For now, we have implemented a simple support method: 28b1ff542b
We can revisit this. Is it a paper cut, yes. But we can ship and solve this later when we have the puzzle pieces laid out. It's okay for a PLG startup to not worry about this yet.
For now, we have implemented a simple support method: 28b1ff542b2a
We can revisit this. Is it a paper cut, yes. But we can ship and solve this later when we have the puzzle pieces laid out. It's okay for a PLG startup to not worry about this yet.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
For feedback, issues, and more.
This could be our golden opportunity to introduce
external clientsto a network. "Flowy Labs - Support" could be a network and people can either "post" to the network publicly sort of like a forum, or directly to a Flowy Labs team member. They cannot see other external members.We must break down this problem, and may have to implement something simple for now. without expanding scope and complexity in pricing, usage, etc.
For now, we have implemented a simple support method:
28b1ff542bWe can revisit this. Is it a paper cut, yes. But we can ship and solve this later when we have the puzzle pieces laid out. It's okay for a PLG startup to not worry about this yet.