Skip to content
Enjazy documentation

Enjazy admin guide

The admin console is the web-based management interface for an Enjazy server running in accounts mode. It lives at /console and is accessible only to administrators. The console lets you manage user accounts, sign-in apps, subscriptions, licence keys, and server settings, including the AI assistant.

Signing in and two-step verification

On Online, open the console on the site origin (https://enjazy.app/console); it signs in against the app issuer (https://the.enjazy.app) and returns to the site. Self-hosted servers use their single origin. Old /admin links redirect permanently; /admin/api/* remains a guarded compatibility alias.

Open /console/login in your browser. Enter your email or username and password, then sign in. The first admin is seeded from ENJAZY_ADMIN_USER, ENJAZY_ADMIN_EMAIL and ENJAZY_ADMIN_PASSWORD during first-run setup.

If your account has two-step verification enabled, you will be prompted for a verification code after entering your password. Each digit is entered into its own cell; pasting fills all cells. You can also use your recovery codes if needed.

The sign-in page shows clear error messages for wrong credentials, non-admin accounts, locked-out accounts, disabled accounts, and network failures. A correct password on a non-admin account displays "This account isn't an administrator." without counting as a failure.

After signing in, the console keeps you authenticated through an HttpOnly refresh cookie. Short-lived access tokens are stored in memory only. You can sign out at any time from the sidebar footer.

Overview

The Overview page gives you a snapshot of your server. It shows four stat tiles under People: Users, Active, Disabled, and Administrators (active administrators only). The Server section displays storage used, server version, data schema, and Node.js version.

A health card shows that the server is running and for how many days. It also indicates whether self sign-up is on or off, and whether outgoing email is set up. Common tasks — Add account and Register app — are available as quick links.

Accounts

The Accounts page lists all accounts with the columns Email (with the username under it), Role, Status, Plan and Created. You can search by email or username, filter by role (Administrator or User) and status (Active or Disabled), sort by any column, and paginate through results. A CSV export is available.

To add a new account, click Add account. Fill in the email (required), username (optional, 3–128 characters), name (optional) and a temporary password (required, at least 8 characters; Generate creates a secure passphrase). Choose the role — User or Administrator — and click Create account. On Enjazy Online the form also has Email is verified: tick it only when you know the address belongs to the person. Left unticked, the person confirms the address from the app with Send the link again (Create account sends no email).

Confirmed email addresses (Enjazy Online). On Enjazy Online (ENJAZY_REQUIRE_VERIFIED_EMAIL, on by default there and off on a self-hosted server) an account must confirm its email address before it can use a paid plan or share lists and invite people. Until then the account uses Free; its subscription, trial or the plan you set waits and applies as soon as the address is confirmed, and nothing is ended. The Plan column and the Subscription card still show the plan the account has. The account drawer shows Email not verified with Mark as verified: use it when you know the address is right, for example for a store reviewer's account. Each use is written to the server log as an administrator action. Accounts that existed before this rule are not exempt.

An account's page

Click an account's row to open its summary drawer, then Manage account to open its page; View in the row's ⋯ menu opens the page directly. From here you can manage every aspect of the account.

Status (disable and enable)

Disable account confirms with "Disable this account?" before revoking all active sessions and signing the account out everywhere. The account's status changes to Disabled. Its data is kept, and it cannot sign in again until you enable it.

Enable account reactivates the account immediately, without a confirmation dialog. The account can sign in again.

The last active administrator cannot be disabled, demoted, or deleted. A warning is shown if this guard applies.

E-mail

Click Change email to open a dialog where you enter a new email address. The server clears the email verification flag and, if SMTP is set up, sends a verification email to the new address. A success toast confirms the change.

Administrator role

Click Make administrator to promote a user to admin. Click Remove administrator role to demote an admin back to a regular user. Both actions require confirmation. The last active administrator cannot be demoted.

Two-step verification

When two-step verification is on, an "On" badge is shown. Click Turn off two-step verification… to open a confirmation dialog. The dialog warns you to confirm who you're talking to before making this change. Confirming clears the TOTP secret and all recovery codes. The status then reads "Off".

Reset password

Click Reset password to open a two-step dialog.

Step 1: Choose how to reset — either Email a reset link (a single-use link is sent to the account's email, valid for a configurable number of minutes) or Set a temporary password. You can also check Sign them out everywhere to revoke all active sessions.

Step 2 (link): Confirms the email address and expiry, then sends the link. A success toast appears.

Step 2 (temporary): Enter a new password (or use Generate for a secure passphrase). After resetting, a shown-once dialog displays the temporary password. It can be copied but is never stored or logged. The user is not forced to change it on next login.

Sessions

The Sessions card lists all active sessions with the app name, browser or device, sign-in time, and last used time. Click Sign out on any row to revoke that session immediately. Click Sign out everywhere… to revoke all sessions at once, confirming with "{n} session(s) end now. They can sign in again."

Data and storage

The Data and storage card shows a digest of the account's personal store: counts of lists, tasks, to-dos, done items, projects, tags, comments, task versions, sync operations, and total storage used. It also shows the store path.

Actions available:

Deleting an account

Click Delete account… to open a confirmation dialog. The dialog shows "Delete this account?" and lists what will be lost: its lists and everything in them, every session, and, when it owns shares, the sharing of those lists. A Download backup button is included in the dialog. A type-to-confirm field requiring the account's email is mandatory. Confirming removes the account, its server store, its owned shares, and its memberships. The administrator's own account and the last administrator are disabled for this action.

On Enjazy Online, when the account has a plan, the dialog also says that paid time left on its plan is not refunded. Deleting the account cancels its Stripe subscription at once, with no refund and no final charge, so Stripe stops billing it. If Stripe cannot be reached, the account is still deleted; the subscription's period then says "Stripe could not cancel it" in Subscriptions, and you must cancel it in the Stripe Dashboard yourself.

Sign-in apps

The Sign-in apps page lists all registered OAuth clients with their name, client ID, type (Public or Confidential), consent status (Trusted or Asks for consent), and redirect URIs. You can search by name or client ID and export to CSV.

Click Register app to add a new app. Provide an app name, redirect URIs (one per line, absolute URLs), and optionally mark it as a public client or a trusted first-party app. Public apps appear immediately in the list. Confidential apps also show a client secret in a shown-once dialog — copy it before closing, as it cannot be retrieved again.

From a row's action menu or the app details drawer, you can edit the app name and redirect URIs, rotate the client secret (confidential apps only), or delete the app. Built-in Enjazy apps cannot be changed or removed.

Subscriptions and keys

The Subscriptions page has three tabs: Account plans, Server keys, and App keys.

Account plans lists all subscriptions with the subscriber, plan, status (Active, Lifetime, Scheduled, Expired, or Ended), renewal interval, and end date. You can search, filter by status, and export to CSV.

Click New subscription to create one. Choose the subscriber type (Account, Server, or App), select the account or enter the purchaser email, pick a plan, choose between Lifetime or a renewing term, set the renewal interval in months, and optionally set a start date. If a conflicting subscription exists, you can end the current one and start now, or shift the new one to start when the current ends.

Renewing a subscription extends the end date immediately and is reversible with an Undo toast. Ending a subscription moves the subscriber to the Free plan immediately and is not reversible.

One subscription list per account (Enjazy Online). Every Online account has one list of subscriptions, shown in Subscriptions and on the account's Subscription card. Each has a type (Purchased through Stripe, Free offer, Administrator grant, Free trial or Invite reward) and is counted either in dates (a purchase and your grants run from their start to their end, whatever else runs) or in days (the offer, the trial and rewards: a day is used only while that subscription is the one in force, from the first midnight UTC after it applies). One subscription is in force at a time: the higher plan first (Business, Team, Pro); for the same plan, dated before day-counted, then the one that ends first, then Purchased, Reward, Offer, Trial. The others wait their turn, and nothing moves another subscription's dates or a Stripe renewal. The drawer shows each subscription's type, how it is counted, its days used and left, where it stands now (In force, Waiting its turn, Pending, Expired, Canceled), who created it and who ended it; the account's Subscription card shows the one in force, its days left and what comes next.

Refunds. Closing an account or ending free time never refunds a payment. Free time and paid time can overlap.

Invite codes (Enjazy Online). Every Online account has a personal invite code, which its owner sees in Settings › Plan once their e-mail address is confirmed and they accept the invite program terms; they cannot change it. When someone joins with a code and confirms their e-mail, the code's owner gets an Invite reward of 14 days of Business, counted in days like the offer (at most 12 times in any 12 months; one reward per person, also after a deleted account joins again; nothing for the owner's own addresses). The account drawer's Invites section lists the account's codes and the people who joined with them, with each reward's state. Add invite code gives the account an influencer code: the code (4 to 24 letters and digits), the discount for the person who joins (1 to 100 %) and what it applies to (the first payment, the first months, or every payment). The person who joins with it gets the discount on their first paid checkout, and anyone who has not paid before can type the code at checkout. The influencer earns the same reward. Switch a code off to stop new joins and its discount; rewards already given stay. The account cannot cancel a reward and nothing is refunded; you can end it early from Subscriptions. While one is in force, the Subscription line reads Invite reward with its end date. An account on a lower paid plan gets Business at once, and its subscription keeps its own dates. ENJAZY_REFERRALS=false turns the program off. The Invite codes page (after Subscriptions in the navigation) lists the codes, newest first: influencer codes by default, or every code with Type: All, and a search by code. Each row shows the code, its owner (opens the owner’s account drawer), the type, the discount, an Active switch, how many people joined with it, how many rewards they earned and when it was made.

Teams (Enjazy Online). The owner of a Team plan invites members from Settings › Plan; each member whose seat is within the team's size gets Team (or keeps their own plan if it is higher) while the owner's plan is in force, and goes back to their own plan as soon as the owner removes them, they leave, or the owner's plan ends. A Stripe Team subscription's seats are its size, and the owner takes one. The account drawer's Team section shows, read-only, the team the account owns (its plan, Seats used, and each member or invitation with its state: Invited, Active, Over limit, Invitation expired) or the team it belongs to and whether that gives it a plan now. Team seats is the one action: for a Team or Business you granted by agreement (with New subscription, or an account's admin plan), set how many people it covers, the owner included (1 to 1,000; empty = one). Until you set it, such a plan has one seat and allows no members. The sign-up offer, trials and invite rewards always have one seat, whatever is set, and a Stripe Team bundle always uses its size. Each change is logged as an admin.action (team.seats).

Server keys lists server licence keys (prefix esl_). Keys are masked in the list. You can create a new key with a label and delete existing keys. Deleting a key causes any servers or apps using it to fall to the Free plan at their next licence check.

App keys lists client licence keys (prefix ecl_). The empty state offers Create key. Keys are created with a label and the Pro plan. Like server keys, they are masked in the list and can be deleted. A lifetime Desktop + Mobile licence bought through Stripe adds its key here by itself, labelled Lifetime and the first eight characters of the buyer's account id; the key never expires, and deleting it stops it working at the next licence check. These licences are not sold unless ENJAZY_DEVICE_LICENCE_SALES is on (off by default: the Desktop and Mobile apps are free). A full refund or a dispute of the payment revokes the licence by itself, and its key disappears from this list. A lifetime server licence bought on the Server Pro payment page appears under Server keys with no subscription and no end; a full refund or a dispute of its payment cancels it, and the server falls to Free at its next licence check.

Settings

The Settings page has two controls, followed by the AI assistant and AI usage sections:

Without outgoing email, password-reset links and verification emails cannot be sent.

AI assistant

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

The section has these rows:

A value set here wins over the server's settings file. Emptying a field, or choosing Off as the provider type, clears the value set here, and the settings file's value applies again. The maximum answer length (tokens) is set only in the settings file.

Save sends only the changed fields. Test connection first saves any unsaved changes, then sends one small request to the provider with the saved configuration. The result shows under the buttons:

Test connection must succeed for AI to be on. 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 a daily limit does not.

Once AI is on, a slow or failing provider does not turn it off. A person whose request the provider did not answer sees "Couldn’t reach the AI provider" with Try again, and the request is not 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 are not 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 how many successful AI requests were answered today (UTC) and in the last 30 days, with the daily limit:

Only the counts are kept: never a task, a prompt, an answer or who asked. A failed or cancelled request is not counted. The counts per plan are kept for 30 days. To check a provider before you turn AI on, see the smoke check in the self-hosting guide.

On a phone

At viewports up to 719 px wide, the console switches to a phone layout. The sidebar becomes a navigation menu accessible from an app bar. Pages use cards and sheets instead of tables and drawers.

Last-resort CLI

The server ships a command-line interface for the database and for migration. It is the operational fallback when the console is unavailable:

npm run -w @enjazy/server db -- status
npm run -w @enjazy/server db -- up
npm run -w @enjazy/server db -- down
npm run -w @enjazy/server migrate-v1 -- --from <1.x data dir or MySQL URL> --to <new data dir> [--dry-run]

status reports the current schema, up applies the forward-only migration ladder, and down restores the pre-upgrade backup copy rather than running destructive down migrations. migrate-v1 migrates a 1.x server into a new database; always run the dry run first.