Admin guideCapabilities
What is optional
Unconfigured capabilities are absent, not disabled — the rule, the one exception, and the list.
An optional capability you have not configured is absent: no greyed-out control, no empty tab, no button that explains itself. A disabled control invites a support question; an absent one reads as what it is.
| Not configured | Result |
|---|---|
| Artifact store | Its routes 404; nothing in the UI |
| Isolated backend | The mode is not offered |
| App storage | No storage on any app |
| Background jobs | On by default. Switched off, no job runs and no schedule fires. With no cluster, runs go to the platform’s own machine |
Admin → System info and Admin → Checks show what is
on. On Checks an unconfigured capability reads skip with a reason, never fail.
Operating dials are not capabilities: a dial always has a value, with the environment as its floor.
The list
Section titled “The list”| Capability | Configured by |
|---|---|
| App storage | A storage resource, and a mount or a bucket |
| Integrations | A connection per kind |
| An SMTP relay or a sending API | |
| The gallery | A setting; off by default |
| Telemetry | A collector endpoint |
| The artifact store | ARTIFACT_* variables |
| Isolated execution | A Kubernetes or ECS cluster |
| Jobs | background_jobs_enabled, and the cluster or the platform’s machine |
| Reachability | Nothing — active whenever an app is public; inert if the internet cannot resolve the install |
| Dependency policy | A setting, and an advisory feed |
| Connected git hosts | A connection |
| Metrics endpoint | METRICS_ADDR |