Platform administration and content operations for authorized Bakasir operators.
The Super Admin panel is separate from a tenant login. Only authorized platform operators should use it. Every cross-tenant action must be justified and audited. Use impersonation only for a defined support case and keep its visible indicator in view.
| Area | Use it for |
|---|---|
| Dashboard | Platform health and high-level tenant/subscription activity. |
| Tenants | Search tenant details, status, security, and manual Owner email verification after proof of mailbox control. |
| Plans & Billing | Plan rules, outlet billing, plugin prices, renewal and provider state. Verify commercial settings before publishing. |
| Users & Access | Admin roles, login controls, and audit review. |
| Licenses & Operations | Self-hosted license lifecycle, system operations, migration/backup visibility and safe service status. |
| CMS & Marketing | Blog, News and Careers drafts/publishing, legal copy, announcements, campaigns and media. Landing Page layout is code-managed, not a CMS editor. |
| Supports | Tenant tickets/live chat and security reports. Vulnerability reports are restricted to Super Admin. |
| Settings & Seeder Data | Platform logo light/dark, integrations, notification templates, core reference images, and managed demo datasets. |
For a new Blog/News/Careers entry, create a draft, choose locale and slug, add the image and allowed content blocks, preview, then publish. Do not publish unsupported claims or private tenant details. Demo seed changes must keep core categories and units distinct from removable demo records.
Open Settings and select the intended section: Global for platform identity, Appearance for Logo Light/Logo Dark and visual assets, Security for administrator controls, OAuth for configured identity providers, Payment for gateway credentials, Notification for delivery templates, Plugins for the official registry, Seeder Data for reference/demo catalog, Database for protected data tools, and Health for safe service status. Save one group at a time and wait for confirmation. A Test Connection action may test stored credentials rather than unsaved edits; save first and verify the actual provider result.
Operations separates Audit Logs, System Logs, Monitor, and Translations. Keep internal infrastructure addresses and raw health details behind Super Admin access; the public status page only exposes safe service summaries.
Production operations
Never run a destructive tenant reset, restore, manual data patch, or provider credential change without an approved operational plan and a verified backup.