Nia documentation · Latest
Administration
Configure Nia accounts, email delivery, storage quotas and optional BrainDump access.Open /admin on your instance and sign in with the administrator password created during initial setup. The administrator account is separate from normal app users.
Instance settings
Configure the public base URL first. It is used for password/setup links, email verification, passkeys, push configuration, OIDC callbacks and native integrations.
The network settings also control:
- allowed CORS origins
- trusted reverse proxies
- forwarded client-address handling
See HTTPS and reverse proxy before exposing the instance publicly.
Users
Administrators can create, edit and delete users, manage active sessions and reset a user’s 2FA state. New users set their own password through a one-time setup link.
- With working SMTP, the link can be sent automatically.
- Without SMTP, copy the generated link and deliver it to the user yourself.
- The initial regular user is created during first-run setup.
If the administrator password is lost, use the server-side reset tool:
# Debian/systemd
sudo nia-todo-admin-password-reset
sudo systemctl restart nia-todo
# Docker Compose
docker compose exec nia-todo nia-todo-admin-password-reset
Email and SMTP
SMTP enables invitations, password setup/reset, email verification and email-code fallback where supported.
Configure:
- SMTP host and port
- security mode: STARTTLS, implicit TLS or none
- optional SMTP authentication
- From address and display name
- optional Reply-To address
- one-time password-link lifetime (1–168 hours)
Save the configuration, send a test email and confirm the public base URL before inviting users. Stored SMTP passwords are not displayed again.
Tasks attachments and quotas
Administrators can enable Tasks attachment uploads globally, select allowed file extensions and set the default quota. A user-specific quota overrides the default. These settings control uploads; they do not give a user access to another person’s tasks.
A retained attachment counts against its uploader’s quota only while that uploader can still access its task. Access may come from personal ownership, a shared project or household membership. For example, a user who uploads a file to a shared project is charged while they have access. If their last access source disappears, the retained file stops counting against their quota. If access is restored, it counts again. No other participant or household receives the charge instead. Retained files from a deleted uploader account are uncharged.
Other participants can read an attachment when they can read its task, even if their own upload quota is zero. Removing an uploader’s access does not itself delete retained files. Deleting the task removes its attachments; quota accounting is not a backup or retention policy.
Uploaded files are authenticated and included in packaged backups when the attachment directory remains below the main data directory. Your reverse proxy’s request-size limit must accommodate the uploads you permit.
Recipe title images
Recipe images are separate from Tasks attachments and do not use an account’s attachment quota or its attachment-upload allowance. Nia verifies and normalizes supported raster images to bounded WebP images, stored with the recipe in SQLite. Access follows the containing cookbook; an image URL is not public access to the image.
Include the SQLite database in backups even if you separately copy the attachment directory. Monitor disk space for both: an attachment quota does not cap the total database size or all retained files.
The attachment accounting service and recipe image service define these separate storage rules.
Modules, sharing and personal memory
Users select their visible Tasks, Shopping and Recipes modules in their account settings. This is not an administrator entitlement switch, and hiding a module does not delete its content. BrainDump has a separate administrator-controlled per-user permission.
Projects, shopping lists and cookbooks can be personally owned or owned by a household. Membership and direct invitations determine access; an administrator’s instance password is not a household role. Content editing and collection management have different permission boundaries. Check the participant’s current access rather than assuming that knowing an item ID, owning an upload or hiding a module changes authorization.
Destination memory is personal to the account and works without an AI model or BrainDump access. Users can disable learning or delete remembered assignments in Settings → Memory. The same memory is used by normal Tasks/Shopping entry, moves, BrainDump and recipe ingredient transfers. It is not shared with the other participants in a collection.
Optional services
The admin panel also contains:
- BrainDump provider and per-user access settings
- OIDC and global 2FA policy
- update status and installation controls for supported Debian packages
After major configuration changes, sign in once in a private browser window to verify the full login flow before closing your existing admin session.