File management system for member organizations

Every member account carries its own drive, visible to that member and to admins only. Signed decisions, certificates, and volunteer agreements sit on the profile they belong to rather than in a shared folder.

Members upload their own files, and files an admin uploads to a personal drive cannot be deleted or altered by the member.

Every group and every chapter gets its own drive alongside its discussions, events, and member list. A marketing committee, a regional body, and a local chapter each keep their files separate, and each drive can be switched off if a group does not need one.

The general group holds the documents everyone needs: statutes, bylaws, policy handbooks, playbooks, brand assets, and templates.

The files section pulls together every drive a person can reach, so members do not have to remember which group a document was filed under.

Access is driven by group membership, role, and membership status. When someone changes role, transfers chapter, leaves the organization, or lets their membership lapse, their file access changes with them.

Nobody has to remember who was sent a link three years ago, which is the failure mode of a shared drive at a few thousand members.

Each group controls two things independently:

• Who can see the group's files
• Who can upload files and change the folder structure

A local admin can be given upload rights to their own chapter's drive without gaining access to any other chapter's.

Orgo is the authentication system for your membership, so documents can be limited to paid-up members. Bylaws can stay open to everyone while minutes stay behind the membership fee.

Each drive records who uploaded, changed, or shared what, and when. Personal drives keep their own log, so files attached to a member's profile carry the same trail.

Drag and drop into folders and subfolders, in an interface deliberately built to feel familiar to anyone arriving from Google Drive. Single files can be up to 5 GB, and there is no restriction on file type.

Images, PDFs, PowerPoint, and Microsoft Office documents open directly in the browser. Media can be browsed as a gallery instead of a list, and PDFs and images generate thumbnails automatically.

A Word-style editor writes documents straight into a drive, so short notes and internal pages do not need to be produced elsewhere and uploaded. Editing is single-user; the editor is not real-time collaborative like Google Docs.

Uploaded video plays in a player carrying your organization's logo, and that player embeds on your own website. It works as your own YouTube for member-facing recordings.

YouTube, Vimeo, and Spotify links embed as well, and embedded media does not consume your storage.

Selected files or whole folders can be shared with anyone who has the link, which suits public policy documents, press assets, and event photography.

The same share can instead require a login, so opening the link prompts sign-in and Orgo checks membership before the file appears.

Files attach directly to discussion threads and to events. Meeting notes sit next to the thread discussing them, and photos from an event stay on the event they came from, with the same permissions as the thread or event itself.

Documents generated from templates and signed inside Orgo, such as volunteer agreements or consent forms, are stored on the signer's own profile alongside their payment and event history.

A Google Drive folder will connect to an Orgo drive, so its contents appear in Orgo without being re-uploaded. The files stay in Google Drive and keep counting against Google's storage rather than your Orgo quota. This integration is coming in September.

The same connection is being built for SharePoint, for organizations standardized on Microsoft 365. This integration is coming in September.

Synchronization works at directory level: connect a folder tree once, and its structure is mirrored inside Orgo rather than being moved item by item. Adding a file on the connected drive makes it visible in Orgo. Directory sync ships with the Google Drive and SharePoint integrations in September.

Once a folder is connected, who sees it is still decided by Orgo group membership, role, and membership status. A document living in Google Drive reaches your members through the same permission model as one uploaded to Orgo, which is the point of the integration.

Plans start at 250 GB and expand in increments, typically 100 GB or 1 TB. The quota covers files in drives plus media uploaded to discussions, events, and courses.

Files are stored on AWS with redundancy and served through a global CDN, so downloads are fast for members regardless of the country they are in.

Nothing is archived away or degraded over time. Romanian Scouts has been on the platform for more than ten years without running into storage problems, and posts and attachments from years back remain accessible.

Two options reduce what your storage has to hold:

• Embedded YouTube, Vimeo, and Spotify media does not count toward storage
• Google Drive and SharePoint sync, coming in September, leaves files on the connected drive