# Administration

The admin panel is at https://your-domain.example/admin.

The installer creates the first administrator; promote another account from the application directory with:

```bash
php artisan make-admin user@example.com
```

| Area | What's there |
| --- | --- |
| Users | Accounts and roles, deletion requests, notifications, attachments. Sign in as a user to see what they see. |
| Docs | Workspaces (with editing and restoring a deleted one), docs sites, and the activity log. |
| AI | AI accounts, the model catalogue, and every AI request with its cost. |
| Finances | Plans, subscriptions and transactions, taxes, countries. |
| Site | The platform's public pages, blog posts, contact messages and announcements. |
| Settings | General, Colors, Admin, Emails, Storage, Media, Security, Compliance, Payments, AI, Analytics, Custom domains, Git sync, License. |

When a customer reports a problem, check in this order: the site's state on its Overview (unpublished changes, needs attention), the workspace's plan and usage, the scheduler, the application log in `storage/logs/laravel.log`, and, for AI, Git or domain issues, the request list, the sync log or the domain's status message.

## Backups

A usable backup includes:

- the complete database;
- the `.env` file;
- `storage/`, including the install marker and local uploads;
- cloud storage buckets, or their replication and versioning policy;
- custom code, themes or language files kept outside the original package;
- the cron line, the web server configuration, and the Caddyfile if you use Caddy.

Encrypt backups, keep copies off the application server, and test a restore on a staging copy. A database-only restore leaves images missing from pages; a file-only restore leaves files the database doesn't know about.