Owner administration and health checks
What belongs to the platform owner, what website administrators configure, and how to read health-check results safely.
On this page
A regular administrator works with the content and settings of the selected website. The Owner section is intended for the owner of the entire platform: it manages projects, central administrator accounts and services that affect more than one website. Therefore, regular users correctly do not see it.
Common web settings
In Web Settings you edit the data belonging to the selected project, for example name, registration behavior, basic SEO and enabled measurement. Always check the selected website in the header before saving.
What belongs to the Owner section
| Screen | Purpose |
|---|---|
| Owner dashboard | platform central management overview |
| Websites and projects | registration and status of managed websites |
| Administrators | central administrator accounts and their assignments |
| Settings Owner | central host settings, not single site content |
| SCUM licenses | central overview of eligible licenses |
| NODERAgent releases | managing approved packages and their availability |
| Managed hosting | central overview of managed server services |
Do not use the owner interface to bypass a regular module. If the change belongs to one website, make it in the module of the given website, where the result and the history are understandable.
Health check is first a diagnosis
On the Health Check page you can see the results of the available checks. Opening the page itself is safe reading: it does not trigger a restart of the site, SCUM server or NODERAgent.
| Result | Recommended Response |
|---|---|
| Okay | no action required |
| Warning | open the detail and compare it with the expected state |
| Error | record the time, extent and service affected; proceed according to the runbook or via support |
| Unknown | check did not have enough data; don't automatically assume an outage |
Manual control and intervention are not the same thing
If an authorized administrator runs a manual scan, Nodera will only refresh the diagnostic results. Restarting, deploying, migrating or changing server settings is a separate sensitive operation and requires its own approved procedure.
Safe owner procedure
- Determine whether the change belongs to one site or the entire platform.
- Verify the target project, account, or service.
- Before taking a sensitive action, read its scope and current status.
- After the change, check the result on the relevant screen and in the Health Check.
- If unclear, stop further interventions and escalate with the time and name of the check.
When you don't see the Owner item
This is expected for a regular administrator. Do not try to bypass it with a direct address. Ask the platform owner for a specific change or for a well-defined permission.