# Folders (https://docs.fuser.studio/docs/teams/folders)

A folder is a named container for projects. Folders give each team a place for its work, and they're how you set the default access level for everything inside.

Folders live in one of two places:

* **At the workspace root** — visible to the whole workspace, governed by the workspace root access level.
* **Inside a team** — visible to that team's members, governed by the folder's own default access.

This page covers creating folders, choosing visibility, and configuring default access.

## Creating a Folder [#creating-a-folder]

    ### Open the new folder dialog [#open-the-new-folder-dialog]

    In the sidebar on the home page, hover the **Folders** section and click the **+** button. You can also create a folder inside a team from the team's section.

    ### Fill out the folder details [#fill-out-the-folder-details]

    Fuser asks for:

    * **Name** — what the folder is called.
    * **Color** — a small dot used to label the folder in the sidebar.
    * **Visibility** — **Private** or **Team** (described below).
    * **Default access** — what level of access folder visitors get by default (described below).

    ### Drop projects into it [#drop-projects-into-it]

    The folder appears in the sidebar immediately. You can drag and drop projects into it, or pick it as the destination when creating new projects.

## Folder Visibility [#folder-visibility]

A folder is either **Private** or **Team**:

* **Private** — only the creator and workspace **Admins** can see it. Use this for a personal scratch folder, or for work-in-progress you don't want to surface yet. Private folders cannot be assigned to a team.
* **Team** — every member of the assigned team can see the folder. If no team is assigned, the folder lives at the **workspace root** and every workspace member can see it.

> [!NOTE] Private folders override their projects
>
> A **Published** project inside a **Private** folder is still hidden from everyone except the folder creator and workspace **Admins**. The folder's privacy gate takes precedence over the project's own visibility setting.

## Default Access [#default-access]

The folder's **default access** sets the level at which people get to its projects when no explicit share is involved.

*  **View** — everyone who can see the folder can read its projects.
*  **Edit** — everyone who can see the folder can read and edit its projects.
* **Inherit** — use whatever the **Workspace root default access** is set to in [Workspace Settings → Access Defaults](https://docs.fuser.studio/docs/teams/workspace-settings.md#access-defaults). The default for new team folders. If you don't change the workspace default, "Inherit" effectively means "Edit" out of the box. Choose Inherit when you want one toggle in workspace settings to drive every folder's defaults at once.

The default applies only to people who have access to the folder in the first place — for **Team** folders, that means team members; for workspace-root folders, that means every workspace member. **Admins** and **Owners** always get Edit regardless.

For the precise rules and edge cases, see [Access Reference](https://docs.fuser.studio/docs/teams/access-reference.md).

## Workspace Root vs. Team Folders [#workspace-root-vs-team-folders]

A folder lives in one of two homes — directly at the workspace root, or inside a team:

        Project

          Project

The **workspace root** is the implicit container outside any folder or team. It has its own default access level (set in [Workspace Settings → Access Defaults](https://docs.fuser.studio/docs/teams/workspace-settings.md#access-defaults)) and applies to:

* Projects you create at the workspace root with no folder.
* Folders that don't belong to a team — these inherit visibility from the workspace.
* Folders set to **Inherit** — the default access flows down from the workspace root.

A **team folder** lives inside a team. It's gated by team membership: non-members can't see it unless someone shares it with them. Inside the team, the folder's default access decides whether members get View or Edit.

## Folder Creator Rights [#folder-creator-rights]

The person who creates a folder always keeps **Edit** access on the folder itself, so they can rename it, change its color, or add projects. Only **Admins**, the folder creator, and (for team folders) team **Managers** can change the default access or delete the folder.

> [!WARNING] Creator access is per-workspace
>
> Creator rights apply only while you're a member of the workspace. If you leave the workspace, you lose your folder-creator rights along with everything else. For team folders, you also need to stay in the team to keep *seeing* the folder — creator rights cover management, not visibility.

## What's Next? [#whats-next]

  - [Sharing](https://docs.fuser.studio/docs/teams/sharing.md): Override folder defaults with explicit shares to specific people.

  - [Access Reference](https://docs.fuser.studio/docs/teams/access-reference.md): Full rules for how folder access combines with teams and shares.