Dashboard, site selection and secure changes
How to read the dashboard, work with the right website or server and verify the change without unnecessary risk.
On this page
Dashboard is the initial control screen of the administration. It helps quickly determine if you're looking at the right website, if the content needs attention, and if basic services are available. It is not a screen that changes the website or restarts the server by itself.
What to check after logging in
- In the upper bar, verify the selected website or SCUM server.
- Read notifications and content status cards.
- Check the last activity if you need to see if another admin has already made the change.
- Only then go to a specific module.
How to understand dashboard tabs
| Type of information | What it tells you | What to do |
|---|---|---|
| Contents | how many records are published, hidden or pending completion | open the owning module and correct a specific record |
| Activity | what has recently changed in the administration | check whether it is the expected work of a colleague |
| Readiness | if critical components are available | open detail or health check first when warning |
| Maintenance | if a manual operation is available for the authorized role | run it only according to the approved procedure |
The website you choose determines what you change
The content and settings belong to a specific website. If you manage multiple projects, changing the selection in the header is the most important check before saving. With the SCUM screens, you select the server in the same way; data from one server should not be mixed with another.
A simple rule: check the name of the selected site or server and the name of the module before clicking Save for the first time.
Saved does not yet mean public
- Saved: the administration accepted the change.
- Active or published: record may be visible to visitors.
- Hidden or draft: the record remains ready in the administration, but the visitor does not see it.
- Queued: job is waiting to be processed; it is not yet a confirmation of delivery or execution.
Recommended check after change
- Save the change and wait for a success message.
- Reopen the detail in the administration and verify the saved values.
- For public content, open the landing page without an editor.
- Check both desktop and mobile and at least one other language if you edited it.
- For orders or payments, check the status on the relevant listing, not just the return page.
What the dashboard does not do automatically
Opening the dashboard alone does not trigger database migration, backup, repair or restart. If an authorized role sees the maintenance button, it is a separate conscious action with its own confirmation and result.
When the data does not fit
First refresh the page and check the selection in the header. Then open the owning module directly. If the difference remains, create a ticket with the screen name, time, and expected status; do not include sensitive credentials.