Project settings

To open a project's settings, go to your WeWeb dashboard and click on the project's card in the Projects tab of your workspace. The project opens on its Deployments tab, with all its settings in the menu on the left:

The menu holds 6 tabs:

1. Deployments
2. Domain
3. Editor Backups
4. WeWeb Cloud
5. Access
6. Settings

You only see the tabs your permissions let you use. For example, the Access tab shows if you have the Access permission on the project, or the Access workspace permission.

Above the tabs, the Open Editor button opens the project in the editor, and the three dots next to it let you open it in safe mode. Back to projects takes you back to your workspace.

Deployments

The Deployments tab lists every publication and export of your project, newest first. Publishing itself is done from the editor: the Publish button at the top right sends your app to staging or production.

From the three dots at the end of a row, you can read the logs of a publication and restore an earlier version to production. If your plan includes code export, you can also download the files of an export.

Learn more about WeWeb Deployments

Domain

In the Domain tab, you will be able to connect a custom domain to your WeWeb app.

Learn how to add a custom domain to your project

Editor Backups

The Editor Backups tab lists the saved versions of your project's editor. Click Rollback Editor on a row to bring your editor back to that state, even when the editor no longer loads. To create a backup yourself before a risky change, use the Settings tab of the editor.

Learn more about WeWeb Backups

WeWeb Cloud

The WeWeb Cloud tab is where you choose your project's WeWeb Cloud plan. It shows what your project used during the current billing cycle, the WeWeb Cloud plans you can switch to, and the add-ons you can subscribe to.

For example, this is where you go when you're ready to publish on your own domain and want to move away from the Free plan.

Upgrades take effect immediately. Downgrades and cancellations take effect at the end of the billing period.

TIP

The WeWeb Cloud tab only appears once your workspace has a workspace plan, as WeWeb Cloud plans are added on top of it. Only people with the Billing workspace permission can change a project's WeWeb Cloud plan.

Access

The Access tab is where you choose who can open the project and what each person can do in it, and which workspace connections it can use. For an internal app, it's also where you choose who can use the published app.

Learn more about giving access to a project

Settings

In the Settings tab, you can:

1. Change the project name and copy the project ID
2. Set up a deploy hook, a URL that WeWeb calls after every successful deployment
3. Choose the GitHub repositories the project's code is pushed to
4. Open the project's self-hosting settings, once your workspace has a weweb-server set up
5. Unpublish the project, which takes every deployed version offline and detaches its custom domains
6. Transfer the project to another workspace (on the Partner plan)
7. Delete the project (beware, this is permanent and we won't be able to recover your project)

What you can change depends on your permissions:

• Renaming the project and setting its deploy hook need the Settings permission on the project.
• Choosing the GitHub repositories needs the Publish › Export permission on the project.
• Unpublishing needs the Publish › Production permission on the project.
• Only the project's creator, the workspace owner, or someone whose role reaches every project can delete or transfer it.

Learn more about roles and permissions →

Learn more about after deploy hooks and self-hosting.

Safe mode

If your app crashes or behaves strangely when you open a project in the Editor, we recommend opening the project in safe mode.

To open a project in safe mode:

1. Open the project from the Projects tab of your WeWeb workspace
2. Click on the three dots icon next to the Open Editor button
3. Choose Safe Mode: No Workflows, Safe Mode: No Workflows & Formulas or Safe Mode: No Workflows, Formulas or Project Coded Elements

This will allow you to test your project:

• With all workflows disabled,
• With all workflows and formulas disabled, or
• With all workflows, formulas and the coded components of your project disabled.

Use the third option when a coded component freezes the Editor, for example one that keeps running in a loop. Each coded component of your project is replaced by a placeholder showing its name and Coded component disabled in safe mode, so the Editor can open and you can fix or delete the component.

This can help you identify what you need to debug in your app.