> ## Documentation Index
> Fetch the complete documentation index at: https://learn.workflow.dog/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects

> Organize workflows, data, integrations, and teammates in a project.

A **project** is the top-level container in WorkflowDog. Its workflows,
workflow runs, variables, connected accounts, team, and billing settings are
kept together.

WorkflowDog does not have a separate workspace layer. When you choose a
project, you are choosing the complete working context for everything in the
project dashboard.

## Create a project

<Steps>
  <Step title="Open the project list">
    Use the project switcher and choose the option to view your projects.
  </Step>

  <Step title="Create the project">
    Select **Create Project**, enter a name, and confirm. The person who creates
    the project starts with Editor access.
  </Step>

  <Step title="Create a workflow">
    Open **Workflows**, select **Create a Workflow**, and choose the trigger
    that should start it. Workflow creation is trigger-first; there is not a
    workflow template picker.
  </Step>
</Steps>

## What belongs to a project

| Project resource      | Scope                                                                 |
| --------------------- | --------------------------------------------------------------------- |
| **Workflows**         | Can use other workflows and variables in the same project.            |
| **Workflow runs**     | Appear in the project's combined run history.                         |
| **Project variables** | Can be read or changed by any workflow in the project.                |
| **Integrations**      | Accounts are linked to the project before its workflows can use them. |
| **Team and roles**    | Access is granted per project.                                        |
| **Usage and billing** | Run credits, usage charges, and seats are tracked per project.        |

<Note>
  Moving a workflow between projects is not available. Create the workflow in
  the project whose integrations, variables, team, and billing it should use.
</Note>

## Switch projects

Open the project switcher from the dashboard sidebar, search by project name,
and choose a project. When possible, the switcher keeps you on the equivalent
dashboard section—for example, switching from one project's **Variables** page
opens **Variables** in the destination project.

The <kbd>P</kbd> shortcut opens the project switcher when focus is not inside
another input.

## Organize workflows with folders

The **Workflows** page supports nested folders. Create a folder, create
subfolders from its menu, and drag workflows between folders or back to the
project root.

Deleting a folder does not delete its workflows:

* Workflows in a nested folder move to the deleted folder's parent.
* Workflows in a top-level folder move back to the project root.
* Nested folders inside the deleted folder are removed.

<Warning>
  Workflow folders are stored in the current browser's local storage. Folder
  names, nesting, collapsed state, and workflow assignments are not shared with
  teammates or synchronized to another browser or device. The workflows
  themselves remain project data.
</Warning>

If folders disappear after clearing browser data or changing devices, the
workflows are still available at the project root.

## Rename a project

Open the project overview, select the project name or its menu, and choose
**Rename Project**. Renaming changes the project label without changing its
workflows, integrations, or URL identifier.

Only an Editor can rename a project. See
[Team and permissions](/essentials/team-and-permissions) for role details.

## Delete a project

Project deletion permanently removes the project and its associated workflows,
runs, variables, integration links, invitations, and other project data. It
also cancels an active usage subscription for that project.

<Warning>
  Project deletion cannot be undone. Confirm that you no longer need the
  project's run history or variable values before deleting it.
</Warning>

An Editor can delete the project from the project overview menu. Because
Editors have broad project control, grant that role only to trusted teammates.

## Troubleshooting

<AccordionGroup>
  <Accordion title="A project is missing from the switcher">
    The switcher lists only projects where your account is a member. Confirm
    that you accepted the invitation while signed in with the invited email
    address and that another Editor has not removed you.
  </Accordion>

  <Accordion title="My workflow folders are different on another device">
    This is expected. Folder organization is local to each browser. Search for the
    workflow by name, then recreate any local folder structure you want on that
    device.
  </Accordion>

  <Accordion title="I cannot rename or delete the project">
    Those actions require Editor access. A Viewer can inspect project resources
    but cannot change project settings.
  </Accordion>
</AccordionGroup>