Organize project files

Consolidate the product files into a single project folder and apply our team naming convention. Move the current mobile flows into Mobile > Auth and Web > Dashboard into Web > V2, tag stale files as ARCHIVE with the quarter and owner, and share edit access only with the design team. Confirm with Elena in design ops once the reorganization is complete.

Before I rearrange everything, make it fast for reviewers to find what matters. Surface the active file for each product line at the top, display owner and last‑updated time, flag any files that haven't been edited in three months, and make a clear path to reach archived versions so stakeholders can still reference older work without cluttering the main view.

Marketing asked me for the live homepage prototype and opened an old copy that did not have the new hero layout. They’re now briefing the wrong direction to the agency. I’ve got multiple copies named similar things across projects and I don’t know which one is the single source of truth. What’s the most reliable way to establish and communicate the canonical file so stakeholders stop using stale copies?

We keep duplicating files and people pull old versions from different folders; it costs the team hours every week and damages our credibility with product and marketing. What organizational rules, permission models, and simple naming conventions should I institute so the design files stay discoverable and the team stops creating shadow copies?