App files, settings and flags
Three views of an app in Apps mode (Files under People & data, Settings under Settings, Flags under Build) cover what the web console calls files, settings and feature flags. They are for apps people sign in to. Reading is open to the organization; changing needs an owner or admin, and other roles see the controls disabled with the reason.
Files
Files kept for the app on its own storage, up to 4 MB each.
| Control | Does |
|---|---|
| Folder (optional) | Lists one folder; blank lists the top level. Uploads go to the folder typed here |
| Upload | Picks a file from your computer. A larger file is refused with the limit |
| Download icon | Reads the file back from the platform |
| Delete icon | Asks first ("This can't be undone"), then deletes. Owners and admins only |
The list shows the name, folder and size. The platform decides which kinds of file are allowed and says so when it refuses one.
Files use the app's own site and its file storage, which is the disk the chat add-on runs on. An app without a site, or whose storage is not running, shows a plain message ("The app's file storage isn't running. Add the chat add-on to the app first") instead of an empty list.
Settings
What the app uses to let people sign in.
| Row | Meaning |
|---|---|
| Mode | dev or live. A dev app only lets the people it allowed sign in |
| Public key | The app's public sign-in key, with Copy |
| Stay signed in for | How long a sign-in lasts between refreshes. Read-only here; shows Default when not set |
| Verified email | Whether a verified email is required to sign in. Read-only here |
| Allowed in dev | For a dev app, the emails that may sign in |
Where people return after signing in is the one thing you can edit: one address per line, then Save. The app checks them before it sends anything: https only, no wildcards, http://localhost only for a dev app, and a live app cannot return to localhost. A problem is shown under the box and Save says what to fix. After saving, the app's sign-in key and addresses are read again.
Other settings (token lifetime, policy overrides, federation, deleting the app's sign-in) stay in the web console.
Flags
Switches that turn a module or a single workflow on or off for this app, for every plan or for one plan tier. A missing flag is not off. Only an explicit off denies the module or workflow.
| Control | Does |
|---|---|
| List | Each flag's key, kind (module or workflow), plan (all plans when blank) and an on/off switch |
| Switch | Turns the flag on or off |
| Delete icon | Asks first, then removes the flag, which makes it count as off |
| Flag key, Kind, Plan tier, Add | Creates a flag, switched on. Blank plan tier means all plans. A flag with the same kind, key and plan tier cannot be added twice |
Flags are the same records the web console shows under the app's Feature Flags tab.
Install and sign in
Platforms and installers for Orkestia Cockpit, how updates arrive, the browser sign-in with PKCE, where the session is stored, chats-only mode, signing out and switching organization
Cards in the chat
How Orkestia Cockpit draws what the Assistant and app chats answer with — tables you can sort, filter and copy, charts, KPI tiles, timelines, record details, diffs — and how to move a wide card into a panel beside the chat