Allow for joining other flows in my company
Right now I can only see the flows I am a part of in my company, it would be nice to be able to see all flow names in my company and be able to join (or request to join) them if I have an interest in them.
There’s now an option to make flows joinable by everyone in the organization.
Olli Jarva commented
As Guy Fraser commented, having open group should be option, in addition to having private groups. However, with private groups, "Request invite" would be nice. We're currently thinking about using API to implement this, but that isn't perfect either: users have to go to separate service to click "Join" (and we have to handle separate authentication etc.).
Jonas Berlin commented
If you go to "Account" and then click "Company" in the left menu and scroll down, near the end you can see a list of all company flows, also flows you cannot join until invited.
Still, you cannot request to join them directly.
Guy Fraser commented
I'd be interested in this feature too.
For example, we have an "open door" Marketing flow - there's a few of us in that flow, and we don't mind others coming in, but we don't want to go round inviting people. It's sort of an optional flow for our team - those who are interested could join, those who aren't just ignore it.
Im Yammer, it's possible to discover "groups" (their equivalent of a flow) but groups can be set up as private (invite only) or public (anyone in your network can join) IIRC.
In flowdock, it might be good if we could have an "open" flow but with restrictions on who could join - eg. based on email address.
For example, we could allow customers to join our flow account, but we wouldn't want them entering internal flows.
But, imagine if there was a fully public flow that anyone could join - customers could be directed from our website straight in to that flow (especially if we could somehow do SSO to our user repository which is Crowd based, or maybe just let them use facebook/google to login?) and immediately start chatting with our team and any other customers that are in there at the time.
It would allow flowdock to be used as a service desk where customers and staff can interact. The customers would have "guest" access meaning they could only see and join certain flows marked as "public".
Then "network" flows could be open to anyone in our company (eg. restriction based on verified email address domain) and "private" flows could be invite only (which is how current flows work IIRC).
For service desk it might make more sense to have a flow per customer - eg. if they want to discuss sales enquiry or disclose confidential info we wouldn't want other customers and random people lurking around watching what's going on.