FundSvcs Community

 View Only
  • 1.  File storage structure/ document storage

    Posted 07-18-2023 03:10 PM

    Hello everyone,

    My team is looking for recommendations on how to organize a complex file structure for grant document storage in an affiliated organization. We are seeking the ability to have grant writing staff, program staff, and leadership from multiple affiliates be able to view and collaborate on grant applications, but making it so staff don't have the permission to delete others' work. 

    Can anyone chime in with their experience with a complex file structure system and permissions system? Thank you!



    ------------------------------
    Leslie Proudfoot
    GRID Alternatives
    lproudfoot@gridalternatives.org
    ------------------------------


  • 2.  RE: File storage structure/ document storage

    Posted 07-20-2023 08:14 AM
    Leslie, can you explain your use-case in more detail? Is it possible that you need a document approval workflow tool, rather than a different type of editing tool?

    Generally, collaborative editing applications allow for comments (alongside the text), suggestions (in-text edits on a draft mode) and full edits, and provide permissions settings for those types of edits. They will also have a revision system that allows you to revert a document to act previous version. 

    Those features are typically sufficient to deal with collaborative editing, but they don't communicate things like the status of a document, and they don't capture approvals. Something like Filestage.io might be a good fit for your case. With other clients we've also developed workflow management tools for grant application development in PM tools like Sortable. 


    Isaac Shalev
    Data Strategy Expert
    (917) 859-0151
    isaac@sage70.com

    Autocorrect was used in composting this email, please excuse any typos





  • 3.  RE: File storage structure/ document storage

    Posted 07-20-2023 09:09 AM

    Hi Isaac, of course.

    Currently my organization has both Google Drive and Microsoft Teams for document storage and collaboration. Collaboration is very easy in Google Drive, but managing the file system and permissions is not so robust. My organization has been using Google Drive for many years, and the file system that existed has become quite disorganized. Everyone on the Development team can share editing access with others, when staff leave the organization their files get lost, new staff don't understand the file paths or how to get to documents, it's not easy to QC to make sure documents are stored on this system (instead of on their desktops), no one can find each other's files, and it's possible to delete other's work, etc. 

    Our organization got Microsoft Teams around 3 years ago but the Development team did not adopt it at that time. The learning curve is slightly higher than Google Drive, and the rollout/ training process was not very thorough, so we didn't gravitate towards it. Now, my Development team is looking at Microsoft Teams as an alternative to the Google Drive system that has gotten disorganized. My Development Operations team believes that Microsoft Teams is a more sustainable approach to file organization than Google Drive. The main thing we like about it is that Microsoft Teams and Salesforce can be connected. Our idea is to make it so every time a grant record is created in Salesforce, it automatically creates a set of folders in Microsoft Teams for each document (grant application/ award letter, etc.). We believe this will help with consistency of file storage. The main issue we have with this system is permissions. We want to make it so 1.) members of the grant team, as identified by the lead grant writer, can collaborate, 2.) everyone who writes grants can have-view only access across the board, and 3.) no one can delete or edit other's work without permission from the lead grant writer. We have around 20 Development staff, plus around 30 program staff and leadership who collaborate with development to write grants. The grant teams are fluid depending on what the grant is, so we don't have a precise designation of "who the grant team is", including cases where the lead grant writer is actually NOT on the Development team. 

    We are wondering if any other folks have experience with a medium to large organization where there are multiple grant writers and grant teams who want to collaborate and share information. Can you share how your file system is organized? Can you share documents, policies, or standards for how your teams organize files and collaborate on grants or major partnerships? Thank you for any thoughts!

    Leslie



    ------------------------------
    Leslie Proudfoot
    GRID Alternatives
    lproudfoot@gridalternatives.org
    ------------------------------



  • 4.  RE: File storage structure/ document storage

    Posted 07-20-2023 12:29 PM

    Leslie, thanks for elaborating. Drive and Sharepoint/Teams both support file-level and folder-level permissions that would allow you to do what you're describing, but it will be painful to keep up with your fluid teams and grant lead roles. My advice is to reconsider the tool you're using to solve the problem, and to re-ask the question. Why do controls need to be so tight? The problem you're describing - people deleting other people's work and editing docs they shouldn't be editing - suggests a problem of role clarity and uncertainty over process. Locking down editing rights doesn't address those underlying issues, and introduces friction that can lead folks to workarounds. At one client who tried this lockdown approach, a certain senior administrator who was a major culprit took to downloading the documents, making edits, and emailing them to the whole team. 

    In terms of best practices for a grant shop like yours, aside from the permissions issue, focus on training to use the 'comments' and  'suggested edit' or 'tracked changes' modes, and to show users how to access and restore previous versions of a document, so they do not fear losing their doc or having their progress undone by an unauthorized edit. Leverage your CRM or PM software to track grant development, assign tasks and roles to users, and use its file library features to define metadata about the documents themselves. Users should access documents from there, and not through the file system. A file system is a very low-context interface, and folks have to remember how to "get to" a file based on some multi-step navigation. It's far better to go to the grant application record in your CRM, click over to the file tab, and see each file, what type it is (LOI, budget, narrative, etc.), what stage it's in (early draft, late draft, final, etc.), who is assigned to work on it, what the next action is, when it's due, etc. Yes, the file is still stored somewhere in the file system, but the folder structure can be much simpler - you're not depending on the location of the file in the folder tree to define what the file is. 



    Thank you,
    Isaac Shalev
    Data Strategy Expert
    Sage70, Inc.
    (917) 859-0151
    isaac@sage70.com

    Schedule a 30-minute consultation now:







  • 5.  RE: File storage structure/ document storage

    Posted 07-25-2023 03:55 PM

    @Zoe Carr

    Thanks for that thorough response, Isaac. This is good food for thought. 



    ------------------------------
    Leslie Proudfoot
    GRID Alternatives
    lproudfoot@gridalternatives.org
    ------------------------------