Group Tasks And Files By Project

Details

Create a project with a name and a clear purpose, then attach tasks and files to it as they come in. Select it in the switcher and the task board and your Drive narrow to just that work; clear the filter and everything is back. Pin the ones you're actively running so they sort to the top, and archive the ones that have wrapped: an archived project keeps its tasks and files exactly where they are, it just drops out of the picker and stops counting against your plan's active-project limit. The reason to file something is not tidiness. A task inside a project carries that project's name and purpose with it, so the employee working it knows which effort it serves rather than only what the one instruction says. Past two or three employees, that is the difference between a board that reads like a company and one that reads like a single overloaded to-do list. Your employees can manage the list too: read it, create a project, update a name or purpose, pin one to the top. Archiving stays yours to approve, because it changes what everybody else can see. Nothing is forced into a project. Existing tasks and files read as Unassigned and stay visible, so there is no cleanup pass to do before this is useful. Two limits worth knowing: only tasks and Drive files carry a project today, so conversations, mailbox and CRM stay shared across the whole workspace, and a project is a filter rather than a wall. An employee working inside one project is not fenced off from what it knows about another.

What changed

• Create, edit, pin, archive, and restore projects from the task header
• Filter the task board AND Drive down to one project, or to unassigned work
• A task carries its project's context, so employees know what it's part of
• Nothing is deleted when you archive a project, its tasks and files stay put
• Filters what you see, it does not fence off what an employee knows