Faculty Collaboration Tools for File Sharing

Faculty collaboration has three distinct modes and each needs different tooling. Committee work (search committees, curriculum review, faculty senate) runs on Microsoft 365 or Google Workspace for Education with real-time co-editing and SharePoint or Drive folders. Research collaboration needs Git-backed version control (GitHub Enterprise, GitLab) for code, Overleaf or Authorea for manuscripts, and Globus for datasets. Administrative tasks — sending a budget .xlsx to the dean, a confidential tenure file to external reviewers — benefit from encrypted ad-hoc transfers so sensitive documents don't live forever in Outlook.

Committee Work and Shared Document Editing

A search committee of eight reviewing 180 applications ends up with folders of .pdf CVs, writing samples, and teaching portfolios. Microsoft 365 SharePoint with permission-scoped sub-sites handles this cleanly — the committee chair controls access, members see only applicants not in their conflict pool, and the AA/EO office can audit the view log for compliance. Co-authoring a rubric in Word Online or Google Docs avoids the "latest_FINAL_v7_markup.docx" problem. Teams or Slack channels per committee keep discussion threaded; email kills committees. Don't use personal Google accounts or free Dropbox — they're outside the institution's retention policy and create discoverable records in lawsuits.

Research Manuscripts Across Co-Authors

Overleaf Pro ($17 per user per month, free institutional licenses at 100+ universities) gives real-time LaTeX collaboration with Git integration. Authorea and Curvenote offer similar workflows with more focus on reproducible figures. For Word-based manuscripts in humanities and social sciences, Microsoft Word's modern co-authoring beats the old email-the-draft-around approach — tracked changes attribute to each co-author, and the merge is automatic. Zotero with a group library handles the citation manager side. When the manuscript goes to the journal, export a clean PDF with author metadata scrubbed for double-blind review.

Research Data and Code Repositories

GitHub Enterprise at $21 per user per month gives unlimited private repos, advanced security features, and SAML SSO for faculty. GitLab Ultimate runs similar pricing with more CI/CD baked in. For data too large for Git, DVC or Git LFS externalizes the bulk to S3 or GCS while the Git history tracks hashes. A physics collaboration with 500 GB of simulation output stores the .root files on an institutional S3 bucket with DVC pointers in the Git repo. Reproducibility tools like Binder, Code Ocean, and the Whole Tale let reviewers rerun your analysis without installing your environment — important for high-stakes papers in Nature or Cell journals.

Confidential Personnel Files and External Reviewers

Tenure dossiers, promotion packets, and external reviewer letters are among the most sensitive documents on campus. A full tenure file weighs 200 MB to 1 GB — CV, research statement, teaching portfolio, external letters, student evaluations, publications. Sharing with an external reviewer at another university means the file leaves the institutional SSO perimeter. Options: (1) Interfolio, purpose-built for academic review with per-reviewer portals and watermarking, roughly $15 to $25 per case, (2) a password-protected ZIP sent via email with the password on a separate channel (weak but common), (3) an end-to-end encrypted transfer with 30-day expiry matching the review window. Options 1 and 3 leave audit trails; option 2 doesn't.

Budget and Administrative Documents

Department budgets in .xlsx, grant pre-awards, course release proposals, and salary adjustment memos all move between faculty chairs and deans. The dean's office typically lives in Microsoft 365 or Google Workspace; attachments over 25 MB bounce from Gmail and over 20 MB from Outlook free. OneDrive and Google Drive shared links handle this for internal recipients. For external consultants (outside auditors on program review, accreditation site visitors from SACSCOC or HLC), a time-bound encrypted link beats provisioning them a guest account. Budget document retention under state sunshine laws often requires 5 to 7 years — keep the master in the institutional records system, not in personal OneDrive.

Scheduling and Coordination Overhead

A committee of eight faculty with teaching loads and research commitments takes 3 weeks to find a 2-hour meeting. Calendly, Microsoft Bookings with Staff, and Doodle reduce the back-and-forth. For recurring meetings, a shared Microsoft 365 calendar view with free/busy shows the next three weeks at a glance. When the meeting requires pre-reading, distribute the agenda and supporting documents 48 hours before — any less and faculty skim in the meeting, defeating the purpose. Shared OneNote or Notion pages keep a running record of decisions across meetings; minutes in a Word doc buried in a folder don't get read.

External Partner Collaboration

Industry partners, granting agencies, non-profit collaborators, and government program officers often can't log into your Shibboleth IdP. For sustained collaborations, provision guest accounts in Microsoft Entra ID (B2B guest, free for 50,000 collaborations per month) or Google Workspace visitor access. For one-off shares — sending a 500 MB pre-grant proposal to NSF program officer, sending a demo video to an industry sponsor — an encrypted ad-hoc link beats account provisioning friction. Services like HexaTransfer, SwissTransfer, and Dropbox Transfer work without the recipient registering.

Retention, Records, and Legal Holds

Public universities fall under state public records laws (Texas Government Code Chapter 552, California PRA, Florida Sunshine Law) that treat faculty emails and working documents as discoverable. Retention schedules typically specify: course syllabi kept 5 years, committee minutes 10 years, personnel files 7 years post-separation, research data per federal grant terms (typically 3 to 7 years after final report). Work files in personal cloud accounts circumvent these schedules and create a compliance nightmare during records requests. Keep faculty work in institutional accounts from day one. When a legal hold hits, IT locks down the relevant accounts and disables deletion — faculty side channels wreck this if the work lived there.

Try it at hexatransfer.com — free, no account, 10 GB max. For the confidential tenure letter your external reviewer at Princeton needs to see but won't sit in her inbox for six years, an encrypted link with 30-day expiry matches the review window exactly.