Running Apps
Run a published app and understand the sandbox and permissions that keep it safe.
Once an app is Live and shared with you, running it is as simple as opening it.
Opening an app
Click a Live app in the gallery (or open a link someone shared) and the app runs. Behind the scenes Opisense loads the app's published version and runs it in a secure sandbox — you just see the working tool.
If you open an app that hasn't been published yet, you'll see App not published yet instead. If you're the owner, there's a shortcut to jump into the builder and publish it.
The sandbox and permissions
Every app runs inside a sandbox. It can only do what its published version declares it needs, so running someone else's app can't quietly reach into data it wasn't granted. The app's permissions travel with the version that was published, which is why publishing a new version is how capabilities change.
Destructive actions
If the app's owner left the confirm destructive actions policy on, the app stops and asks you to confirm before doing anything that could change or remove data. This is a safety net for tools that write or delete — confirm only when you mean it.
Owner actions
If you own the app (or were shared in as a Builder), you'll also see management controls while running it:
- Build — jump back into the builder chat to make changes
- Share — manage who can run or edit the app
- Activity — review what the app has been doing
- Confirm destructive actions — toggle the safety policy
People shared in as a User see the running app only, without these controls.