Staging for apps

A second copy of an app with its own data and its own variables, where new versions run before they go live. Required for apps shared with several teams or the whole organisation.

An app people rely on should not change under their hands. Staging is a second copy of your app, beside the live one, with its own data and its own variables. A new version runs there first; you try it, and when it is right you make it live.

When versions go to staging

  • Apps shared with several teams or the whole organisation: every new version goes to staging first. Your workspace’s rules for apps require it, and I only make a version live for that audience once it ran on staging.
  • Your own and your team’s apps: staging is optional. Turn it on in the app’s settings under Staging, or ask me: “put new versions of the release board on staging first”.

When a version is ready on staging, I tell you in your chat. The card has Open staging, to try it, and Make it live. Making it live goes through the same rules as sharing: if something is still missing, the card says what.

Want to share an app wider whose live version never ran on staging? Ask me to put it on staging; once it ran there, share it again.

Staging data

Staging never touches the data of the live app. It gets one of two data sets:

Data What it is Who chooses it
Sample records (default) Records made from the app’s tables, with realistic shapes and no real data. Anyone who may change the app
Copy of live data without personal data The live data, with names, e-mail addresses, phone numbers and other personal fields removed and free text masked. Notes and form entries people saved in the app are never copied. A workspace admin

Removing personal data can miss a field, for example a name hidden in a code. Check the copy before you share staging, and choose it only where sample records are not enough. Every change of the data is recorded in the team’s activity.

Staging variables

Staging gets the app’s plain variables and its own variables, set under Staging in the app’s settings. The live app’s secrets never reach staging, so staging cannot act with live credentials by accident: set test credentials there instead. Staging also never writes to your connected tools; it can read them with your own rights.

Rolling back

Making a version live does not change how rollback works: Bring it back on an earlier version still restores its code and its data in one step. Staging stays as it is.

Where it runs

Staging runs on your team’s runner, next to the live app, like every app. If the runner is offline, staging starts as soon as it is back.

Last updated: January 1, 0001

Open kanman