Back to home
Files

Files

Your files, with their formats, organised and linked to the task, project and client.

The files space

Your files as your eye sees them:
a grid of previews, not a list of names.

Open the project folder and you see the files by their faces — the design, the photo, the print file, the spreadsheet — not identical rows. Press any file to see its details, who uploaded it, and which task and client it belongs to; switch to list view if you prefer rows.

Visual identity refresh / FilesClient: Riyadh Press

Folders

Files

The grid is the default view — the list is one click awayPress any file to see its details and its links
Files will not crowd you any more.

Everything in front of you is a live, in-use copy, linked to its task, project and client the moment it is uploaded. What is no longer in use crowds neither your grid nor your search results.

and with it ends

file clutter and old versionswasted resourcesscattered searchhigh archiving costslost time

What piles up never gets searched; what is linked is found first time — a file here is part of the work in progress, not an archive you pay to store.

Bad habits

Where do your files live today?
On your laptop, or in a cloud that knows nothing about your work.

Six common habits that look practical today and cost you in two months: a file that does not know its task, several versions with no clear latest, an open link with no record of who opened it. Each has a price — and a clear alternative.

The final version is on my laptop

The file lives on one person's machine. If they travel or the machine dies, the work stops; if they leave the company, the file leaves with them — the company owns the work but not its file.

A file belongs in the team's space, not on an individual's machine: whoever joins the project finds it, whoever leaves loses access and the files stay.
A separate cloud with no context

The file is in Drive or Dropbox: it exists, but it knows nothing of its task, its project or its client. So you search for a filename you forgot instead of opening the task you remember.

Upload it from inside the task and it inherits that task, project and client — you reach it three ways, not only by its name.
final · final-2 · final-approved

Two copies edited at once, one edit lost, and nobody can say which is newest — so the wrong one goes to print and is discovered after delivery.

One copy in its place inside the task, and documents edited together in a single live version instead of emailed attachments.
The explanation in a chat, the file somewhere else

The second colour is approved gets said on WhatsApp while the file sits in a folder. Two months later you find the file but not the reason for the decision — so the discussion starts over.

Write the note on the file itself, so it stays beside it for whoever opens it after you — not in a chat buried under a hundred messages.
An anyone-with-the-link link

The fastest way to share and the most dangerous: the link stays open after the project ships and after the employee leaves, and you have no idea who opened it or when.

Access by role and permission inside the workspace: the team changes and access changes with it, with no stray links sitting in somebody's inbox.
A folder named after an employee, not after work

Only Noura knows her way around Noura's files. Whoever replaces her starts day one on a scavenger hunt, and every question about an old file goes through her.

Project and client folders: the structure follows the work, not the people, so it still makes sense a year later and after the team changes.
Tips

Four habits that make your files find themselves.

Upload the file from inside the task, not from your desktop

One second makes the difference: a file uploaded inside its task inherits the task, project and client at once, so you find it later through any of the three. One uploaded from outside stays a name in a folder.

A folder per project or client, not per person

A structure that follows the work still makes sense a year later and after the team changes. One that follows people dies with the first resignation.

Write the note on the file, not in a side chat

The reason behind the decision — why this colour, why the previous version was rejected — stays attached to the file for whoever opens it after you, instead of being lost in yesterday's messages.

Make access a role, not a link

Define who sees a project's files by their role in the workspace. The team changes and access changes with it — no forgotten public link, no file stranded in a personal account.

Put Files to work

Try it with your team and judge after the first hour.