Use the owner account created with the bootstrap command.
◎
Doctor self-service
Account data
Doctors can export their commercial account record or submit an owner-reviewed erasure request, even when prescribing access is disabled.
Open account-data tools ⌄
↻
Account recovery
Choose a new password
Overview
Practice administration
Manage doctor access, invitations, software distribution, and security evidence.
Control serverConnected securely
Accounts
Team accounts
A single view of every clinician and their current access.
Total doctors—
Access enabled—
Needs attention—
Expiring in 30 days—
iDisabling an account revokes its server sessions immediately. A connected app detects this at its next licence check (normally within the configured polling window); a disconnected desktop can continue only until its signed offline lease expires (at most the configured offline window).
Team accounts and access state
Account
Role
Licence access
Last sign-in
Status
Actions
Account creation
Doctor invitations
Only doctors with a one-time invitation can create an account.
1Enter doctor details2Create one-time code3Share securely
iThe doctor chooses their own password. Activation codes are shown once and are never stored in readable form.
One-time code
!Copy this now — it will not be shown again.
Doctor invitations
Email
State
Access until
Activation
Notes
Actions
Doctor support
Feedback inbox
Review portal support requests and product feedback. Messages must not contain patient data.
Doctor feedback and support requests
Received
Doctor
Subject
Category
State
Actions
Private owner testing
Test builds
Unverified software for your own test computer. Hidden from doctors and excluded from every automatic-update feed.
!Not a customer release. Use synthetic data only. Never submit prescriptions during QA. Downloads require owner verification and expire after seven days. An integrity signature does not certify Windows compatibility.
Upload a private test build
Owner-only test downloads — not published releases
Build
Target
Expires
Integrity
Actions
Verified distribution
Software releases
Publish separate updater artifacts and doctor-facing installers for macOS, Windows Intel/AMD, and Windows ARM64.
iEvery artifact needs an offline Ed25519 signature over its exact bytes. The macOS updater ZIP uses its Sparkle signature; installers and Windows artifacts use the detached offline signature. macOS and Windows files may use the owner-approved OS-unsigned mode; doctors are instructed to continue past Unknown Developer or SmartScreen only for downloads started directly from 3pres.com.
＋New release draft
Uploaded software releases
Release
Target
State
Published
Size
Actions
Release evidence
—
File
—
Size
—
SHA-256
—
Minimum app / OS
—
Distribution
—
Signature
—
Verification key
—
Release notes
—
Transactional delivery
Email queue
Monitor delivery without exposing message contents.
iRecipients are masked and message bodies remain encrypted. Sent and expired capability bodies are permanently destroyed.
Transactional email delivery queue
Created
Recipient
Kind
State
Attempts
Last result
Actions
Reviewed lifecycle
Privacy requests
Review and document account export and erasure workflows.
!Erasure is a controlled pseudonymization. Reconcile active billing first; required payment, audit, and decision evidence remains under the recorded retention basis.
Doctor privacy requests
Requested
Doctor
State
Review / retention
Actions
Security trail
Audit events
Important activity and routine session renewals, kept separately for easier review. Every event is retained.
Successful routine refreshes are in Auth refreshes. Sign-ins, security warnings, and other actions stay here.