Files
AdventureLog/documentation/docs/guides/admin_panel.md
Sean Morley d22c55e182 Refactor deployment configurations and update documentation
- Replaced the All-in-One (AIO) deployment setup with a Standard Deployment configuration, introducing .env.advanced.example for advanced settings.
- Updated .dockerignore to reflect the new environment file structure.
- Removed .env.aio.example and associated references from documentation and workflows.
- Enhanced installation instructions to clarify the new Standard Deployment process.
- Updated GitHub Actions workflows to align with the new deployment structure, including smoke tests and image builds.
- Improved documentation for environment variable references and deployment options.
2026-06-12 21:49:01 -04:00

43 lines
1.8 KiB
Markdown

# Admin Panel
The AdventureLog admin panel is powered by Django and is available at `/admin` on your backend URL. In Standard Deployment installs, that is the same domain as the frontend (for example `https://adventurelog.example.com/admin`).
## Access requirements
Only users with the **staff** flag (`is_staff=True`) can access the admin panel. The first-boot superuser created from `DJANGO_ADMIN_*` environment variables has staff access by default.
## What you can manage
| Section | Description |
| ------- | ----------- |
| **Users** | Create, edit, and deactivate user accounts |
| **Locations** | View and manage location records in the database |
| **Social applications** | Configure OAuth/OIDC providers (GitHub, OIDC, etc.) |
| **Invitations** | Send invite links for private instances |
| **World data** | Countries, regions, and cities reference data |
## CSRF configuration
If the admin panel loads but form submissions fail, verify `CSRF_TRUSTED_ORIGINS` in your `.env` or `.env.advanced` includes your public domain:
```env
CSRF_TRUSTED_ORIGINS=https://adventurelog.example.com
```
When using a single domain, set `SITE_URL` instead and the origins are derived automatically. See [Environment Variables](../configuration/environment_variables.md#url-and-networking).
## Social auth setup
OAuth and OIDC providers are configured in the admin panel under **Social applications** and **Social accounts**. Step-by-step guides:
- [Social Auth overview](../configuration/social_auth.md)
- [GitHub](../configuration/social_auth/github.md)
- [Authentik](../configuration/social_auth/authentik.md)
- [Pocket ID](../configuration/social_auth/pocket_id.md)
- [OpenID Connect](../configuration/social_auth/oidc.md)
## Related guides
- [Invite a User](invite_user.md)
- [Disable Registration](../configuration/disable_registration.md)