Flowdock Flows

A flow is like a team room. Each flow consists of a chat and a team inbox. We recommend that you create a flow for each team. For example, your company has three teams working on different projects. Each team would have their own flows (such as Web Team, Mobile Team, and Marketing and Sales). You could also have a company-wide flow for company-level discussions.

CA Flowdock consists of three parts:

  1. The flow sidebar is a list of your open flows and private conversations. The currently selected flow or private conversation is highlighted.
  2. The chat contains the discussions of the selected flow or private conversation.
  3. The team inbox displays an activity stream from the tools and services that you have integrated with the selected flow. It also displays search results. The team inbox can be toggled from the Inbox button in the top right.

Flow recommendations

Keep it simple. Start with one flow for each team. In addition to team flows, you can create flows for cross-functional projects (for example, Mobile Development) and location or business unit-specific flows(for example, Denver Office and Marketing). Other flow examples include Non-Work, All Employees, Build Status, and Volunteering.

By defaulting to open flows, members of your organization have an efficient way of collaborating or solving problems across the company. Use invite-only flows for teams that may need to keep information secure, such as human resources or legal.

Feedback

Need more help? The CA Agile Central Community is your one-stop shop for self-service and support. To submit feedback or cases to CA Agile Central Support, find answers, and collaborate with others, please join us in the CA Agile Central Community.