Platform settings
The platform's administration sections, one at a time: processes, limits, antivirus, email, alerts, OpenTelemetry, artificial intelligence, app authentication, mobile app, templates, unused files, installation and open source.
The Settings are the control panel of the whole installation. They are not the settings of an app — those live inside each app and travel with it. Here is where you decide what the platform does on its own, where it sends its warnings, from what values it starts worrying, and how long a session lasts.
It opens through the Settings item, at the bottom of the sidebar. Only accounts with an administrator profile get in.
The sections are in a navigation on the left, in groups: Platform, Warnings, Observability, Artificial intelligence, Apps, Installation and About. One section opens at a time, and the address changes with it, so the browser's back button goes to the previous section. The Installation group only appears in a single-organisation installation. On a narrow screen, the navigation becomes a drop-down list above the section.

Note
Each section has its own Save button, in the header, and it saves only that section. Switching sections without saving loses what was typed in it.
Processes
The Processes section turns on and off what runs while nobody is watching. There are three independent switches:
| Switch | What happens when it is on | What you lose when you turn it off |
|---|---|---|
| Scheduler | Runs the schedules, the scheduled reports and the workflow timers. | Nothing is deleted: the appointed times simply do not run until it is back on. |
| Observability index | Moves what the apps record into the central index and applies each app's retention periods. | The Radar screens show stale data and the logs are kept forever. |
| Real-time notifications | Notifications reach the screen of whoever is working, on the spot. | Notifications go on being created and delivered — but they only appear on the next visit. |
The email warnings switch is in the Alerts section.
Each switch takes effect when you click Save, without restarting the server: what you turn on starts at that moment, and real-time notifications that you turn off close straight away.

Warning
Turning off the Scheduler is the number one cause of "my scripts stopped running". If a schedule looks dead, check this switch before investigating the script. The same goes for scheduled reports and for wait steps in workflows — they all depend on the same engine.
Antivirus
The Antivirus section connects the platform to an antivirus over ICAP, so that the files entering the apps are scanned before they are stored, and shows the files in quarantine. It is explained in Antivirus.
This is how the platform sends its own alarms — not to be confused with the email each app sends to its users, which is configured in the app's notification channels.
Fill in:
- Server and Port of the email service.
- Security — SSL/TLS encrypts from the start of the connection (port 465); STARTTLS if the server offers it opens the connection without encryption and switches to TLS if the server offers it (port 587); None never encrypts, for internal servers without TLS (port 25). Without a user and password, sending doesn't authenticate.
- User and Password of the sending account. The password is written once and never comes back to the screen: the field starts saying it is set, and leaving it empty means "do not touch", never "delete".
- From — the address that appears to whoever receives.
- Recipients: addresses, separated by commas, that receive every alarm. Blank, each app warns the people assigned to it, and apps with nobody assigned and the platform warn the active administrators.

Alerts
The Alerts section says whether the platform warns by email and from what values.
The Email warnings switch, at the top, turns the warnings on. When it is off, nobody is warned, and problems are only discovered by opening the Radar. The warnings go out through the server in the Email section.
A new problem in a published app, or a resolved problem that happens again, always warns, with no threshold. What triggers each alert and what the email says is in Email alerts.
The Thresholds tell the platform what is normal and what deserves an email. All of them are evaluated within the window defined at the end of the section.
| Value | What it means |
|---|---|
| API server failures (%) | Percentage of requests that fail on the server (5xx) above which a widespread failure alarm opens, with at least 5 failures in the window. Refusals, cancelled requests and validation errors do not count. |
| Minimum requests | Below this number of requests, the percentage does not count. One error in three requests is 33% and means nothing. |
| Failed scripts | How many failed runs open an alarm. |
| Queue lag (s) | How long the background work may fall behind before being considered late. |
| Free disk (%) | Below this percentage, warn. |
| Window (min) | The period everything above is counted over. |
Tip
On an installation with little traffic, raise the Minimum requests. It is the field that avoids false alarms in apps that are only used in the morning.
Limits
Two settings that apply to the whole platform:
- Session length (h) — how long a session lasts without activity. While you work, the session renews itself; only prolonged inactivity forces you to sign in again.
- Max file (MB) — the maximum size of a file uploaded in any app of the installation. It also applies to files uploaded to an app's assets. It goes up to 100 MB. Importing apps does not depend on this value: it accepts packages up to 1 GB (see Importing and exporting apps).
OpenTelemetry
The OpenTelemetry section, in the Observability group, sends what happens in the apps to the company's OpenTelemetry server, over OTLP/HTTP in JSON. The Radar keeps working as before: the export is a copy.
- In Endpoint, type the base OTLP/HTTP address, for example
https://otel.empresa.pt:4318. Keplin adds/v1/tracesand/v1/logs. - Optional: in Headers, click Add header and type the Name and
the Value of the service's authentication headers, for example
Authorizationorx-api-key. The values are stored encrypted and do not appear again; left blank, the saved value stays. - In What to send, choose:
- API calls and script runs, as traces, with the trace and span IDs that Keplin already uses;
- Radar errors, as logs, with the type, the message and the error's stack trace, linked to the trace;
- Audit, as logs: who changed what on the platform, without the before and after;
- Browser activity, as traces: the screens opened, the clicks and the reads. It is a lot: turn it on only if the service can take it.
- Click Test connection. The test passes when the server accepts a test export.
- Turn on Send to OpenTelemetry and click Save.

The export starts the moment it is turned on, without the history. The request and response data are never sent. The Status shows the time of the last export and how many spans and logs went out since the server started, and the last error, if it is more recent than the last export.
Public address
The Public address is the address people use to open the platform, for
example https://platform.example.com. It is the one used in email links,
such as the password recovery link for app accounts. The section is in the
Installation group, which only appears in an installation with a single
tenant; in multitenant, each tenant's address applies.
It is filled in at the first administrator sign-in, with the address the administrator used. If that is not the address people use (for example, if the administrator signed in through the internal network IP), correct it and click Save.
Without a Public address, password recovery only works for apps published on their own domain. The address that comes with a request is never used for the link, because whoever makes the request chooses it.
The platform's PostgreSQL server
For internal PostgreSQL datasources (see Connecting databases), the installation needs a PostgreSQL server where the platform creates the databases. The configuration belongs to the installation, not to an app: in a single-organisation installation it lives in Settings, in the Managed PostgreSQL section of the Installation group; in a multi-client installation it lives in the installation's back office. Fill in the address, the port, the administration account and the limit of databases per client, save, and use Test server to confirm that the platform can create databases on that server. Until it is configured, the PostgreSQL option of the Internal tab is disabled when creating a datasource.
Browser engine
The screenshots that agents ask for through MCP and the screen tests (see The test project) use a browser without a screen that runs on the server. There is only one for the whole installation, in a separate process with low priority: when the machine is under pressure, the browser gives way, not the apps' requests.
The Browser engine section, in the Installation group (in a multi-client installation, in the installation's back office), shows the State (running, or closed until the next job), whether Chromium is installed, the Jobs running and queued, the free Memory and the Last error. It also has the limits that protect the server:
| Limit | What it does |
|---|---|
| Jobs at once | How many pages are open at the same time. More pages, more memory and CPU. |
| Queued requests | With the queue full, a new request is refused at once, with the reason. |
| Idle minutes before closing | Closed, the browser takes no memory; the next job opens it again. |
| Minimum free memory (MB) | Below this, no new page opens. 0 turns the guard off. |
Close the browser now gives the memory back at once. If Chromium is missing, Install Chromium downloads it; the installation and the platform updates already install it and check that it starts.
Updating the platform
Where and how you update depends on the installation mode:
- Single-organisation installation: there is no update through the interface. The Updates section of Settings shows the Installed version: and the command to run on the server console with the new version's zip, with a button to copy it. The installer keeps the settings and the data and runs the migrations; to go back to an earlier version, install that version's zip.
- Multi-client installation: the update is done in the installation's back office, under Updates, and that is the screen the rest of this section describes. Each client's Settings have no updates.
The update section shows the installed version and the list of available versions. The process has two buttons, on purpose:
- Prepare — fetches the chosen version and prepares it without touching anything that is being served. The platform keeps working.
- When the preparation finishes, the plan appears: how many databases will be migrated, which app files are rewritten and in how many versions, plus the notice that the databases are copied before anything is touched.
- Apply this update — only after you have read the plan. The platform becomes unavailable during the restart and comes back on the new version.

Note
If an app has changes on disk that are not in the history yet, the plan says so and the update records them first, in a separate entry, before it rewrites the files. Files that the platform writes on its own, such as the copies of script dependencies that a schedule makes, do not count.
If anything goes wrong along the way, the previous version is restored automatically and the screen says so — including the log of what failed.
The rollback returns the databases, and also the app files that the migrations had rewritten, to the state before the update.
Server check
On the updates screen, the Server check block shows whether the machine has what the apps' scripts, the screenshots and the screen tests need: Chromium, the scripts' isolation, the scripts' network rules and the platform processes running as the installation's user. The check runs at the end of the installation, at the end of each update and when the server starts; Check now runs it on request.
The summary says «Everything is fine.», how many warnings there are, or how many problems are still to fix. Each problem says what fails and shows the command that fixes it, to run as root on the server console.
Artificial intelligence
The Artificial intelligence group has the Providers section: the tenant's AI services that the apps' scripts can use, with the credentials and the authorised models. See AI providers.
App authentication
The App authentication section, in the Apps group, registers the providers the apps' users can sign in through: Microsoft Entra ID, Google, an OpenID Connect or OAuth 2.0 service and, in an installation with a single tenant, Active Directory. It is explained in Sign in with authentication providers.
Mobile app
The Mobile app section serves the Android app used to enter the apps of this platform. It has two files to download and one QR code per app — it is explained in detail in the Mobile app chapter.

Templates
The Templates section, in the Apps group, lists this platform's templates: the ones saved from the apps with Save as template (see App templates). System templates belong to the installation and do not appear here.
Each row shows the name, the version, the description, the app it came from, the date it was saved and the size. On each one:
- Download downloads the
.keplintemplatefile, to take it to another installation. - The bin icon deletes the template. The confirmation appears on the row itself: click Delete to confirm, or Cancel. The template leaves the New app gallery, and the apps already created from it do not change.

Unused files
Files uploaded to the apps are not deleted on their own: not when the record that had them is deleted, not when an attachment is replaced, not when a form is left halfway. The Unused files section finds them and lets you choose what goes. Nothing is deleted on its own.
- Click Find unused files, in the header. The search runs in the background on the server: you can leave the page and come back, and it carries on.
- While it searches, the page shows the progress (for example, «3 of 12 apps») and what it is reading. Each app appears as soon as it finishes, with the files that no known reference uses: name, size, upload date and versions. The icon next to the name downloads the file, so you can check what it is.
- Choose the files and click Delete selected. The page asks for confirmation; before deleting, the platform checks the chosen files again, and a file that has meanwhile come into use stays.

The result is kept: when you come back to the section, the last search appears, with the date and how long it took. Search again repeats the search in every app, and Search this app, in an app's header, only in that one. Cancel the search stops a search in progress. If the server restarts halfway, the page says the last search stopped halfway. Time per source shows how long each database read took, to understand where the time of a slow search goes.
A file counts as used when its token appears in the app's design, in the app's SQLite databases (including processes and notifications) or in a text column of a model table, in any version. Read-only datasources are not read, because Keplin never writes to them. A table outside the model or an external system is not seen: check before deleting. Files from the last 24 hours are not included, and an app with a database that cannot be read is left out of the list.
Warning
A deleted file does not come back. The bytes leave the app's storage and the file leaves the registry of every version.
Open source
The Open source section lists the open source libraries installed in the platform, with the version and the licence of each one. Each library's name opens the project's page. Type in the search field to filter the list by name or by licence.
Frequently asked questions
I changed a threshold and received nothing. Alarms are only evaluated minute by minute and only within the defined window. Also check that the Email warnings switch, in the Alerts section, is on, and that the server in the Email section is filled in.
Can I have different email servers per app? Yes — and it is the normal thing. The email on this page is only the platform's warnings; each app configures its channels in its own settings.
Who can see this page? Only accounts with an administrator profile. A developer does not see it in the sidebar and does not get in by direct address either.