Projects

A project is the top-level container in Runner. Everything — environments, files, schedules, runs, and members — belongs to a project. Access control is project-scoped: each member has a role that determines what they can do within that project.

Your projects

The project list shows a card for each project you have access to. Each card shows the project name, your role in it, and counts for environments, files, schedules, runs, and members. The counts are clickable and take you directly to that section — useful for jumping straight to the schedules or runs of a project without opening it first.

The last updated time and author give you a sense of recent activity without having to open the project.

Creating a project

Click Add Project, enter a name, and click Save. Runner adds you as the project owner and takes you to the Environments page.

The name is the only required field. Choose something that makes the project's purpose clear to other members — it appears in the project list, in email notifications, and in run logs.

Editing a project

Open the project and click Edit. The name is the only editable field. To manage who has access, go to Members & Roles.

Deleting a project

A project can only be deleted once it is empty. Remove all environments, files, schedules, and runs first — the Delete button is disabled until then. This prevents accidental loss of run history or workflow files that other members may still need.