Scaling your organization

Everything you’ve learned so far works just as well for fifty people as for five — but at scale, good habits are what keep things sane. This page is about working deliberately as your organization grows.

Scale your folder structure, not just your file count

A flat library is fine at ten files and miserable at ten thousand. Decide on a structure early and make it a convention everyone follows.

A pattern that scales for a music organization:

• Top level: projects or releases. One folder per release or client.
• Second level: stages. Inside each, sub-folders for demos, stems, mixes, and masters.
• An archive. Move completed work out of active folders so day-to-day stays focused.

Write it down

Document your folder convention and link it where your team will see it. A shared structure that everyone understands is the single biggest lever for a large library staying usable.

Use roles deliberately

At scale, sloppy roles become a liability. Apply the principle of least authority:

• Keep the Admin circle small — the people who genuinely run the organization.
• Make everyone else a Member. They can do all the real work without being able to change the organization itself.
• Revisit roles periodically as people’s responsibilities change.

See Members & roles for the full breakdown.

Make sensitive work private by default

Organization-wide visibility is convenient for a small team where everyone’s trusted with everything. As you grow — and especially across a global team with external collaborators — shift important work to private and grant access deliberately.

1. Make the sensitive file or folder private.
2. Grant Owner to the people responsible for it.
3. Grant Editor to active collaborators.
4. Grant Viewer to stakeholders who need to follow along.

This keeps each release’s circle exactly as wide as it should be. The Access-control patterns page goes deeper.

Lean on history and notifications across time zones

A global team is rarely online at once. Two features bridge the gaps:

• Activity history lets anyone catch up on exactly what happened while they were offline.
• Notifications make sure the right people learn about shares and new versions without anyone having to chase them.

Together they mean work moves forward around the clock without constant hand-offs.

Plan seats ahead of growth

Inviting people is smoothest when the seats are already there. Before a hiring push or a new project team forms, size your plan for where you’re going — then invitations just flow.

A scaling checklist

• A documented folder convention everyone follows
• A small, intentional set of Admins
• Sensitive work set to private with deliberate grants
• Seats sized a little ahead of your team
• The team relying on history + notifications to stay in sync

Nail these, and LMG Core grows with you instead of against you.