Services / user manual
API Keys and Settings
Configures application access and panel behavior. Stores credentials and operator-selected settings.
Define repeatable templates and external integrations for workloads.
Definition and integration flow
Forge control plane
How to use it
Operator workflow
- 01
Open API Keys and Settings from the administrator panel and review the current state.
- 02
Set the specific configuration that expresses the desired api keys and settings outcome.
- 03
Save deliberately, then follow the operation, activity, health, or runtime observation that confirms the result.
- 04
Keep the before-and-after evidence in Activity and verify the workload path before relying on the change.
What Forge owns
Boundary and safety
Templates and integrations define repeatable behavior. Review variables, credentials, and event destinations before they are assigned to live workloads.
Review the affected node, workload, route, or secret before saving. Capture state and health evidence before changes that affect data or public traffic.
Before you finish
Verification checklist
- The operator has the required administrative role.
- The intended node, workload, or project is selected.
- The resulting operation or observation reaches a terminal state.
- A rollback path exists before changing production traffic or storage.
Continue the manual
Use this feature in the wider Forge workflow.
Move from platform understanding to the relevant operating guide when you need exact environment, network, deployment, or recovery steps.