Settings

Settings is the last item in the Explorer tree. It holds what is about the project itself, not the app you are building: its name, its description, keeping it up to date, and switching it off.

The rule for what goes here is short. If a setting changes what the people using your app see or do, it belongs with the app, in Explorer: the theme, the layout, the icons, sign-in, the database. If it changes how Sapilon holds, maintains or charges for the project, it belongs in Settings.

General

• Name is what the project is called in Sapilon: in the project list, in the bar at the top of the studio, and in the browser tab. It is not the name people see when they install your app on a phone or a desktop. That name is set per web app, on its Web Manifest page.
• Description is the same answer you gave in Next Steps, under the project basics. The agent reads it to understand what you are building, so keeping it current keeps the agent’s picture current. Editing it in either place changes the one answer. Until you have answered the basics in Next Steps, Settings sends you there instead of offering the field.
• Key names your project’s repository. It is set when the project is created and never changes, because the repository, its history and every link to it depend on it.
• Created is the day the project was started.

Updates

Every app in your project is built on a foundation that Sapilon maintains: security fixes, upgrades to the tools underneath, and new capabilities. They arrive as numbered platform versions, such as Platform v2.13. The Updates section shows which version the project is on and whether a newer one is ready.

• What’s new lists each release you have not applied yet, newest first. Open one to see what it changes.
• Needs your attention means a release asks something of you, for example a step to take or a change to check afterwards. Those releases open by themselves, so you read what they ask before you choose Update now.
• Update now applies the update app by app. It lands as a new version of the project, so you can go back from it like from any other change.

When an update you can see or must act on is ready, the Dashboard says so and links here. Updates that change nothing you would notice don’t interrupt you.

How an update treats code you have edited yourself is explained in Editing generated code.

Danger zone

• Deactivate stops all of the project’s services. Nothing is deleted, and you can reactivate it from the same place at any time. A project that still has servers running can’t be deactivated: remove its servers on the Publish page first (see The servers).
• Delete removes the project and all its files, permanently. You confirm it by typing the project’s name. Afterwards you are taken back to your project list.

Who can open Settings

Only the project’s owner. Experts working on the project don’t see these settings, and opening the page sends them to the Dashboard. An expert who thinks the project should be updated asks the owner, because an update changes the project and can change what its users see.