Skip to content
Enjazy documentation

Enjazy Server administrator guide

This guide is for the administrators of an Enjazy Server that your team or company runs. The admin console is where you manage the people who use the server, the sign-in apps, the server licence and the server's settings, including the AI assistant. Open it at /console on your server's address (for example https://tasks.example.com/console). Only administrators can open it.

To install the server, set up email or HTTPS, or back up and update it, see the self-hosting guide.

Signing in and two-step verification

Open /console/login on your server's address. Enter your email or username and password, then sign in. The first administrator is the one created during setup (see Setup in the browser).

If your account has two-step verification turned on, the console asks for a verification code after your password. Each digit goes in its own box; pasting fills them all. You can also use one of your recovery codes.

The sign-in page tells you clearly when the password is wrong, the account isn't an administrator, is locked or is disabled, or the network failed. A correct password on an account that isn't an administrator shows "This account isn't an administrator." and doesn't count as a failed attempt.

The console keeps you signed in on this browser. You can sign out at any time from the bottom of the side menu.

Overview

The Overview page gives you a snapshot of your server. Under People it shows four totals: Users, Active, Disabled and Administrators (active administrators only). The Server section shows the storage used, the server version, the data version and the Node.js version.

A health card shows that the server is running and for how many days, whether people can create their own accounts, and whether outgoing email is set up. The common tasks, Add account and Register app, are one click away, and Documentation links to these guides.

Accounts

The Accounts page lists every account with its email (and username under it), role, status and creation date. You can search by email or username, filter by role (Administrator or User) and status (Active or Disabled), sort by any column, and move through the pages. Export CSV downloads the list.

To add an account, choose Add account. Fill in the email (required), username (optional, 3 to 128 characters), name (optional) and a temporary password (required, at least 8 characters; Generate creates a strong passphrase). Choose the role, User or Administrator, and choose Create account.

Confirmed email addresses. If your server asks people to confirm their email address (the ENJAZY_REQUIRE_VERIFIED_EMAIL setting in the self-hosting guide), an account can't share lists or invite people until it confirms its address. The account's panel then shows Email not verified with Mark as verified: use it when you know the address is right. Each use is written to the server log as an administrator action.

An account's page

Click an account's row to open its summary panel, then Manage account to open its page; View in the row's ⋯ menu opens the page directly. From here you manage everything about the account.

Status (disable and enable)

Disable account asks "Disable this account?", then signs the account out everywhere. Its status changes to Disabled. Its data is kept, and it can't sign in again until you enable it.

Enable account turns the account back on at once, with no confirmation. The person can sign in again.

The last active administrator can't be disabled, made a regular user or deleted. The console warns you when this applies.

Email

Choose Change email and enter the new address. The new address is marked as not confirmed and, if outgoing email is set up, the server sends a confirmation email to it. A message confirms the change.

Administrator role

Choose Make administrator to make someone an administrator, or Remove administrator role to make an administrator a regular user again. Both ask you to confirm. The last active administrator can't lose the role.

Two-step verification

When two-step verification is on, the card shows "On". Turn off two-step verification… opens a confirmation that reminds you to make sure who you're talking to first. Confirming removes the person's authenticator app setup and all their recovery codes, and the card then shows "Off".

Reset password

Reset password opens a two-step dialog.

Step 1: choose how to reset: Email a reset link (a link that works once, sent to the account's email and valid for a limited time) or Set a temporary password. You can also tick Sign them out everywhere.

Step 2 (link): shows the email address and how long the link works, then sends it. A message confirms it was sent.

Step 2 (temporary password): enter a new password (or use Generate). The temporary password is then shown once. You can copy it, but it is never stored or written to a log. The person isn't asked to change it at their next sign-in.

Sessions

The Sessions card lists where the account is signed in: the app, the browser or device, when it signed in and when it was last used. Sign out on a row ends that session at once. Sign out everywhere… ends them all, after you confirm ("{n} session(s) end now. They can sign in again.").

Data and storage

The Data and storage card shows how much the account holds: lists, tasks, to-dos, done items, projects, tags, comments, task versions, sync changes and the total storage used.

Deleting an account

Delete account… asks "Delete this account?" and lists what will be lost: its lists and everything in them, every session and, when it owns shared lists, the sharing of those lists. The dialog has a Download backup button. Type the account's email to confirm. The account, its data, the lists it shared and its memberships are then removed. You can't delete your own account or the last administrator.

Sign-in apps

Sign-in apps are the apps allowed to sign people in with their accounts on this server, for example a tool your company built. The Sign-in apps page lists each app with its name, client ID, type (Public or Confidential), whether it asks people for consent (Trusted or Asks for consent), and its redirect addresses. You can search by name or client ID and export the list as CSV.

Choose Register app to add one. Give it a name and its redirect addresses (one per line, full addresses), and mark it as a public app or a trusted app of your own if it is one. A public app appears in the list at once. A confidential app also gets a client secret, shown once: copy it before you close the dialog, as you can't see it again.

From a row's ⋯ menu or the app's details panel you can rename the app and change its redirect addresses, replace its client secret (confidential apps only), or delete it. Enjazy's own apps can't be changed or removed.

Settings

The Settings page holds the options for the whole server:

Server license

This section shows the server's plan (Free or Server Pro), its Server ID and the state of its licence. From here you can Upgrade to Pro, install or replace a server key, open Manage subscription, Send the key again to your email, or Detach license to move it to another server. See Server licence for how buying, renewal, checks and moving a licence work.

AI assistant

The AI assistant section sets up the AI that suggests sub-tasks and priorities, summarizes the week and plans goals for the people who sign in. A plan counts as one request against the daily limit. AI works when your server uses accounts. It stays off until a provider is set up and Test connection succeeds. The self-hosting guide covers the server side: the settings, the key file and privacy.

The section has these rows:

A value set here wins over the server's settings. Emptying a field, or choosing Off as the provider type, clears the value set here, and the server's setting applies again. The longest answer length can be set only in the server's settings.

Save applies your changes. Test connection first saves any unsaved changes, then sends one small request to the provider. The result shows under the buttons:

Test connection must succeed for AI to be on, and a failed test turns AI off. A change of the provider type, base URL, model or key (in the console or in the key file) also turns it off until the next successful test. Changing the timeout or the daily limit doesn't.

Once AI is on, a slow or failing provider doesn't turn it off. A person whose request the provider didn't answer sees "Couldn’t reach the AI provider" with Try again, and the request isn't counted. If that happens often with a model on your own machine, set the timeout to 120 seconds.

One successful request counts as one; failed requests aren't counted. The count starts again at midnight UTC. When a person's requests are used up, the app shows when they start again. Prompts and answers are never stored or logged; only the daily count is kept.

AI usage

The AI usage section follows the AI assistant section. It shows one row, Everyone on this server, with how many AI requests were answered today (UTC) and in the last 30 days, and the daily requests per person or "No daily limit".

Only the counts are kept: never a task, a prompt, an answer or who asked. A failed or cancelled request isn't counted.

Change log

The last section lists the new features, improvements and fixes in each version of the server, newest first. To update the server, see Updating the server.

On a phone

On a phone or in a narrow window, the console switches to a phone layout. The side menu opens from the top bar, and pages use cards and sheets instead of tables and side panels.