Administration
Operating a realm's users and data: the admin API and UI, the command line, audit trail, erasure, compliance and the security model.
These pages are for whoever runs a realm — not for application code:
| Task | Page |
|---|---|
| Manage users and roles from a service | Admin API |
| Point-and-click administration | Admin UI |
backd-server bootstrap, backd login, day-to-day CLI | Command line |
| See who did what | Audit trail |
| Deactivate or erase a user | Deleting and erasing users |
| Personal data, consents, retention | Compliance |
| Move an app between instances, seed staging, extract a report | Exporting and importing |
| What backd protects, and the pre-exposure checklist | Security model |
backd, the command line for developers and administrators: the project tools on CONFIG_DIR, and a running backd’s admin API for users, keys and data.
backd-serverbackd-server runs the server roles (serve, worker, executor, egress, provision) and the tools that work on MongoDB or run Deno directly: bootstrap, functions build, offline export and import.
Admin APIManage a realm’s users and roles from server-side services with an API key.
Admin UIThe web interface for operating a realm: switching it on, who sees what, and where to serve it.
Audit trailA permanent, append-only record of who changed users, roles, network restrictions, API keys and invitations, and when.
Deleting and erasing usersDeactivate an account and keep its data, or erase a user: a tombstone, and the collections’ policies applied. What is kept, and for how long.
Compliance with backdWhat backd provides for privacy compliance (personal data scope, consents, erasure, retention) and what stays your job.
Exporting and importingMove a realm, a database or some collections between instances as a package, seed staging with anonymized data, or extract a report.
Security modelWhat backd protects, how, and a checklist before exposing it.