Project Settings

A project's Settings hold what applies to the whole project: its name, bulk actions, export, cloning, moving, transferring and deleting. Open the project, then Settings in its sidebar. The tabs are General, Collaborators, Deployments and Advanced.

Name and description

Under Basic Information, change the Project Name (shown in the project list and the sidebar) and an optional Description. Renaming changes nothing that runs. The section also shows the project's server and its Project ID, for the API and the CLI.

Suspend or restart every service

Under Bulk Operations:

• Suspend All stops every service at once. Configuration, domains and volumes stay; deploy to start them again.
• Restart All restarts every service, one at a time, with the same images and configuration.

To deploy every service at once, use Deploy all (How Deploys Work).

Export

Export downloads the project as a Zenavo manifest (<project>.zenavo.json): its services, sources, settings, volumes, domains and variables, including variable values. Keep the file private.

Import it again from New Project → Import a Zeabur template or a Zenavo export, on any server and in any team. An export holds configuration, not data: to bring data along, use backups.

Clone a project

Clone Project creates a copy with all services and configuration, in this team or another team you are a member of, on any of its servers. Give the copy a name (by default <project>-copy) and pick the team and server.

• The copy is not deployed: review it, then deploy it.
• Volume data is not copied. Restore a backup in the copy to bring data along, or move the project instead if it should leave its current server.
• Domains and fixed TCP/UDP ports are cleared, since the original still uses them. Bind new ones under each service's Networking tab.
• Variables, config files, build settings and health checks are copied as they are. Generated variables such as database passwords keep their values, so check the services that hold credentials before you deploy the copy next to the original.

Cloning is useful for a staging copy of production, or to try a change without touching the running project.

Move to another server

Move to another server moves a deployed project, with its volume data, to another server of the same team. See Move a Project.

Transfer to another team

Transfer project ownership (team admins) moves a project to another team you administer, onto one of that team's servers.

Only a project that has never been deployed can be transferred: a deployed project's services and volumes live on a server of its team. To hand over a deployed project, clone it into the other team, restore its backups there, and delete the original once the copy runs.

Both teams' audit logs record the transfer.

Delete a project

Delete project (team admins) removes every service, domain and volume of the project from its server, and its backups from Zenavo. Type the project name to confirm. This cannot be undone: download any backups you need first.

Deleting a project that has been deployed runs a job that removes its resources from the server; follow it under Deployments. A project that was never deployed is deleted at once.

Collaborators

Everyone in the project's team can open it, with their team role. Per-project collaborators are not available yet; Collaborators lists who has access and links to the team's members.

Deployments

Deployments lists every deployment of the project, newest first, with its kind and status. Open one to read its logs, or to roll back every service to it.

Advanced

• Configuration → Edit JSON edits the full project manifest, including variable values. Saving does not redeploy. Use it for settings the console has no field for, or many changes at once; the manifest format is the one Export downloads.
• Migration checklist tracks a migration onto this project: source backed up, data restored and checked, sign-in, workers, email and callbacks verified, DNS switched, and the source kept running for the rollback window. You tick the items yourself; a successful deployment does not tick them. See Migrate from Zeabur.