/
The admin passphrase, the Administration area of Dermi Atlas Manager, the local account controls, the deployment-wide settings, and the deployment purge.
Administration of a Dermi Atlas Professional deployment is split between two places. Team membership, seats, and billing belong to the license owner in Dermi Portal. Everything that acts on the deployment itself (the settings that govern logging, retention, and statistics, the immediate disabling of an account, and the permanent removal of clinical data) belongs to Dermi Atlas Manager on the computer that hosts the deployment, behind an admin passphrase.
This article covers setting that passphrase, the recovery phrase issued with it, what the Administration area holds, and how the deployment purge works.
The admin passphrase is set once, on the Admin Passphrase page that Dermi Atlas Manager opens at the end of a fresh installation and at the first launch on an existing installation. Until it is set, the Administration area cannot be opened.
The passphrase never leaves the host computer, and Dermi cannot reset it. It is asked for again before a purge, an uninstall, and a member list resync.
Illustrative demo with synthetic data. Learn more
The passphrase is a safeguard at that computer: it keeps irreversible and deployment-wide actions from being taken casually or by accident, while clinicians and staff keep signing in to Dermi Atlas with their own accounts. Anyone with administrative control of the host computer itself is outside its reach, which is why the host is secured in its own right, as described in Data Security Architecture.
Immediately after the passphrase is set, the Recovery Phrase step shows a single-use recovery phrase of six groups of four characters. It is shown once and never again.
The phrase resets a forgotten passphrase, and a new phrase is issued each time one is used. To use it, open the Administration page in Dermi Atlas Manager, select Use Recovery Phrase on the locked page, and enter the phrase together with a new passphrase in the Reset Passphrase drawer.
A new phrase can be issued at any time from the Admin Passphrase card in the Administration area with Reissue Recovery Phrase. Issuing a new one retires the previous phrase.
When both the passphrase and the recovery phrase are lost, the passphrase is reset on the host computer itself; the steps are in Troubleshooting Dermi Atlas Manager Installation Issues. No accounts, settings, or patient records are affected by that reset.
The Admin Passphrase card in the Administration area carries Change Passphrase, which opens a drawer holding a Current Passphrase field and a New Passphrase field, with one Show passphrase checkbox governing both.
Administration is a section of the Dermi Atlas Manager sidebar. It is locked every time the application starts and is unlocked for the rest of that session by entering the passphrase once. Lock in the page header locks it again without closing the application; it refuses to lock while a settings change has not been applied.
The unlock card carries an Operator Name (optional) field above the passphrase, up to 64 characters, with the hint "Recorded on each action taken while unlocked." A name entered is held for the unlocked session, recorded on every administrative action taken during it, shown beside Atlas Manager on the Administration Activity card, and cleared at Lock. It records who was at the keyboard; the passphrase remains the only gate.
The page is grouped into four headings: Deployment, Settings, Maintenance, and Purge and Uninstall.
User Accounts, described as "Accounts and invitations mirrored from the Dermi Portal", lists the accounts on the deployment. It is read-only: each row carries the member's name, the username, a Clinician or Assistant chip, a membership chip reporting what the last member list from Dermi Portal said about that person, and a Disabled chip where the account has been disabled locally. Accounts appear once a member claims an invitation. Pending invitations are listed after the accounts under an Invitations heading, by email address with the account type chip; they are acted on in Dermi Portal.
Each account row offers one action:
Disabling is the immediate control for a member who must lose access at once, for example after a lost device or a departure taking effect the same day. Removing the member in Dermi Portal is the durable one, because a member removed there is refused at the deployment from its next check-in whatever the local setting says.
Illustrative demo with synthetic data. Learn more
Above the list, a status row reports the state of the member list, and Sync Now checks in with Dermi Portal immediately rather than at the next scheduled check-in. It is the control to use after a change made in the portal should take effect at once.
Illustrative demo with synthetic data. Learn more
Administration Activity, described as "Sign-in and administration records of the deployment", sits after User Accounts. View Activity opens the records in a drawer, newest first. The rows are read-only, each carrying an operation chip, the actor, the time, and a one-line summary, with the address and device named on account rows.
The actor takes one of four forms:
Recorded here are sign-ins and failed attempts, two-factor, password, and email changes, invitation claims, session sign-outs, account recovery and deletion, refused actions, settings changes, account disabling and enabling, member list check-ins and their outcomes, and purge outcomes. Three filters at the top of the drawer narrow the list:
Refresh, the icon beside the filters, reloads the list from the newest row, and Load More at the end of the list appends older ones.
Clinical activity is not listed here. Patient, entry, and image events are read from the patient record in Dermi Atlas, as described in Audit Logging Configuration.
Illustrative demo with synthetic data. Learn more
Four deployment-wide settings live here, each applying to every account on the deployment:
A change is saved with Apply Changes in the page header, and a shorter retention period is confirmed by typing a phrase before it is applied.
Illustrative demo with synthetic data. Learn more
The logging levels are covered in Audit Logging Configuration, the deletion policies and the retention period in Configuring Data Retention for Deleted Records, and what Deployment Statistics sends in Data Security Architecture. The Admin Passphrase card sits in the same group.
The last heading holds the two actions that remove data, in one panel with a red border: the Deployment Purge card, described below, and the Atlas Uninstall card below it. Atlas Uninstall removes Atlas and its patient records and images from this computer, keeps the license and existing backups, and asks for the passphrase again at Begin Uninstall.
The deployment purge permanently deletes every patient record on the deployment while leaving the deployment itself, its accounts, and its configuration in place. It is the tool for decommissioning a deployment, for clearing an evaluation or training installation before real use, and for returning a host to a clean state without reinstalling.
There is no recovery from it. A backup taken beforehand is the only way back, and the card carries a Create Backup button that opens Backup Management for that reason. See Backing Up and Restoring Dermi Atlas Professional.
What is deleted:
What is kept:
To run it:
Illustrative demo with synthetic data. Learn more
The outcome is reported in the drawer rather than as a notification, and open Dermi Atlas pages refresh themselves as the records disappear. The purge is recorded on the Administration Activity card, where the outcome can be read after the drawer is closed. Only one purge runs on a deployment at a time; a second request while one is in progress is refused rather than queued.
Dermi Atlas Manager administers the deployment, not the team. It cannot invite a member, change a member's account type or email address, remove a member, or add or reduce seats. Those belong to the license owner in Dermi Portal, and the deployment applies them at its next check-in, as described in Inviting and Managing Team Members. Dermi Atlas Manager holds no seat counts and no purchase controls.
Nothing in the Administration area sends clinical data anywhere. The member list travels from Dermi Portal to the deployment and reports only who is on the team, and Deployment Statistics sends totals only.
Your feedback helps improve the documentation
Typical response within 24 hours.
All demonstrations, screenshots, and media on this page use synthetic data only. No real patient information is shown.
The following are synthetic and do not correspond to real patients:
Media is provided solely to illustrate platform functionality and workflows.