Where things live

Every task, document, and folder in Dhanu belongs to exactly one of three homes. Not two, not none. Picking the right one decides who can see the work and who can change it.

The three homes

Personal is yours. Drafts, scratch work, anything you are not ready to share. Nobody else in the workspace sees it.

A team library belongs to a team. Everyone on that team can reach what is in it. This is the right home for shared reference material that is not tied to one piece of work — brand guidelines, templates, the standing research folder.

A project is a boundary around one piece of work, with its own member list on top. A client engagement, a launch, an investigation. See What a project is.

Choosing between them

Ask who should see it, and for how long.

• Only me, for now → personal
• My team, indefinitely, not tied to one job → team library
• A specific group of people, for one piece of work → project

Moving something later is fine. The point is that at any moment there is one answer to “who can see this”, not a pile of overlapping permissions to reason about.

What follows the scope

Because the home is a property of the thing itself, everything downstream inherits it. A task in a project produces documents in that project. An image or spreadsheet the AI makes inside a task belongs wherever the task belongs. You do not set permissions separately on each artifact, and they cannot drift apart.

One deliberate exception: templates are never project-scoped. They stay personal or shared with a team so that a template does not vanish when a project is archived.

Next

What a project is covers the third home in detail, including the roles inside it.