User Management
On a single-workspace instance, an administrator manages database users under Settings > Users. In multi-workspace mode, use Settings > Members for membership of the active workspace. The steps below describe the single-workspace Users panel.
Add a user
Section titled “Add a user”- Open Settings > Users and select Add User.
- Enter an email address, optionally add a name, and choose User or Administrator.
- Leave Send invitation email selected to send a setup link, then create the user.
The user record and setup token are created even when email delivery fails. The interface reports a failed send; check Email Configuration before resending. Setup tokens expire after seven days.
The same operation is available through POST /api/admin/users with an admin session and a JSON body:
{"email":"newuser@example.com","name":"New User","role":"user","sendInvitation":true}User creation is limited to 20 requests per admin per hour. The API returns invitationSent so callers can distinguish user creation from successful email delivery.
Roles and invitations
Section titled “Roles and invitations”A database user has either the user or admin instance role. Admins can manage users, instance settings, webhooks, and email configuration. AUTH_ADMIN_EMAIL also grants the configured account admin access. OIDC deployments may map groups through OIDC_ADMIN_GROUPS; see Authentication.
A new user has no password until they use the setup link. For a user without a password, Resend invitation rotates the token and sends an activation reminder. The response reports whether the email was sent. Existing users can request a magic login link or password reset from the login screen. There is no Reset Password action in the Users tab.
Edit or remove a user
Section titled “Edit or remove a user”Select Edit to change a user’s name or role. Administrators can also manage the designer flag for the user’s workspace membership. The list shows email, name, role, password state, invitation state, and last login when available.
Select Delete to remove another user’s account. An admin cannot delete their own account this way. The delete operation removes the user row and pending reset tokens; it does not explicitly delete or transfer the user’s presentations. Transfer ownership before removal when needed. See Sharing & Permissions and GDPR & Privacy for related data handling.
The admin API also supports GET /api/admin/users, PATCH /api/admin/users/{userId}, DELETE /api/admin/users/{userId}, and POST /api/admin/users/{userId}/resend-invitation. User creation and deletion write auth audit events with request IP and user agent. The Users tab does not include a separate audit-log screen.