Whoever runs draften (the operator, superadmin in the interface) sees an extra Installation part in the menu, with the pages Organisations, Installation and Operations. They cannot see inside the organisations, though: they know only their name, bindings, owners and size. On your own installation, the operator is the first administrator you give the installer.
Installation
The version, updates, backups and licence of this installation, and the defaults for every organisation.
Version — which version is running and whether the updater is running (and when it last looked for new versions). When a new version is available, it is here with its release notes and an Update to … button; the application keeps running during the update and you see the progress right in the card. After an update there is also Go back to … the previous version. The guide Updating with the updater shows the procedure. When the updater is not running, the card says so and points to the command line (./draften update).
Worker processes — how many worker processes are running and a field for the new number (1–16). The updater writes the number into .env (WORKER_REPLICAS) and starts the processes again. Before adding a process, try raising the concurrency on the Operations page — see Operations and capacity.
Encryption key — replacing the MASTER_KEY. The updater creates a new key and writes it into .env on the server; it never reaches the interface. Then keep a copy of .env off the server — see Backup and restore.
Database backups — the last seven database dumps in the backups/ folder on the server (when taken, kind, version, size), the time of the daily backup with its time zone and a Back up now button. The updater backs up every day (01:00 by default) and before every update; when the daily backup fails, the card shows why. The backups lie on the same disk as the database — copy them elsewhere, see Backup and restore. Without the updater, the card points to the command ./draften backup.
Requests — the updater's last ten requests (update, going back, the number of processes, replacing the key, a backup on request): who made them, when they finished and any error.
The updater handles only one request at a time; the next one can be made once it has finished. A request it has not taken yet can be cancelled.
Data retention — after how many days messages, drafts and the texts the assistants learn from are deleted in every organisation (90 by default, 30–3,650 days, or "Never delete"). Lessons and knowledge corrections stay. Shortening the period asks for confirmation — older data is deleted for good at the next clean-up. After the update that brings data retention, the first clean-up comes only 24 hours later. What exactly is deleted is in Where the data lives.
Licence — whom the licence belongs to, until when it is valid, how many mailboxes and assistants it allows and how many are created; a new one is uploaded here too. See The licence.
On our service (SaaS), our pipeline deploys new versions: the Version card says so, and no licence is uploaded here.
Installation status — whether MASTER_KEY is set (without it nothing stored encrypted can be read), whether there is a default mail sender, which organisations have no owner signed in yet, and how many mailboxes have no access.
Default API keys — model keys for organisations and mailboxes without their own. Only here can a key to an OpenAI-compatible server (a local model) be added, because it carries the server address. See Model API keys.
Default outgoing mail — where invitations go out from for organisations without their own sender, and also the invitations to found an organisation. See Outgoing mail.
Organisations
Invitations to found an organisation — the easiest way: enter the future owner's e-mail, optionally the organisation's name (it is pre-filled) and the language of the e-mail. The invitee gets a link valid for 7 days, founds the organisation themselves and becomes its owner. A new invitation for the same address replaces the old one. The list shows each invitation's status (pending, used, expired); an unsent one can be Sent again, a valid one Revoked. The invitee's steps are in the guide Founding an organisation.
New organisation — or set it up yourself: the name, the first owner's e-mail (and name, for a new person), optionally the Entra tenant ID and the e-mail domains.
Organisations set up — the list with sign-in, owners and size. For each:
- Edit sign-in — the directory bindings (the owner can set them too),
- Seat an owner — when the owner is lost,
- Suspend / Resume — a suspended organisation is locked: members cannot sign in and the assistants skip its mailboxes,
- Delete — only a suspended one, with everything in it (mailboxes, assistants, messages, drafts, keys, settings). The accounts of people who were only in this organisation are deleted too; anyone who is a member elsewhere as well, or has access to a mailbox in another organisation, keeps their account, and so does the operator. It cannot be undone; you confirm by typing the name.
Operations
The Operations page shows the running workers, the assistants' lag and the job queue. It is described in Operations and capacity.