/
The Dermi Portal account owns billing, licenses, and team membership; Clinician and Assistant accounts are used by team members on a Dermi Atlas Professional deployment.
Dermi products use two kinds of accounts. The Dermi Portal account is created at portal.dermi.ai and owns the subscription, the licenses, and the membership of each licensed deployment. Team member accounts are created on a Dermi Atlas Professional deployment and are the accounts used for clinical work on the practice network. The two are separate systems: the Dermi Portal account does not sign in to Dermi Atlas Professional, and a team member account does not sign in to the Dermi Portal.
The Dermi Portal account is the owner. It is used for:
This account lives on Dermi infrastructure and holds no patient data. Its relationship to a deployment is limited to telling the deployment who is on the team: the Dermi Portal cannot read clinical data on the practice network, change the deployment's configuration, or create or elevate an account on it. Membership changes made in the portal are applied by the deployment at its next check-in.
A team member account is created on the deployment itself by claiming an invitation sent from the Dermi Portal. Each member chooses their own username and password and can add two-factor authentication to their own account. The claim process is described in Claiming a Team Invitation.
Every member account belongs to the deployment's team, and every member sees every patient the team documents. Patient records, images, and clinical notes are stored only on the practice's own infrastructure and are never sent to Dermi. Each account carries an Account Type, chosen by the owner when the invitation is sent:
Both types capture images, create patients, add entries and notes, annotate, compare, search the shared patient list, and edit patient assignment. The actions reserved for clinician accounts are listed in How a Team Shares Patient Records.
Account identity is handled separately from clinical data. A member's email address, account type, name, and username are held in the Dermi Portal so that membership can be managed and so that verification and security email can be delivered, and the technical client details of account activity, such as IP address, user agent, and time zone, are transmitted with verification links and security notifications. The full scope of this processing is described in the Dermi Privacy Policy.
Administration sits outside the deployment's two account types. Team membership, seats, and billing are administered by the owner in the Dermi Portal, and the deployment itself is administered locally in Dermi Atlas Manager behind an admin passphrase: settings, disabling and enabling accounts, and the deployment purge. See Inviting and Managing Team Members and Atlas Manager Administration.
The same email address can be used for the Dermi Portal account and for a team member account; the owner commonly invites their own address as the first member of a deployment. The same address can also be a member of several deployments, for example at different practice sites: each deployment is its own team with its own member accounts and credentials, and a Dermi Portal account can own several licenses, one per deployment. A single deployment holds one team, and an address appears on that team once.
Cloud demo visitors sign in with their own Dermi Portal account. Each visitor's account is its own single-member team, so the features that involve other members do not appear there, and demo clinical data is cleared weekly.
Your feedback helps us improve our documentation
Contact our support team for personalized help