Skip to content

Install and run

Offered apps from your libraries appear in the app library as Custom · owner/repo. Opening one shows its tools and the address it reaches. Install asks only what the file asks:

  1. Its settings, including the app’s address.
  2. Run on: one of your tunnels that runs custom apps.
  3. Who signs in: the workspace once, or each person.
  4. The approval of exactly what will run.

Nothing runs until an admin approves it. The approval covers one exact version: the code, the address, the settings, the tunnel and every tool.

A new version, a new setting, a new address or another tunnel needs a new approval. The approved version keeps running until then. When you approve an update, the console shows what changes. Changing the address or the tunnel clears the app’s sign-ins.

State
Awaiting approval Installed, but nothing approved yet.
Running The approved version runs on its tunnel.
Update pending A newer version or setting waits for approval. The approved one keeps running.
Paused An admin paused it.
Stopped Custom apps are off on its tunnel.

Every tunnel runs custom apps by default. An admin can turn them off per tunnel in the tunnel’s settings. Their approvals stay for when you turn it back on.

A tunnel that does not offer Run on may be an older version: update it.

  • Socket tools (IMAP and SMTP) do not run in the tunnel yet.
  • Give custom apps a tunnel of their own if you want them apart from your other apps.