Skip to content

Keep a Project while its source and development history remain useful. Invite collaborators to the Project with roles suited to their work; they do not automatically receive Site management or visitor access. Review conversations, previews, connected resources, schedules, and Site relationships when changing ownership or access.

Reuse or retire

Publish a reviewed Project template when others should create independent copies. A published version freezes the reviewed reusable source and configuration; later source edits do not change earlier remixes. To keep a production application running, manage its Site independently. Disconnecting a Site source leaves its current release in place, but new releases need an authorized connection.

Export or archive

If you have export access, download the Project's default-branch source as a ZIP. The download contains the saved source; it does not by itself establish that the application will run elsewhere. Before operating it outside Playbooks, review its dependencies and prepare configuration examples, applicable schema or migration guidance, and operating instructions. Handle credentials and private data separately; do not assume they are part of the source download.

Archive a Project to remove it from active work while retaining a recovery path. Before deletion, inspect associated Sites, schedules, collaborators, and retained development data. A Site operates separately from source editing and has its own production obligations; manage it explicitly rather than assuming a Project action handles it.

Example: stop development without losing production

A Project may no longer need active editing while its Site still serves customers. Review the Site separately before archiving or removing source work; production has its own release, data, configuration, and obligations.

Record which source and revision the Site uses and how future updates will be prepared. See Site operations before assuming a Project lifecycle action handles production.

Review collaborators

When someone changes responsibilities, inspect their Project role and any separate Site or connection access. A person who only needs a finished result may need Artifact sharing or Site visitor access instead of source access. Use Permissions for the shared model.