Flow: Files & Assets
File handling in Flow
As the sole product designer on Flow, it was my responsibility to carve out the look and feel for these pages, as well as solve our UX problems.
File Management Issues
Flows core purpose is to streamline and unite engineering workflows, which includes bringing all of a users working files together in one place.
Dedicated File Management
In Flow, files were initially displayed on the sidebar. We fixed this by creating pages around file management, as well as building out Dropbox, Google Drive, and SharePoint integrations
User Needs
- Make file mgmt feel more accessible and intuitive on Flow
- Create nested file pages within the PBS and TL
- Implement versioning and user permissions
Scope
The Files and Assets pages provided another way to track progress on a product or deliverable. Versioning was implemented by having the file version synced with the last time it was updated on Dropbox, Google Drive, or SharePoint, and creating a version history backlog that users with permission could roll back to at any point. We created three groups for permissions at feature launch: Primary Stakeholders, typically your engineering leads and project managers, who would have unrestricted access to an entire product tree; Contributors, who would have a unique set of permissions within a tree granted by primary stakeholders; and viewers, who could only do as their name implies.
Main Files and Assets page showing file organization and versioning
Version Control
Automatic syncing with cloud storage platforms ensures teams always work with the latest file versions.
Permission System
Role-based access ensures only primary stakeholders can manage all versions while team members access current files.
Cloud Integration
Seamless integration with Dropbox, Google Drive, and SharePoint for unified file management.
“Work in progress view” with enhanced file management features
Outcome
The Files and Assets page provided a new way for users to experience their content more matter-of-factly without the view of the timeline. Direct feedback from one customer said that the versioning system and versioning permissions saved lots of time and meta work on their part.