> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://help.moveworks.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://help.moveworks.com/_mcp/server.

# Folders

Folders are the primary way to set access in Agent Studio. Every asset lives in exactly one folder, and that folder sets the default access for the assets inside it. Item-level grants are the exception.

## Folders vs. Views

The Agent Studio sidebar shows folders and views.

* A **folder** holds assets and defines their default access. When you place an asset in a folder, it inherits that folder's access rules.
* A **view** is a filtered lens over assets you already have access to. It doesn't grant access on its own.

<table>
  <thead>
    <tr>
      <th>
        Type
      </th>

      <th>
        Examples
      </th>

      <th>
        Grants access?
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        <strong>Folders</strong>
      </td>

      <td>
        Public, Personal, Custom folders
      </td>

      <td>
        Yes. Sets default access for contained assets
      </td>
    </tr>

    <tr>
      <td>
        <strong>Views</strong>
      </td>

      <td>
        Connectors, Shared with me, Installation drafts
      </td>

      <td>
        No. Filters what you can already see
      </td>
    </tr>
  </tbody>
</table>

## The Three Folder Types

<table>
  <thead>
    <tr>
      <th>
        Folder
      </th>

      <th>
        Created by
      </th>

      <th>
        Default access
      </th>

      <th>
        What it's for
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        <strong>Public</strong>
      </td>

      <td>
        System (one per workspace)
      </td>

      <td>
        Visible and usable by all Agent Studio users
      </td>

      <td>
        Org-wide, shared assets
      </td>
    </tr>

    <tr>
      <td>
        <strong>Personal</strong>
      </td>

      <td>
        System (one per user, auto-created)
      </td>

      <td>
        Owner and Agent Studio admins
      </td>

      <td>
        Your drafts and in-progress work
      </td>
    </tr>

    <tr>
      <td>
        <strong>Custom</strong>
      </td>

      <td>
        Admin
      </td>

      <td>
        Defined per folder by the admin
      </td>

      <td>
        Scoped domains like "HR Integrations" or "Finance Automations"
      </td>
    </tr>
  </tbody>
</table>

Only Agent Studio admins can create, rename, or delete custom folders, and only admins set folder-level default access. Developers work within the folders they've been given access to.

### Personal Folders

Every user gets one Personal folder, created automatically. New assets start there as drafts.

* **You and Agent Studio admins can see your drafts.** Admins have workspace-level visibility so they can govern assets across the workspace.
* When you create an asset in your Personal folder, you automatically get the **Developer** role so you can build and test it.
* If you later move that asset into a custom folder, you keep your Developer access on it.

## Inheritance

Assets inherit access from their folder at the moment they're placed in it.

* A new asset placed in a folder picks up that folder's default access automatically.
* Move an asset to a different folder, and it picks up the new folder's defaults.

## Item-Level Overrides Are Additive Only

A Manager can grant extra access on a single asset, beyond what its folder allows. Overrides only add access. They cannot take it away.

* Allowed: a Manager can grant a specific user `Use` on one asset in a folder they otherwise can't access.
* Not allowed: a Manager cannot lock one asset down below its folder's default at the item level.

To make an asset *more* restrictive than its folder, change the folder's default or move the asset to a more restrictive folder.

A folder sets the default access for the assets inside it. It does not limit who can later be granted access to an individual asset. Managers can add per-asset access on top of the folder default.

## What You See in the Sidebar

The sidebar shows only folders where you have at least one role on the folder itself, or at least one item-level grant on an asset inside it. Public and Personal are always visible.

## Folder Lifecycle

Custom folders are created, renamed, and deleted by admins. The two system folders, Public and Personal, can't be deleted by anyone.

<table>
  <thead>
    <tr>
      <th>
        Action
      </th>

      <th>
        What happens
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        <strong>Create</strong>
      </td>

      <td>
        The folder appears in the sidebar. On creation it's accessible to the creating admin and all admins; other users see nothing until the admin sets the folder's default access.
      </td>
    </tr>

    <tr>
      <td>
        <strong>Rename</strong>
      </td>

      <td>
        The name updates everywhere immediately. Asset URLs and IDs are unchanged.
      </td>
    </tr>

    <tr>
      <td>
        <strong>Delete</strong>
      </td>

      <td>
        Contained assets move to Public so nothing that depends on them breaks. A confirmation shows the asset count first. The assets then pick up Public's default access.
      </td>
    </tr>
  </tbody>
</table>

Deleting a folder moves its assets to Public rather than deleting them. Every Agent Studio user can see Public, so downstream plugins and actions keep working. Admins can reorganize the assets into restricted folders afterward.

## Moving Assets Between Folders

Moving an asset can change who has access, because the destination folder's defaults apply.

When an asset moves, its existing item-level grants are **cleared**. The asset then inherits the destination folder's defaults. Before the move commits, a confirmation explains that some users may gain or lose access. A more detailed preview, showing the affected users and dependent assets, is coming soon.

After the move, a Manager can grant item-level access on top of the new defaults.

## Sharing Across Teams

Because an asset lives in exactly one folder, cross-team sharing works in one of three ways:

* **Shared folder.** Put reusable assets in Public or a shared custom folder. This is simple, but can get cluttered if overused.
* **Per-asset grants.** Leave the asset in its owning folder and grant specific cross-team users on that asset.
* **Groups.** Group-based folder access is planned for a future release. Today, access is granted to individuals or org-wide through Public.

## Related

The roles a folder can grant by default.

Why connectors don't follow the standard folder defaults.