Working in the Superadmin Area
What superadmins typically do here
The superadmin area supports global platform administration rather than tenant-local operations.
Typical activities:
- manage companies
- review global users and access
- maintain platform-level mail or identity settings
- monitor host, Redis, storage, and application health
- review worker and cleanup behavior
Recommended working pattern
- confirm whether the issue is global or company-specific
- make the smallest useful platform-wide change
- review the operational effect before changing more
This is especially important because superadmin actions often have broader consequences than normal admin changes.
Typical operational cases
Company onboarding
Create the company context first, then align the user and access model that belongs to it.
Global mail or identity change
Treat these as cross-platform changes and verify their effect carefully.
Platform health review
Use metrics, storage, and worker-related pages to understand whether the platform is healthy or moving toward backlog and pressure.
Good habits
- separate global issues from tenant-local issues early
- make platform changes in controlled steps
- read metrics together rather than one panel in isolation
- treat worker tuning as an operational tool, not as a cosmetic setting
Common mistakes
- using superadmin rights for changes that belong in company-level admin
- changing several platform-wide defaults at once
- reacting to one technical signal without checking the broader system picture