Admin Page Tour Print

The Admin page is where most owner-level maintenance happens inside Cockpit. It brings together updates, module handling, backup and restore tools, cleanup scheduling, storefront management, and other operational controls.

When to Use This

• You are new to Cockpit and want to understand the main owner workflow page.
• You need to know where updates, backups, and restore options live.
• You want to train another operator on the safe parts of the admin area.
• You want a quick explanation before using the admin tools on a live panel.

What the Admin Page Usually Contains

The exact layout can evolve, but the Admin page typically groups together tasks such as:

• base panel update checks
• updater readiness and permission guidance
• installed module management
• backup and restore tools
• cron cleanup setup
• storefront management

How to Approach the Page Safely

1. Start by reading the status and helper text before clicking any action buttons.
2. Check updater readiness first if you plan to run updates.
3. Use backup options before making changes that could affect live data.
4. Review module lists carefully so you know whether a module is installed, outdated, or available remotely.
5. Treat restore tools and destructive maintenance actions as planned operations, not casual clicks.

Expected Result

After learning the Admin page layout, you should know where to go for updates, backups, module operations, scheduled cleanup, and partner storefront settings without needing to guess.

Important Areas to Understand

• Updater readiness: Tells you whether the base panel is ready for update extraction and install steps.
• Backup and restore: Lets you export or re-import matching configuration data when you need recovery or migration support.
• Cron cleanup creator: Helps generate reusable cleanup jobs for runtime files, downloads, JSON data, and other selected categories.
• Storefront management: Lets you manage partner storefront entries and control whether those integrations are enabled.

Common Mistakes

• Running an update without checking readiness: This is one of the easiest ways to create avoidable install issues.
• Restoring the wrong backup package: Restore actions can overwrite matching data sets, so confirm the archive before uploading it.
• Turning on storefronts before testing endpoints: Save and verify the endpoint first, then enable it panel-wide.
• Treating cleanup settings as harmless: Some cleanup categories remove stored state and should be reviewed carefully.

Example Use Cases

• Routine maintenance: An owner logs in weekly to check for base updates, review modules, and confirm cleanup jobs are still correct.
• Pre-update safety pass: Before updating the base panel, the admin creates a fresh backup and checks updater readiness.
• Partner rollout: A reseller adds a storefront entry for a supplier and tests the endpoint before enabling storefronts globally.

Good Habits on the Admin Page

1. Keep a recent backup before major changes.
2. Read warnings in the restore and cleanup areas instead of skipping them.
3. Make one operational change at a time when the panel is live.
4. Use module and update actions deliberately, not in bulk without review.

Related Articles

• What Updater Readiness Means
• How to Update Cockpit from the Admin Page
• How to Manage Installed Modules
• How to Restore a Backup Safely