Project Settings

Open Settings from the project sidebar to configure project-wide behavior. The available actions depend on your project role.

General

The General page includes:

• Project name, description, type, and subtype.
• Template publication for creating or updating a private template.
• The source language currently used by Localization.
• Personal light, dark, or system appearance selection.
• Project primary and accent colors, with an option to restore the defaults.
• A maintenance action that repairs variable references.
• Project deletion in the danger zone.

Deleting a project is permanent. Its sheets, flows, scenes, assets, localization, brainstorming sessions and every backup are deleted, and nothing can bring it back. The confirmation shows the project’s latest backup: download it first if you may want the project again, because importing that ZIP into a workspace rebuilds it. Anyone who has the project open is told and taken back to the workspace dashboard.

If the project has no backup, the confirmation offers to make one first: Back up, download and delete is chosen by default, and Delete without a backup deletes the project at once. With the backup, the project is locked for everyone while it is made, even while the workspace is read-only or has no storage left, and the workspace dashboard shows its progress. Once it is ready your browser downloads it, and the project is deleted when the whole file has arrived. If the download is cut, nothing is deleted and the dashboard offers it again. You can cancel the deletion from the dashboard until then; a backup that fails, or one not downloaded within seven days, also ends it, and the project unlocks. A finished backup is kept among the project’s backups when it fits the plan’s backups and storage; otherwise it is deleted. The deletion waits for an import or a translation run already under way.

A project cannot be deleted while one of its templates is being published; try again once the publication finishes. Templates already published from the project keep working, because each version keeps its own copy of the files it uses.

Version Control

Version Control has separate switches for automatic versions of:

• Flows.
• Scenes.
• Sheets.

The page also shows current usage against the plan allowance for manually created project snapshots and named entity versions. Save after changing the automatic entity-version switches. Project snapshots are created and managed from the separate Snapshots page; there is currently no daily snapshot switch.

Usage Limits

Usage Limits is read-only. It shows the active plan and current usage for project items, project snapshots, named versions, workspace storage, projects, and members. Item totals are broken down into sheets, flows, scenes, and flow nodes. A status badge warns when a limit is close or has been reached.

Localization provider

Use Localization settings to enter a DeepL API key, choose the Free or Pro endpoint, test the connection, and inspect reported character usage. See Localization Overview for the translation workflow.

Members

The project member list shows each member and their current role. Project invitations can grant Editor or Viewer access. Owners cannot be removed from this list, and the current user cannot remove themselves with the member-removal action.

Workspace membership and project membership are separate. A person must be able to access the workspace before project-level access is useful. See Create a Workspace.

Import and Export

The Import & Export page can preview and import Yarn Spinner .yarn files or Yarn Spinner project ZIPs. It also configures export engine format, included sections, asset handling, formatting, and pre-export validation. Only project owners, who hold the manage_project permission, can prepare or run an import. See the dedicated Import and Export guide.

Snapshots and Trash are covered separately in Snapshots and Trash.