Maurice
7da0080557
* docs(wiki): correct the install and operations pages for 4.0.0 Quick Start passed docker an empty ENCRYPTION_KEY: an assignment prefix is not expanded on the same command line, so the server silently generated its own key instead of taking the one the page told you to set. The tag examples pinned to the 3.x line, the documented tmpfs size did not match the shipped compose file, and several .env values were described as reaching the container when compose never interpolates them. * docs(wiki): match the MCP reference to the registered surface The scope table was missing the whole Collections group and the totals said 27 scopes across 13 groups where the code registers 29 across 14. The Cloudflare link on the setup page pointed at an anchor on its own page instead of the heading on Troubleshooting. * docs(wiki): correct the plugin and admin pages Three links to Plugin-Development carried a .md suffix, which does not resolve on the wiki. The admin pages described tabs, permissions and storage behaviour that had moved on. * docs(wiki): bring the feature pages back in line with the app Costs still documented the old panel, where categories could be added, renamed, reordered and deleted; they are fixed now and the panel is a day-grouped ledger with settlements. Trip sharing, journeys, maps, packing, reservations and the account pages had all drifted in the same way. * docs(wiki): cover the pages the first pass did not reach The MCP catalog listed 168 of the 201 registered tools; the settlement tools and rate_place were missing here and the Collections family from the addon page. Several resource rows claimed a trips:* scope where the handler asks for trips:read. * docs(wiki): tighten the corrections a review picked apart The audit-log resource is the row id, not the credential id; an admin password reset does not bump password_version the way the page implied; and a few of the new paragraphs described behaviour more confidently than the code supports. * docs(wiki): fix what a last read-through caught Costs shows every figure in your display currency, not the trip's, and an expense with no payer still counts against the members it is split between. Studio's cutoff is a 1024px viewport rather than phones alone, and the Integrations tab is gated on the providers an admin has configured. * docs(wiki): the last few the review caught A passkey satisfies the MFA policy everywhere except the WebSocket handshake, which still asks for TOTP, so a passkey-only account under that policy gets no live updates. Mobile optimizes a day from two places, not three. The ctx.db row carried an unescaped pipe that split the table, and the Backups table linked with a wiki link whose pipe did the same.
3.9 KiB
Admin — Users and Invites
The Users tab in the Admin Panel lets you view all registered users, manage their accounts, and create invite links so new people can register without open registration.
User list
The user table shows every registered account with the following columns:
| Column | Description |
|---|---|
| User | Avatar, username, and an always-visible presence dot (green = online, grey = offline) |
| Account email address | |
| Role | Badge showing Administrator or User |
| Created | Account creation date |
| Last Login | Date and time of most recent login |
| Actions | Edit and delete buttons |
Your own account row is highlighted. You cannot delete your own account.
User actions
Edit a user
Click the pencil icon on any row to open the edit form. You can change:
- Username
- Email address
- Role — a dropdown with User and Administrator
- Password — set a new password; must be at least 8 characters
Click Save to apply changes.
Below the fields sits Reset passkeys, which removes every passkey that user has registered — the recovery path when someone loses their authenticator. It asks for confirmation, reports how many passkeys it removed, and takes effect immediately rather than on Save. The user can still sign in with their password. See Passkeys.
Delete a user
Click the trash icon and confirm. Deletion is permanent. The user's account is removed from the database along with their data (cascade behavior is enforced at the database level).
You cannot delete your own account while logged in as that user.
Creating a user directly
Click Create User (top-right of the Users tab) to create an account without an invite link. You set the username, email, password, and role at creation time.
Invite links
Invite links let a specific number of people register themselves. This is useful when open registration is disabled.
Creating an invite
Click Create Link (invite links section, below the user table). Configure:
- Max uses — how many times the link can be used before it expires:
1×,2×,3×,4×,5×, or∞(unlimited). Defaults to1×. - Expiry — how long the link remains valid:
1d,3d,7d,14d, or∞(no expiry). Defaults to7d. - Add to trip (optional) — bind the invite to a trip. Anyone who registers through the link is automatically added to that trip as a member. Defaults to No trip (a plain registration invite). The selector only appears when at least one trip exists.
After creation the link is copied to your clipboard automatically. Share it with the intended recipient. The URL format is:
<APP_URL>/register?invite=<token>
Invite list
Existing invites are listed below the creation button. Each row shows:
- The invite token (truncated, monospace)
- A status badge —
active,used up, orexpired - Usage —
used / max(orused / ∞for unlimited) - Expiry date, if set
- Adds to — the bound trip, if the invite is trip-bound
- Created by — the admin who generated the link
- A copy link button (only shown for active invites)
- A delete (revoke) button
Revoking an invite immediately invalidates it; anyone following the link after revocation will receive an error.
Permissions
The Users tab also hosts the Permissions panel at the bottom, which controls what roles can perform which actions. See Admin-Permissions for details.