Admin And Settings

The Admin section holds the system-wide controls that do not belong inside a single workflow or playbook.

Main Surfaces

API Keys for operator and service access
General Settings for tenant-level posture
Agentic Settings for runtime defaults and prompt warning posture
Platform Settings for activation timing, fleet behavior, and supervision defaults

API Keys

This is the access-control surface for operators and services that need to talk to the platform without going through a browser session every time.

Agentic Settings

These settings are the shared defaults for runtime-facing behavior that should not be configured ad hoc on every workflow.

Platform Settings

These settings shape control-plane loops and supervision posture. They matter because a workflow system is not only about prompts; it is also about timing, attention, and recovery behavior.

Why This Matters

These settings shape the operating posture of the whole system. They are not per-workflow authoring fields. They are the shared defaults and access controls that make the control plane usable in practice.

Public-Repos Point

For a public docs site, this section is also where outside operators learn that Agirunner has real system settings and access-control surfaces, not only workflow authoring screens.

How It Connects To The Rest Of The System

Admin and Settings is the layer underneath the more visible workflow and runtime pages:

API Keys controls who can access the platform, API, and integrations
General Settings controls broad logging and retention posture
Agentic Settings controls shared specialist execution defaults
Platform Settings controls supervision, timing, and control-plane behavior

These pages do not usually create work directly, but they shape how the rest of the system behaves once work is launched and observed.